说实话 我这边打开超慢~~节点也不少。
C:\Documents and Settings\Administrator>tracert 66.152.167.249
Tracing route to 249-167-152-66-dedicated.multacom.com [66.152.167.249]
over a maximum of 30 hops:
4 30 ms 31 ms 31 ms 202.97.45.169
5 77 ms 30 ms 93 ms 202.97.33.118
6 77 ms 77 ms 46 ms 202.97.60.182
7 234 ms 234 ms 187 ms 202.97.51.218
8 249 ms 249 ms 249 ms 202.97.50.54
9 * * 359 ms cpr1-ge-4-0.sanjoseequinix.savvis.net [208.173.5
4.33]
10 * 359 ms 343 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.7
0.200.198]
11 327 ms * 374 ms cr2-bundle-pos-1.losangeles.savvis.net [204.70.1
97.29]
12 359 ms 312 ms 312 ms ber1-tenge-3-1.losangeles.savvis.net [204.70.193
.50]
13 359 ms * 359 ms tge4-2.cr2.lax.multacom.com [208.172.36.102]
14 * 359 ms * tge3-1.cr3.lax.multacom.com [208.64.231.5]
15 357 ms * * 249-167-152-66-dedicated.multacom.com [66.152.16
7.249]
16 309 ms * * 249-167-152-66-dedicated.multacom.com [66.152.16
7.249]
17 371 ms * 359 ms 249-167-152-66-dedicated.multacom.com [66.152.16
7.249]
Trace complete.
C:\Documents and Settings\Administrator>ping 66.152.167.249
Pinging 66.152.167.249 with 32 bytes of data:
Reply from 66.152.167.249: bytes=32 time=314ms TTL=50
Reply from 66.152.167.249: bytes=32 time=359ms TTL=50
Reply from 66.152.167.249: bytes=32 time=359ms TTL=50
Request timed out.
Ping statistics for 66.152.167.249:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 314ms, Maximum = 359ms, Average = 344ms