|
djtodd
Anon
2012-Nov-6 6:10 pm
[Cable] Very poor latentcy on Cable...Anyone else experiencing really bad ping times/latentcy on Teksavvy Cable?
Tracing route to google.com [74.125.226.38] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms my.router [192.168.1.1] 2 2102 ms 3093 ms 3091 ms 10.126.208.129 3 1495 ms * 2378 ms gw01.orvl.phub.net.cable.rogers.com [66.185.91.1 05] 4 1121 ms 42 ms * dupont5.cable.teksavvy.com [24.52.255.18] 5 78 ms 792 ms 806 ms dupont3.cable.teksavvy.com [24.52.255.129] 6 501 ms 1019 ms 2568 ms 72.14.212.134 7 1019 ms 11 ms 53 ms 216.239.47.114 8 1603 ms 487 ms 503 ms 64.233.175.132 9 1225 ms 154 ms 30 ms yyz06s06-in-f6.1e100.net [74.125.226.38] |
|
|
jibby
Member
2012-Nov-6 7:04 pm
no problems for me on Dupont
Tracing route to google.com [74.125.228.104] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms my_router [192.168.1.1] 2 8 ms 9 ms 9 ms 10.126.211.129 3 12 ms 11 ms 11 ms 24.156.150.5 4 9 ms 9 ms 7 ms dupont5.cable.teksavvy.com [24.52.255.18] 5 9 ms 14 ms 8 ms dupont4.cable.teksavvy.com [24.52.255.125] 6 52 ms 9 ms 9 ms 72.14.212.134 7 11 ms 30 ms 12 ms 209.85.255.232 8 38 ms 37 ms 31 ms 209.85.255.235 9 40 ms 39 ms 41 ms 209.85.249.11 10 38 ms 39 ms 41 ms 72.14.236.153 11 41 ms 39 ms 41 ms 72.14.238.253 12 41 ms 42 ms 39 ms iad23s08-in-f8.1e100.net [74.125.228.104]
wow there are 5 dupont IP's now? jeez |
|
2 edits |
to djtodd
First trace is really high latency. Second shows picking a further away Google server (likely due to not using TekSavvy's DNS). In Ottawa I get 20ms or below the whole way but to a closer server, at least one accessible using fewer hops. Tracing route to google.com [74.125.226.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dlinkrouter [192.168.0.1]
2 8 ms 7 ms 8 ms 10.125.240.129
3 18 ms 17 ms 15 ms 69.63.242.13
4 9 ms 8 ms 7 ms richmond3.cable.teksavvy.com [24.52.255.74]
5 13 ms 13 ms 13 ms richmond1.cable.teksavvy.com [24.246.55.9]
6 14 ms 15 ms 15 ms 72.14.212.134
7 15 ms 20 ms 14 ms 216.239.47.114
8 15 ms 14 ms 15 ms 72.14.233.142
9 14 ms 15 ms 13 ms yyz06s05-in-f4.1e100.net [74.125.226.4]
|
|
|
TSILiz Premium Member join:2012-08-20 |
to djtodd
Hi There,
Feel free to post in the direct forum as well and we can troubleshoot. |
|
|
to djtodd
For comparison, here's what I'm seeing here in Ottawa:
doug$ traceroute www.google.com traceroute: Warning: www.google.com has multiple addresses; using 74.125.226.52 traceroute to www.google.com (74.125.226.52), 64 hops max, 52 byte packets 1 10.0.1.1 (10.0.1.1) 0.727 ms 0.323 ms 0.293 ms 2 10.124.6.1 (10.124.6.1) 6.748 ms 9.982 ms 9.630 ms 3 67.231.222.25 (67.231.222.25) 15.923 ms 21.294 ms 15.318 ms 4 fallowfield1.cable.teksavvy.com (24.246.55.22) 7.810 ms fallowfield2.cable.teksavvy.com (69.196.175.186) 9.424 ms fallowfield3.cable.teksavvy.com (24.52.255.78) 8.425 ms 5 fallowfield3.cable.teksavvy.com (24.52.255.77) 13.171 ms 13.993 ms 13.241 ms 6 gw-google.torontointernetxchange.net (206.108.34.6) 13.159 ms 16.237 ms 13.548 ms 7 216.239.47.114 (216.239.47.114) 14.180 ms 13.609 ms 13.247 ms 8 64.233.175.132 (64.233.175.132) 14.216 ms 13.335 ms 15.520 ms 9 yyz06s06-in-f20.1e100.net (74.125.226.52) 15.570 ms 15.617 ms 13.625 ms |
|
ReeG join:2012-02-27 North York, ON |
to djtodd
Yes horrible right now
Tracing route to google.com [74.125.226.37] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1 2 * 2905 ms 128 ms 10.126.29.129 3 * * * Request timed out. 4 511 ms 582 ms 3290 ms yorkmills6.cable.teksavvy.com [24.52.255.138] 5 1054 ms 2069 ms 950 ms yorkmills2.cable.teksavvy.com [24.52.255.9] 6 2295 ms 104 ms 450 ms 72.14.212.134 7 * * 1918 ms 216.239.47.114 8 * * * Request timed out. 9 1325 ms 3010 ms * yyz06s06-in-f5.1e100.net [74.125.226.37] 10 * * 1487 ms yyz06s06-in-f5.1e100.net [74.125.226.37]
Trace complete. |
|
ReeG |
to djtodd
Reset my modem and it's fine now. Take from that what you will. This isn't the first time I've had brutal speeds and packet loss and then a modem reset magically makes everything work fine again. This was happening every other day a month or two ago, then it was fine for a while, now it's happened twice since last night.
OP what modem do you have? Probably meaningless but I'm curious none the less.
Tracing route to google.ca [74.125.226.56] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1 2 9 ms 9 ms 9 ms 10.126.29.129 3 15 ms 14 ms 14 ms 69.63.254.17 4 9 ms 10 ms 7 ms yorkmills5.cable.teksavvy.com [24.52.255.134] 5 11 ms 9 ms 12 ms yorkmills5.cable.teksavvy.com [24.52.255.133] 6 10 ms 9 ms 16 ms gw-google.torontointernetxchange.net [206.108.34 .6] 7 11 ms 9 ms 10 ms 216.239.47.114 8 11 ms 12 ms 10 ms 64.233.175.132 9 9 ms 10 ms 10 ms yyz06s06-in-f24.1e100.net [74.125.226.56]
Trace complete. |
|
|
djtodd to jibby
Anon
2012-Nov-6 8:48 pm
to jibby
Yeah, it would appear that power cycling my cable modem cleared my response times down to your levels.
Thanks! |
|
|
to djtodd
Yup...second time it happens to me since yesterday. A power reset fixes all.
tracert google.com
1 1 ms 1 ms 1 ms READYSHARE [192.168.1.1] 2 * * * Request timed out. 3 171 ms 143 ms 183 ms 67.231.222.29 4 568 ms 186 ms 431 ms stlaurent1.cable.teksavvy.com [24.246.55.6] 5 47 ms 284 ms 41 ms stlaurent3.cable.teksavvy.com [24.52.255.81] 6 291 ms 146 ms 27 ms 72.14.212.134 7 328 ms 106 ms 121 ms 216.239.47.114 8 211 ms 269 ms 144 ms 64.233.175.98 9 900 ms 513 ms 126 ms yyz06s07-in-f2.1e100.net [74.125.226.66] |
|
creed3020 Premium Member join:2006-04-26 Kitchener, ON |
to jibby
said by jibby:wow there are 5 dupont IP's now? jeez Consider it a good thing that Dupont has 5 1gbps links. It should mean that there is more than enough capacity for the all of the customers on that POI. I think that almost all of the Toronto POIs are up to 5 links now. Perhaps the newly created Comstock is the only one with less than that. |
|
|
jibby
Member
2012-Nov-7 5:01 pm
said by creed3020:said by jibby:wow there are 5 dupont IP's now? jeez Consider it a good thing that Dupont has 5 1gbps links. It should mean that there is more than enough capacity for the all of the customers on that POI. I think that almost all of the Toronto POIs are up to 5 links now. Perhaps the newly created Comstock is the only one with less than that. oh yeah i'm happy about the capacity, don't get me wrong just still a little amazed Rogers can't come up with a a better way (like higher capacity single connections rather than splitting everything up) actually scratch that, i'm not amazed, it IS Rogers after all |
|