|
to rmortier
Re: Anyone else have high latency on TekSavvy Chatham Cable tonight?You're going to see steam coming out of my ears tomorrow if this same shit happens during NFL. |
|
|
Sunday night is typically the worst if it is a congestion issue. |
|
RizzleQCunningham's Law Enthusiast Premium Member join:2006-01-12 Windsor, ON |
to mt99808
Better have good ventilation in that room |
|
|
Good so far |
|
mt99808 |
to rmortier
Seriously ....wtf is going on with this? I can't even stream SD video. |
|
JakeG join:2013-02-23 Chatham, ON |
to rmortier
Once again another night of high pings where its useless to play any games or watch netflix:
Tracing route to google.com [74.125.226.132] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 7 ms 8 ms 9 ms 10.194.140.1 3 101 ms 101 ms 98 ms 192-171-60-26.cpe.pppoe.ca [192.171.60.26] 4 98 ms 97 ms 97 ms ae3_2553-bdr02-tor.teksavvy.com [192.171.60.28]
5 98 ms 102 ms 130 ms ae1_2120-bdr04-tor.teksavvy.com [69.196.136.68]
6 * 105 ms * 72.14.212.134 7 106 ms 106 ms 112 ms 209.85.255.232 8 98 ms 96 ms 97 ms 209.85.250.7 9 107 ms 107 ms 105 ms yyz08s14-in-f4.1e100.net [74.125.226.132]
Trace complete. |
|
|
They obviously have no idea what they're doing or they would respond. Just pay your bill and carry on. |
|
|
ShawnSBusiness Solutions Agent Premium Member join:2012-11-22 Chatham, ON |
ShawnS
Premium Member
2014-Sep-21 7:48 pm
Hello all, A big thanks to those who have provided us with traceroutes. This issue is still being investigated, We would like to see more traceroutes if possible. said by TSI Gabe:Can you continue posting traceroutes. Google.com is fine. Thank you for your patience as we work towards resolving this issue. Warm regards, Shawn S |
|
RizzleQCunningham's Law Enthusiast Premium Member join:2006-01-12 Windsor, ON Ubiquiti UDM-Pro Ubiquiti U6-LR
|
RizzleQ
Premium Member
2014-Sep-21 9:14 pm
Here's today's peak time traceroute taken seconds ago: Tracing route to google.com [74.125.226.136] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router [192.168.1.1]
2 8 ms 8 ms 6 ms 10.195.236.1
3 115 ms 114 ms 114 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10]
4 109 ms 108 ms 112 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 116 ms 116 ms 114 ms ae0_2140-bdr04-tor.teksavvy.com [69.196.136.132]
6 * 116 ms 108 ms 72.14.212.134
7 115 ms 113 ms 109 ms 209.85.255.232
8 117 ms 117 ms 107 ms 209.85.250.7
9 113 ms 107 ms 103 ms yyz08s14-in-f8.1e100.net [74.125.226.136]
Trace complete.
|
|
|
to rmortier
Tracing route to google.com [173.194.46.101] over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.1.1 2 10 ms 12 ms 9 ms 10.194.140.1 3 124 ms 322 ms 206 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10] 4 145 ms 290 ms 200 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 235 ms 132 ms 209 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]
6 * 197 ms 222 ms 72.14.212.134 7 116 ms 178 ms 128 ms 209.85.255.232 8 386 ms 131 ms 132 ms 216.239.46.162 9 174 ms 198 ms 136 ms 209.85.254.241 10 156 ms 212 ms 204 ms 209.85.245.225 11 135 ms 135 ms 277 ms ord08s13-in-f5.1e100.net [173.194.46.101]
Trace complete. |
|
mt99808 |
to rmortier
Tracing route to facebook.com [173.252.110.27] over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.1.1 2 11 ms 10 ms 10 ms 10.194.140.1 3 118 ms 118 ms 144 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10] 4 253 ms 119 ms 121 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 121 ms 212 ms 115 ms ae0_2140-bdr04-tor.teksavvy.com [69.196.136.132]
6 319 ms 120 ms 287 ms 10ge2-1.core2.tor1.he.net [216.66.39.113] 7 129 ms 129 ms 130 ms 10ge15-1.core1.chi1.he.net [184.105.213.150] 8 * * * Request timed out. 9 298 ms 200 ms 203 ms 74.119.76.222 10 230 ms 203 ms 203 ms 173.252.64.171 11 151 ms 155 ms 266 ms be2.bb02.frc3.tfbnw.net [204.15.22.224] 12 158 ms 154 ms 315 ms ae88.dr04.frc1.tfbnw.net [173.252.64.193] 13 * * * Request timed out. 14 * * * Request timed out. 15 149 ms 199 ms 204 ms edge-star-shv-13-frc1.facebook.com [173.252.110. 27]
Trace complete.
Tracing route to pokerstars.com [77.87.181.63] over a maximum of 30 hops:
1 4 ms 4 ms 3 ms 192.168.1.1 2 11 ms 11 ms 15 ms 10.194.140.1 3 144 ms 228 ms 123 ms 192-171-60-26.cpe.pppoe.ca [192.171.60.26] 4 207 ms 255 ms 106 ms ae3_2553-bdr02-tor.teksavvy.com [192.171.60.28]
5 114 ms 112 ms 115 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]
6 134 ms 202 ms 147 ms xe-2-2-1.cr1.tor1.ca.as4436.gtt.net [69.31.143.1 25] 7 117 ms 121 ms 135 ms ae2-69.tor10.ip4.gtt.net [46.33.80.241] 8 356 ms 405 ms 211 ms xe-9-0-1.par70.ip4.gtt.net [89.149.185.141] 9 406 ms 220 ms 388 ms ae0-69.cr1-cdg1.ip4.gtt.net [46.33.95.238] 10 228 ms 340 ms 250 ms as6762.xe-0-0-2.cr1.cdg1.fr.as4436.gtt.net [69.2 2.139.50] 11 215 ms 224 ms 205 ms xe-8-3-0.londra32.lon.seabone.net [89.221.43.119 ] 12 356 ms 215 ms 212 ms rational-service.londra32.lon.seabone.net [195.2 2.209.126] 13 * * * Request timed out. 14 368 ms 405 ms 225 ms 77.87.177.169 15 * * * Request timed out. 16 299 ms * * 77.87.180.14 17 260 ms 211 ms 211 ms 77.87.181.63
Trace complete.
|
|
|
to mt99808
OMG make it stop. Every night at primetime for the last ~two months! I opened a ticket and it went away for a few days and now it's back!
Tracing route to google.com [74.125.226.104] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1] 2 21 ms 7 ms 7 ms xx.xx.xx.xx 3 * 29 ms 19 msvl-201.gw03.ym.phub.net.cable.rogers.com [66.185.90.17] 4 * 21 ms 22 ms gi-1-1-3.gw01.grnsbr.phub.net.cable.rogers.com [24.153.7.5] 5 18 ms * * ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36] 6 18 ms * * 72.14.212.134 7 16 ms 17 ms 18 ms 216.239.47.114 8 16 ms * 20 ms 209.85.250.207 9 * * 20 ms yyz08s13-in-f8.1e100.net [74.125.226.104]
Trace complete. |
|
Charlee Premium Member join:2013-09-05 canada |
Charlee
Premium Member
2014-Sep-21 9:32 pm
said by Treegravy:3 * 29 ms 19 msvl-201.gw03.ym.phub.net.cable.rogers.com [66.185.90.17] 4 * 21 ms 22 ms gi-1-1-3.gw01.grnsbr.phub.net.cable.rogers.com [24.153.7.5] Looks like your not part of the issue that this thread is talking about. You appear to be on rCable, not cCable and may want to look at troubleshooting/ opening a ticket in the direct. |
|
|
Wow, my internet is fucking terrible right now. So glad I'm paying these idiots EIGHTY FUCKING DOLLARS A MONTH. |
|
rmortier |
Seriously, I can't stream shit, I can't play games. I can't even fucking do work stuff. |
|
rmortier |
FUCK |
|
jonana join:2000-08-05 Saint-Laurent, QC |
to ShawnS
Same situation here in Montreal area, every evening between ~7-11pm
Tracing route to www.google.com [74.125.226.148] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 33 ms 33 ms 35 ms 206.248.154.104 3 33 ms 31 ms 30 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]
4 * * * Request timed out. 5 31 ms 30 ms 30 ms 209.85.255.232 6 31 ms 48 ms 31 ms 209.85.250.7 7 30 ms 30 ms 30 ms yyz08s14-in-f20.1e100.net [74.125.226.148]
Trace complete.
Tracing route to www.google.com [74.125.226.115] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 36 ms 35 ms 37 ms 206.248.154.104 3 32 ms 52 ms 30 ms ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
4 * 30 ms 32 ms 72.14.212.134 5 30 ms 83 ms * 216.239.47.114 6 31 ms 30 ms 33 ms 209.85.250.207 7 30 ms 30 ms 32 ms yyz08s13-in-f19.1e100.net [74.125.226.115]
Trace complete. |
|
RizzleQCunningham's Law Enthusiast Premium Member join:2006-01-12 Windsor, ON Ubiquiti UDM-Pro Ubiquiti U6-LR
|
to rmortier
Here's an idea: Instead of cursing and doing absolutely nothing to help the problem, you be civil and help by posting traceroutes every day during peak hours when the problem surfaces. Thank you |
|
|
to rmortier
I'm convinced they literally have no clue what the issue is.
Other than the obvious .... uhhh .... Cogeco's fault!!!! |
|
|
Tracing route to dslreports.com [64.91.255.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gateway [10.42.23.1]
2 7 ms 7 ms 6 ms 10.194.140.1
3 115 ms * 115 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10]
4 118 ms 122 ms 114 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 113 ms 114 ms 116 ms ae3_2150-bdr03-tor.teksavvy.com [69.196.136.163]
6 121 ms 119 ms 106 ms 10ge15-2.core1.tor1.he.net [209.51.184.253]
7 126 ms 125 ms 125 ms 100ge13-1.core1.chi1.he.net [184.105.80.5]
8 * * * Request timed out.
9 126 ms 123 ms 126 ms lw-dc3-core2-vlan66.rtr.liquidweb.com [209.59.157.226]
10 141 ms 133 ms 135 ms lw-dc3-dist15-po6.rtr.liquidweb.com [69.167.128.243]
11 129 ms 126 ms 126 ms www.dslreports.com [64.91.255.98]
Trace complete.
Tracing route to netflix.com [69.53.236.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gateway [10.42.23.1]
2 7 ms 7 ms 7 ms 10.194.140.1
3 112 ms 116 ms 116 ms 192-171-60-26.cpe.pppoe.ca [192.171.60.26]
4 * 113 ms 112 ms ae3_2553-bdr02-tor.teksavvy.com [192.171.60.28]
5 119 ms 117 ms * ae1_2120-bdr04-tor.teksavvy.com [69.196.136.68]
6 104 ms 108 ms * ix-0-0-2-0.tcore1.tnk-toronto.as6453.net [64.86.33.21]
7 183 ms 209 ms 207 ms if-0-0-0-4.core4.tnk-toronto.as6453.net [63.243.172.29]
8 124 ms 126 ms 138 ms if-0-3-2-0.tcore1.ct8-chicago.as6453.net [63.243.172.34]
9 130 ms 130 ms 130 ms p5-1.ir1.chicago2-il.us.xo.net [206.111.2.33]
10 181 ms 184 ms 183 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
11 180 ms 185 ms 186 ms te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]
12 188 ms 185 ms 174 ms te-3-0-0.rar3.sanjose-ca.us.xo.net [207.88.12.58]
13 169 ms 172 ms 177 ms ae0.cir1.sanjose2-ca.us.xo.net [207.88.13.73]
14 179 ms 180 ms 181 ms 216.156.85.46.ptr.us.xo.net [216.156.85.46]
15 182 ms 180 ms 173 ms xe-2-2-0-954.jnrt-edge01.prod1.netflix.com [69.53.225.26]
16 184 ms 180 ms 179 ms te1-8.csrt-agg01.prod1.netflix.com [69.53.225.6]
17 184 ms 183 ms 182 ms www.trynetflix.com [69.53.236.17]
Trace complete.
Tracing route to samsung.ca [206.67.236.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gateway [10.42.23.1]
2 8 ms 6 ms 7 ms 10.194.140.1
3 112 ms 111 ms 117 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10]
4 113 ms 111 ms 117 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 116 ms 130 ms 117 ms ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
6 108 ms 111 ms 110 ms 10ge2-1.core2.tor1.he.net [216.66.39.113]
7 121 ms 129 ms 132 ms 10ge1-1.core1.nyc5.he.net [72.52.92.49]
8 118 ms 115 ms 126 ms 10ge6-1.core1.nyc6.he.net [72.52.92.101]
9 128 ms 129 ms 126 ms 198.32.160.145
10 129 ms 128 ms 123 ms u122.ppp66.samsung.co.kr [157.197.66.122]
11 137 ms 127 ms 141 ms u35.ppp70.samsung.co.kr [157.197.70.35]
12 125 ms 126 ms 130 ms 208.248.44.66
13 128 ms 123 ms 121 ms 208.248.44.73
14 121 ms 120 ms 121 ms samsungcamerausa.com [206.67.236.26]
Trace complete.
|
|
|
to RizzleQ
Why should we have to waste our time on here posting trace routes. If they don't know what the hell is wrong with their network I'm with the wrong ISP. |
|
RizzleQCunningham's Law Enthusiast Premium Member join:2006-01-12 Windsor, ON Ubiquiti UDM-Pro Ubiquiti U6-LR
|
RizzleQ
Premium Member
2014-Sep-21 9:55 pm
said by mt99808:Why should we have to waste our time on here posting trace routes. If they don't know what the hell is wrong with their network I'm with the wrong ISP. Because the person who is capable of fixing the problem asked us to. How is that a waste of time? It takes seconds to do it and post it. |
|
|
to rmortier
If he was capable of fixing it he would have done it already |
|
mt99808 |
to rmortier
Teksavvy is so good for months and then there's always shit like this where they have no clue what the hell is going on. And it goes on for weeks. |
|
|
to RizzleQ
Yeah man, totally reasonable. Let's just fix this bullshit, the same bullshit we've been dealing with over a year. Remember January through May? I do, I know you do too because I remember you posting. Remember September 2013? I do. I know you do too. It's impossible to get stable internet in Chatham it seems. It's exhausting because friends on Cogeco in the Blenheim and Windsor areas have zero problems but since I'm not about to sign up with a Cogeco contract + hidden fees, I have to suffer with this mess every 3 months. |
|
|
mt99808
Member
2014-Sep-21 10:00 pm
said by rmortier:Yeah man, totally reasonable. Let's just fix this bullshit, the same bullshit we've been dealing with over a year. Remember January through May? I do, I know you do too because I remember you posting. Remember September 2013? I do. I know you do too. It's impossible to get stable internet in Chatham it seems. It's exhausting because friends on Cogeco in the Blenheim and Windsor areas have zero problems but since I'm not about to sign up with a Cogeco contract + hidden fees, I have to suffer with this mess every 3 months. What he said |
|
|
to RizzleQ
said by RizzleQ:Because the person who is capable of fixing the problem asked us to. How is that a waste of time? It takes seconds to do it and post it. It's a waste of time because this is an ongoing issue that just keeps reoccuring and it lasts for weeks/months. |
|
rmortier |
I even moved in May because I was tired of the shitty internet on the other side of Chatham and I fucking MOVED to the other side of Chatham because people had said it was only my area. What a waste that turned out to be. |
|
|
mt99808
Member
2014-Sep-21 10:08 pm
I'm in Prestancia .... they told me there's no congestion in this part of Chatham. Other parts yes but definitely not where I am. mmmmkk |
|
|
Haha, wow. It has to be all of Chatham then because I'm over by Teppermans now, and prior I used to be on Riverview near Union Gas. |
|