dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
973
priyen
join:2009-12-23
North York, ON

priyen

Member

Absurd Ping to Google.Ca!

Im getting 44ms ping to google.ca.. suppose to be like 10ms
o.o

Tracing route to google.ca [74.125.226.24]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms [192.168.1.1]
2 * * * Request timed out.
3 12 ms 14 ms 11 ms 66.185.91.185
4 9 ms 9 ms 8 ms gw-greensboro-to-ipr01.distributel.net [209.195.70.70]
5 11 ms 11 ms 11 ms 206-80-244-121.cpe.distributel.net [206.80.244.121]
6 11 ms 11 ms 11 ms gw-google.torontointernetxchange.net [206.108.34.6]
7 11 ms 11 ms 11 ms 216.239.47.114
8 28 ms 27 ms 27 ms 216.239.46.160
9 48 ms 48 ms 46 ms 72.14.239.90
10 77 ms 46 ms 47 ms 72.14.239.127
11 * * * Request timed out.
12 47 ms 46 ms 47 ms yyz06s05-in-f24.1e100.net [74.125.226.24]

Trace complete.

Anyone know why?
Riplin
join:2002-05-13
canada

Riplin

Member

Olympic hammering?

pstewart
Premium Member
join:2005-10-12
Peterborough, ON

pstewart to priyen

Premium Member

to priyen
Can you post the actual ping? You posted a traceroute which is a different measurement....

donoreo
Premium Member
join:2002-05-30
North York, ON

donoreo

Premium Member

said by pstewart:

Can you post the actual ping? You posted a traceroute which is a different measurement....

Exactly, traceroutes are always slower than pings.

Gone
Premium Member
join:2011-01-24
Fort Erie, ON

Gone

Premium Member

said by donoreo:

Exactly, traceroutes are always slower than pings.

They shouldn't be, both being the same ICMP echo requests (on Windows, anyway) and all that. Case in point:
quote:
Pinging www-cctld.l.google.com [74.125.226.55] with 32 bytes of data:
Reply from 74.125.226.55: bytes=32 time=10ms TTL=57
Reply from 74.125.226.55: bytes=32 time=9ms TTL=57
Reply from 74.125.226.55: bytes=32 time=10ms TTL=57
Reply from 74.125.226.55: bytes=32 time=10ms TTL=57
quote:
Tracing route to www-cctld.l.google.com [74.125.226.63]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 7 ms 8 ms 10.202.196.1
3 10 ms 9 ms 10 ms asr-link1-burlington1.net.start.ca [64.140.112.154]
4 11 ms 9 ms 9 ms core1-toronto1-te3-3.net.start.ca [64.140.112.153]
5 9 ms 9 ms 9 ms gw-google.torontointernetxchange.net [206.108.34.6]
6 11 ms 10 ms 9 ms 216.239.47.114
7 9 ms 9 ms 9 ms 64.233.175.132
8 10 ms 9 ms 9 ms yyz06s06-in-f31.1e100.net [74.125.226.63]

Trace complete.
*nix is a bit different, but even if I do a traceroute off my router the difference when using UDP is negligible.

donoreo
Premium Member
join:2002-05-30
North York, ON

donoreo

Premium Member

I always find it takes a big longer on the hops. I am usually doing it from a NIX of some sort, hardly ever windows.

JoJoBlue
join:2009-12-08
Scarborough, ON

JoJoBlue to priyen

Member

to priyen
Google.ca has multiple servers (maybe all of the 74.125.226.* block). Each time you ping 'www.google.ca', you're randomly connected to one. I've noticed that sometimes, some of them are noticeably more laggy than others. Perhaps try 74.125.226.88 or something else and see if you get better results.
highwire2007
join:2008-05-17
Nepean, ON

highwire2007 to priyen

Member

to priyen
OK here

1 10.0.1.1 (10.0.1.1) 0.678 ms 0.346 ms 0.491 ms
2 10.124.6.1 (10.124.6.1) 6.223 ms 7.233 ms 6.054 ms
3 69.63.255.245 (69.63.255.245) 15.923 ms 14.267 ms 15.699 ms
4 fallowfield2.cable.teksavvy.com (69.196.175.186) 6.724 ms
fallowfield3.cable.teksavvy.com (24.52.255.78) 8.801 ms
fallowfield1.cable.teksavvy.com (24.246.55.22) 7.842 ms
5 fallowfield3.cable.teksavvy.com (24.52.255.77) 13.282 ms 13.176 ms 12.701 ms
6 gw-google.torontointernetxchange.net (206.108.34.6) 14.467 ms 14.035 ms 13.961 ms
7 216.239.47.114 (216.239.47.114) 13.248 ms 13.429 ms 12.476 ms
8 64.233.175.132 (64.233.175.132) 14.787 ms 16.143 ms 14.223 ms
9 yyz06s06-in-f18.1e100.net (74.125.226.50) 14.291 ms 14.312 ms 14.254 ms

1 2002:18f6:595:1::1 7.355 ms 0.490 ms 0.469 ms
2 2002:c058:6301::1 12.963 ms 13.141 ms 13.719 ms
3 gige-g2-18.core1.tor1.he.net 12.509 ms 12.863 ms 16.217 ms
4 2001:478:245:1::6 13.731 ms 13.448 ms 15.461 ms
5 2001:4860::1:0:28 12.979 ms 13.465 ms 14.226 ms
6 2001:4860:0:1::26a 13.979 ms 13.134 ms 13.979 ms
7 2607:f8b0:8000:13::12 13.509 ms 12.693 ms 13.973 ms
priyen
join:2009-12-23
North York, ON

priyen

Member

It got fixed in a few hours.. and the ping was also 44 and traceroute showed 47 .. so..anyways fixed, thanks for the help