Tracing route to www.yahoo.co.jp [210.152.236.115] over a maximum of 30 hops:
1 61 ms 60 ms 70 ms 211.11.106.4 2 70 ms 60 ms 60 ms 211.11.106.1 3 60 ms 60 ms 70 ms 192.168.0.1 4 60 ms 61 ms 60 ms 192.168.1.1 5 60 ms 70 ms 70 ms 211.16.128.5 6 60 ms 80 ms 70 ms 210.190.177.41 7 70 ms 80 ms 71 ms 210.190.162.34 8 60 ms 70 ms 70 ms 210.254.187.162 9 70 ms 70 ms 70 ms 210.254.187.45 10 70 ms 60 ms 60 ms 210.254.187.6 11 80 ms 80 ms 70 ms 211.6.0.78 12 70 ms 80 ms 70 ms 203.183.238.129 13 70 ms 80 ms 71 ms 203.183.254.29 14 70 ms 80 ms 70 ms 203.183.250.147 15 61 ms 80 ms 60 ms 202.239.61.245 16 70 ms 80 ms 81 ms 210.152.236.115
Trace complete.
C:\>ping www.google.com
Pinging google.lb.google.com [216.239.37.100] with 32 bytes of data:
Reply from 216.239.37.100: bytes=32 time=230ms TTL=41 Reply from 216.239.37.100: bytes=32 time=220ms TTL=41 Reply from 216.239.37.100: bytes=32 time=231ms TTL=41 Reply from 216.239.37.100: bytes=32 time=220ms TTL=41
Ping statistics for 216.239.37.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 220ms, Maximum = 231ms, Average = 225ms
Tracing route to www.yahoo.co.jp [210.152.236.114] over a maximum of 30 hops:
1 131 ms 120 ms 130 ms 211.11.106.5 2 130 ms 121 ms 120 ms 211.11.106.1 3 140 ms 131 ms 140 ms 192.168.0.1 4 140 ms 130 ms 131 ms 192.168.1.1 5 130 ms 140 ms 130 ms 211.16.128.5 6 130 ms 130 ms 150 ms 210.190.177.41 7 141 ms 130 ms 150 ms 210.190.162.34 8 130 ms 141 ms 130 ms 210.254.187.162 9 130 ms 130 ms 141 ms 210.254.187.45 10 140 ms 130 ms 130 ms 210.254.187.6 11 130 ms 140 ms 130 ms 211.6.0.78 12 150 ms 140 ms 130 ms 203.183.238.129 13 131 ms 140 ms 140 ms 203.183.254.29 14 130 ms 131 ms 150 ms 203.183.250.139 15 130 ms 140 ms 161 ms 203.183.237.57 16 140 ms 140 ms 141 ms 210.152.236.114
Trace complete.
C:\>ping www.google.com
Pinging google.lb.google.com [216.239.37.100] with 32 bytes of data:
Reply from 216.239.37.100: bytes=32 time=300ms TTL=41 Reply from 216.239.37.100: bytes=32 time=301ms TTL=41 Reply from 216.239.37.100: bytes=32 time=300ms TTL=41 Reply from 216.239.37.100: bytes=32 time=300ms TTL=41
Ping statistics for 216.239.37.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 300ms, Maximum = 301ms, Average = 300ms
Tracing route to www.yahoo.co.jp [210.152.236.111] over a maximum of 30 hops:
1 170 ms 160 ms 161 ms 61.113.158.3 2 170 ms 170 ms 171 ms 61.113.158.1 3 240 ms 230 ms 241 ms 192.168.6.1 4 220 ms 231 ms 220 ms 192.168.3.1 5 220 ms 221 ms 220 ms 211.16.174.163 6 240 ms 231 ms 230 ms 210.190.177.221 7 231 ms 240 ms 230 ms 210.190.162.163 8 231 ms 230 ms 240 ms 210.254.187.131 9 241 ms 220 ms 220 ms 210.254.187.109 10 220 ms 230 ms 221 ms 210.254.187.70 11 240 ms 230 ms 231 ms 211.6.0.78 12 230 ms 241 ms 230 ms 203.183.238.129 13 230 ms 231 ms 240 ms 203.183.254.29 14 240 ms 231 ms 400 ms 203.183.250.147 15 231 ms 240 ms 230 ms 202.239.61.245 16 241 ms 240 ms 230 ms 210.152.236.111
Trace complete.
C:\>ping www.google.com
Pinging google.lb.google.com [216.239.37.100] with 32 bytes of data:
Reply from 216.239.37.100: bytes=32 time=381ms TTL=41 Reply from 216.239.37.100: bytes=32 time=390ms TTL=41 Reply from 216.239.37.100: bytes=32 time=381ms TTL=41 Reply from 216.239.37.100: bytes=32 time=381ms TTL=41
Ping statistics for 216.239.37.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 381ms, Maximum = 390ms, Average = 383ms