reply to c2roth
Re: Kitchener Slow Speeds
said by c2roth:Maybe local node congestion?
Thanks for the responses guys.
I'll make a direct forum thread for this and see what we can determine. I've been collecting speedtests, pingtests, tracerts, and clusters of 100 pings to common websites. I also setup a line monitor within the TekSavvy group and the data it collected last night shows the crazy high pings I was seeing.
I wasn't able to test this morning to see if things had cleared up but that is the next step along with rebooting the modem.
Quick update. After going through the standard tests I got some more details:
East Cost Line Monitor: »ny-monitor.dslreports.com/r3/cri···and=3905
West Coast Line Monitor: »220.127.116.11/r3/cricket/grapher?t···and=3905
Pings have been TERRIBLE in the past 72 hours. I cannot do anything sensitive to latency. Gaming and VOIP (Skype) are both non-functional at this point.
Tracing route to google.ca [18.104.22.168]
over a maximum of 30 hops:
1 23 ms 11 ms 11 ms 10.125.96.1
2 422 ms 19 ms 35 ms 22.214.171.124
3 377 ms 99 ms 7 ms kitchener3.cable.teksavvy.com [126.96.36.199]
4 31 ms 9 ms 10 ms kitchener1.cable.teksavvy.com [188.8.131.52]
5 47 ms 10 ms 8 ms gw-google.torontointernetxchange.net [184.108.40.206]
6 38 ms 14 ms 49 ms 220.127.116.11
7 505 ms 239 ms 9 ms 18.104.22.168
8 456 ms 29 ms 11 ms yyz06s06-in-f23.1e100.net [22.214.171.124]
Tracing route to ns.teksavvy.com [126.96.36.199]
over a maximum of 30 hops:
1 31 ms 10 ms 9 ms 10.125.96.1
2 413 ms 22 ms 62 ms 188.8.131.52
3 457 ms 20 ms 11 ms kitchener3.cable.teksavvy.com [184.108.40.206]
4 11 ms 9 ms 38 ms kitchener2.cable.teksavvy.com [220.127.116.11]
5 21 ms 10 ms 60 ms 2120.ae0.agg01.tor.packetflow.ca [18.104.22.168]
6 32 ms 11 ms 56 ms ns.teksavvy.com [22.214.171.124]
Notice the terrible pings for the second hop, I think this is the CMTS? Then the POI link looks congested. Whats weird is that the traffic goes over one link and then over another. That seems backwards. I would think that traffic would be handed off the TSI link to another segment further down the network.
ping -n 100 -l 1000 (ipv4 Gateway)
Reply from 126.96.36.199: bytes=1000 time=497ms TTL=255
Reply from 188.8.131.52: bytes=1000 time=504ms TTL=255
Reply from 184.108.40.206: bytes=1000 time=483ms TTL=255
Reply from 220.127.116.11: bytes=1000 time=482ms TTL=255
Ping statistics for 18.104.22.168:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 555ms, Average = 402ms
Nice average ping of 402ms to my gateway...yuck
I'm not sure as to cause of this but service had been rock solid in terms of speed and latency since installation in June. Something locally must have changed in the past week or so.