Bad Pings to East Coast

[#1]

Ping was done to Washinton, United States

Tracing route to hosted-by.i3d.net [162.244.54.43]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms router.asus.com [192.168.50.1]
2 9 ms 11 ms 9 ms 24.78.128.1
3 53 ms 10 ms 10 ms rc2nr-be108-1.wp.shawcable.net [64.59.180.109]
4 175 ms 34 ms 257 ms rc3fs-hge0-7-0-0.mt.shawcable.net [66.163.76.22]
5 164 ms 282 ms 44 ms rc1eqn-tge0-0-0-0.uk.shawcable.net [66.163.78.146]
6 248 ms 43 ms 42 ms de-cix.nyc.i3d.net [206.130.10.63]
7 48 ms 48 ms 48 ms 10ge.usrtv1-rt002i.i3d.net [109.200.218.157]
8 48 ms 48 ms 49 ms hosted-by.i3d.net [162.244.54.43]

[#2]

Ping was done to Chicago, United States

Tracing route to hosted-by.i3d.net [138.128.140.53]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms router.asus.com [192.168.50.1]
2 9 ms 9 ms 8 ms **.**.**.**
3 241 ms 10 ms 10 ms rc2nr-be108-1.wp.shawcable.net [64.59.180.109]
4 173 ms 9 ms 9 ms rc3sc-hge0-9-0-0.wp.shawcable.net [66.163.73.145]
5 217 ms 25 ms 26 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
6 25 ms 25 ms 25 ms be4225.ccr41.ord03.atlas.cogentco.com [38.88.205.9]
7 25 ms 25 ms 25 ms be2766.ccr42.ord01.atlas.cogentco.com [154.54.46.177]
8 26 ms 26 ms 27 ms be3470.rcr51.b022161-0.ord01.atlas.cogentco.com [154.54.1.102]
9 26 ms 27 ms 28 ms 38.32.36.186
10 26 ms 27 ms 26 ms hosted-by.i3d.net [138.128.140.53]

[mjducharme]

Bad pings? You are in Winnipeg and getting 48 ms to Washington state and 26 ms to Chicago. Those look great, no problem. Unless you can find a way to increase the speed of light, you're unlikely to get much better.

[#4]

Look at hops 4, 5 100+

Shows its going to the UK for some reason, 100+ in montreal

[mjducharme]

That doesn't mean anything. Hop routers typically rate limit ICMP on purpose to help lessen the impact of ICMP related DDoS attacks. If you get high latency to a hop in between and lower latency to a future hop, then the initial high latency isn't real and can be ignored. Same with packet loss.

If you run a continuous ping to the target instead of a traceroute (ex. ping -t 162.244.54.43) and you sometimes get >100 ms over a hundred repeated pings, then you might have an actual issue.

[#6]

I see ping spikes all the time.

I'll wait for a official Shaw rep to answer thanks though.

[mjducharme]

Run a continuous WinMTR or continuous ping (ping -t 162.244.54.43), and see what your latency looks like to the final hop over a period of time. A single tracert isn't good enough for troubleshooting for this.

P.S. I am a high-level network engineer at an ISP - I do know what I am talking about, even though I am not an "official shaw rep".

[#8]

ping -t 162.244.54.43

Pinging 162.244.54.43 with 32 bytes of data:
Reply from 162.244.54.43: bytes=32 time=279ms TTL=57
Reply from 162.244.54.43: bytes=32 time=623ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=50ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=206ms TTL=57
Reply from 162.244.54.43: bytes=32 time=74ms TTL=57
Reply from 162.244.54.43: bytes=32 time=229ms TTL=57
Reply from 162.244.54.43: bytes=32 time=56ms TTL=57
Reply from 162.244.54.43: bytes=32 time=55ms TTL=57
Reply from 162.244.54.43: bytes=32 time=273ms TTL=57
Reply from 162.244.54.43: bytes=32 time=206ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=48ms TTL=57
Reply from 162.244.54.43: bytes=32 time=49ms TTL=57

[#9]

C:\WINDOWS\system32>ping -t 138.128.140.53

Pinging 138.128.140.53 with 32 bytes of data:
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=141ms TTL=56
Reply from 138.128.140.53: bytes=32 time=160ms TTL=56
Reply from 138.128.140.53: bytes=32 time=829ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=159ms TTL=56
Reply from 138.128.140.53: bytes=32 time=28ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=116ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=28ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56
Reply from 138.128.140.53: bytes=32 time=27ms TTL=56
Reply from 138.128.140.53: bytes=32 time=26ms TTL=56

[#10]

This test was done through cloudping.info

Pinging 3.80.0.0 with 32 bytes of data:
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=256ms TTL=239
Reply from 3.80.0.0: bytes=32 time=96ms TTL=239
Reply from 3.80.0.0: bytes=32 time=74ms TTL=239
Reply from 3.80.0.0: bytes=32 time=243ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=65ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=67ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=66ms TTL=239
Reply from 3.80.0.0: bytes=32 time=189ms TTL=239
Reply from 3.80.0.0: bytes=32 time=167ms TTL=239