Why does traceroute take much longer than ping?
Posted
by PHP
on Server Fault
See other posts from Server Fault
or by PHP
Published on 2010-02-05T08:40:42Z
Indexed on
2010/04/01
20:43 UTC
Read the original article
Hit count: 771
traceroute
|ping
How to explain this?
C:\Documents and Settings\Administrator>tracert google.com
Tracing route to google.com [64.233.189.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms <1 ms <1 ms reserve.cableplus.com.cn [218.242.223.209]
3 108 ms 135 ms 163 ms 211.154.70.10
4 * * * Request timed out.
5 2 ms * 1 ms 211.154.64.114
6 1 ms 1 ms 1 ms 211.154.72.185
7 1 ms 1 ms 1 ms 202.96.222.77
8 2 ms 1 ms 2 ms 61.152.81.145
9 1 ms 2 ms 1 ms 61.152.86.54
10 1 ms 1 ms 1 ms 202.97.33.238
11 2 ms 2 ms 2 ms 202.97.33.54
12 2 ms 1 ms 2 ms 202.97.33.5
13 33 ms 33 ms 33 ms 202.97.61.50
14 34 ms 34 ms 34 ms 202.97.62.214
15 34 ms 186 ms 37 ms 209.85.241.56
16 35 ms 35 ms 44 ms 66.249.94.34
17 34 ms 34 ms 34 ms hkg01s01-in-f104.1e100.net [64.233.189.104]
Trace complete.
So average time should be :1+7+108+2+1+1+2+1+1+2+2+33+34+34+35+34+34+35+34,which is a lot bigger than ping
C:\Documents and Settings\Administrator>ping google.com
Pinging google.com [64.233.189.104] with 32 bytes of data:
Reply from 64.233.189.104: bytes=32 time=34ms TTL=241
Reply from 64.233.189.104: bytes=32 time=34ms TTL=241
Reply from 64.233.189.104: bytes=32 time=34ms TTL=241
Reply from 64.233.189.104: bytes=32 time=34ms TTL=241
Ping statistics for 64.233.189.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 34ms, Average = 34ms
© Server Fault or respective owner