|
to ragingwolf
Re: More cable issues?Experiencing a lot of packet loss in Brampton, this is 4 days straight all after 5pm. |
|
|
to ragingwolf
Issues loading files from dropbox. downtown toronto cable. |
|
TSI GabeRouter of Packets Premium Member join:2007-01-03 Gatineau, QC |
TSI Gabe
Premium Member
2014-Mar-31 7:37 pm
looking into it right npw |
|
|
|
to ragingwolf
Everything is ungodly.
Nothing loads.
April Fools is tomorrow, not today =/ |
|
Newfie join:2001-05-08 Toronto, ON |
to ragingwolf
Yep. Another slow night here. Crazy amounts of packet loss on nLayer tonight. Major issues between nLayer and Tinet too. traceroute to dallas-ventrilo.nfoservers.com (66.150.214.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.737 ms 3.792 ms 3.410 ms
2 10.126.185.129 (10.126.185.129) 13.365 ms 8.708 ms 8.293 ms
3 209.148.245.193 (209.148.245.193) 21.582 ms 22.916 ms 23.928 ms
4 69.63.248.185 (69.63.248.185) 10.900 ms 11.946 ms 11.361 ms
5 69.196.136.132 (69.196.136.132) 12.350 ms 11.309 ms 14.394 ms
6 xe-3-0-1.cr1.tor1.ca.nlayer.net (69.31.143.141) 12.058 ms 10.909 ms 16.108 ms
7 ae2-50.tor10.ip4.tinet.net (199.229.230.89) 189.567 ms 33.153 ms *
8 xe-1-2-0.dal40.ip4.tinet.net (89.149.187.34) 237.375 ms 79.231 ms 114.686 ms
9 internap-gw.ip4.tinet.net (77.67.70.66) 63.442 ms 64.660 ms 115.694 ms
10 border1.pc-1-bbnet1.ext1a.dal.pnap.net (216.52.191.24) 59.730 ms
border2.pc-1-bbnet1.ext1a.dal.pnap.net (216.52.191.25) 58.177 ms
border2.pc-2-bbnet2.ext1a.dal.pnap.net (216.52.191.85) 173.408 ms
11 dallas-ventrilo.nfoservers.com (66.150.214.8) 58.839 ms 63.728 ms *
|
|
Viscera join:2005-05-03 North Bay, ON |
to ragingwolf
More info if it helps...
Pings to facebook.com:
Round-Trip: 254.586 min, 258.554 avg, 266.778 max (ms) Packets: 50 transmitted, 27 received, 46% lost
Seq Address RX Bytes TTL RTT (ms) +/- (ms) 0 facebook.com (173.252.110.27) 64 82 259.63 2 facebook.com (173.252.110.27) 64 82 259.28 -0.35 3 facebook.com (173.252.110.27) 64 82 256.27 -3.01 4 facebook.com (173.252.110.27) 64 82 257.39 1.13 8 facebook.com (173.252.110.27) 64 82 254.59 -2.80 9 facebook.com (173.252.110.27) 64 82 255.75 1.16 10 facebook.com (173.252.110.27) 64 82 259.68 3.93 16 facebook.com (173.252.110.27) 64 82 255.76 -3.92 18 facebook.com (173.252.110.27) 64 82 259.99 4.23 22 facebook.com (173.252.110.27) 64 82 259.95 -0.04 24 facebook.com (173.252.110.27) 64 82 262.20 2.25 26 facebook.com (173.252.110.27) 64 82 261.21 -0.99 27 facebook.com (173.252.110.27) 64 82 257.74 -3.47 30 facebook.com (173.252.110.27) 64 82 256.32 -1.42 31 facebook.com (173.252.110.27) 64 82 256.51 0.19 32 facebook.com (173.252.110.27) 64 82 260.50 3.99 33 facebook.com (173.252.110.27) 64 82 260.59 0.09 34 facebook.com (173.252.110.27) 64 82 266.78 6.19 35 facebook.com (173.252.110.27) 64 82 260.83 -5.95 36 facebook.com (173.252.110.27) 64 82 257.39 -3.44 39 facebook.com (173.252.110.27) 64 82 254.63 -2.76 40 facebook.com (173.252.110.27) 64 82 255.57 0.94 41 facebook.com (173.252.110.27) 64 82 258.58 3.01 44 facebook.com (173.252.110.27) 64 82 256.70 -1.88 45 facebook.com (173.252.110.27) 64 82 258.78 2.08 47 facebook.com (173.252.110.27) 64 82 258.18 -0.60 49 facebook.com (173.252.110.27) 64 82 260.15 1.97
Pings to amazon.ca: Packets: 50 transmitted, 0 received, 100% lost
Pings to google.ca are perfect though. A lot of various websites simply refuse to load at all.
As far as the Tracert to amazon.ca from my router goes: Hop Address Min (ms) Max (ms) Avg (ms) +/- (ms) 1 10.207.12.1 8.23 10.80 9.19 2 192-171-63-10.cpe.pppoe.ca (192.171.63.10) 18.39 18.89 18.59 9.40 3 192-171-63-11.cpe.pppoe.ca (192.171.63.11) 17.54 36.22 23.84 5.24 4 69.196.136.132 17.13 18.86 17.96 -5.88 5 10ge1-2.core2.tor1.he.net (209.51.191.173) 18.09 18.91 18.47 0.51 6 10ge1-1.core1.ymq1.he.net (184.105.222.94) 47.89 51.67 50.03 31.56 7 10ge14-4.core1.nyc4.he.net (184.105.222.97) 57.63 69.23 62.61 12.58 8 100ge5-1.core1.ash1.he.net (184.105.223.165) 245.14 245.14 245.14 182.53 |
|
|
to ragingwolf
same here, downtown TO |
|
|
to TSI Gabe
Looked into it for you, hurricane electric is down, now please reroute. |
|
1 edit |
to ragingwolf
Recent test. This one had a lot less timeouts than my previous tests.
Tracing route to any-rc.a01.yahoodns.net [98.139.102.145]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 22 ms 23 ms 21 ms 209.148.242.185
4 12 ms 15 ms 20 ms 69.63.249.185
5 12 ms 14 ms 11 ms 69.196.136.68
6 11 ms 14 ms 17 ms xe-3-0-1.cr1.tor1.ca.nlayer.net [69.31.143.141]
7 97 ms 149 ms 98 ms xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77]
8 * * * Request timed out.
9 51 ms 60 ms 52 ms ae-8.pat2.bfz.yahoo.com [216.115.101.147]
10 50 ms 49 ms 51 ms ae-4.msr2.bf1.yahoo.com [216.115.100.73]
11 * 384 ms 303 ms UNKNOWN-98-139-128-X.yahoo.com [98.139.128.19]
12 523 ms 307 ms 291 ms et-18-25.fab2-1-gdc.bf1.yahoo.com [98.139.128.55
]
13 56 ms 53 ms 57 ms po-10.bas2-1-prd.bf1.yahoo.com [98.139.129.31]
14 54 ms 50 ms 53 ms w2.rc.vip.bf1.yahoo.com [98.139.102.145]
Trace complete.
New test a couple of minutes later.
Tracing route to any-rc.a01.yahoodns.net [98.139.102.145]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 12 ms 22 ms 22 ms 209.148.242.185
4 14 ms 14 ms 14 ms 69.63.249.185
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * 221 ms ae0-30g.cr1.nyc2.us.nlayer.net [69.31.95.122]
9 249 ms 197 ms 198 ms xe-1-2-1.cr2.ord1.us.nlayer.net [69.22.142.85]
10 * 125 ms 141 ms ae0-60g.cr2.ord1.us.nlayer.net [69.31.111.154]
11 * * * Request timed out.
12 239 ms 251 ms 246 ms ae-8.pat2.bfz.yahoo.com [216.115.101.147]
13 228 ms * 174 ms ae-4.msr1.bf1.yahoo.com [216.115.100.25]
14 243 ms 242 ms 183 ms UNKNOWN-98-139-130-X.yahoo.com [98.139.130.13]
15 90 ms 91 ms 92 ms w2.rc.vip.bf1.yahoo.com [98.139.102.145]
Trace complete.
|
|
|
to ragingwolf
First I was having problems loading Facebook. Now deviantArt isn't wanting to load anything. I'm in South London. |
|
ReeG join:2012-02-27 North York, ON |
ReeG
Member
2014-Mar-31 7:48 pm
whew glad it's not just me. |
|
|
to ragingwolf
Tracing route to 63.240.104.93 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1 2 9 ms 8 ms 9 ms 10.126.96.1 3 11 ms 11 ms 11 ms 66.185.91.29 4 12 ms 11 ms 11 ms 69.63.251.190 5 * * * Request timed out. 6 * * 12 ms xe-2-2-1.cr1.tor1.ca.nlayer.net [69.31.143.125]
7 * 40 ms * xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77] 8 114 ms 116 ms * ae2-30g.ar2.ord1.us.nlayer.net [69.31.111.150] 9 55 ms 52 ms 58 ms as2914.ae11.ar2.ord1.us.nlayer.net [69.31.111.21 1] 10 54 ms 47 ms 54 ms 192.205.32.193 11 71 ms 63 ms 71 ms cr2.cgcil.ip.att.net [12.122.132.198] 12 89 ms 69 ms 69 ms cr1.n54ny.ip.att.net [12.122.1.1] 13 69 ms 69 ms 64 ms gar1.nw2nj.ip.att.net [12.122.131.81] 14 62 ms 100 ms 69 ms 12.122.251.10 15 73 ms 66 ms 69 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.24 0.65.22] 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
Area 52 server of WoW. Latency is getting hammered. My latency has been higher than normal on the world servers already. Imagine how surprised I was to find myself sitting at 73 ms home / 1245 ms world |
|
|
to ragingwolf
Using Tunnelbear VPN app (Toronto developed, i believe) on my Android while connected to wifi, am able to visit the sites that were giving me problems.
Urge to kill, subsiding... |
|
|
to jdrom
Same.. Origin wont even load my games, BUT usenet seems to be fine. Some random sites seem to be very slow as well (dsl, oshawa) |
|
|
to ragingwolf
NHaving same probably in KiTchener,what is Rogers up to |
|
|
Hamilton here, same issues described. |
|
TSI Marc Premium Member join:2006-06-23 Chatham, ON |
TSI Marc
Premium Member
2014-Mar-31 8:20 pm
Man. I knew it. It was nice and sunny today in Chatham. Too good to be true. Sheesh. Really sorry for the disruption gang. |
|
|
At least its not just a tsi issue. I can connect to origin fine now but dslreports wont load now lol. ( using my phone to axs this site now)
EDIT: went from no load, to lightning fast again... the internet gods are not happy? |
|
|
to ragingwolf
Lol - Can no longer access DSLreports via computer. Am loving access using VPN. Had never used it on my phone, and became inspired when I read an article about Twitter being blocked in Turkey. Quite useful. » www.cbc.ca/m/news/#!/con ··· .2588110 |
|
TSI Andre Premium Member join:2008-06-03 Chatham, ON |
to ragingwolf
|
|
|
to ragingwolf
lol. Is it even possible to get stable internet in southern Ontario? Like I'd pay extra if there was such a thing. |
|
damir join:2013-12-12 CANADA |
damir
Member
2014-Mar-31 8:55 pm
... the question is ... WHAT is next ............... |
|
TSI Andre Premium Member join:2008-06-03 Chatham, ON
1 recommendation |
I hope that it rains timbits next |
|
|
to ragingwolf
Having trouble loading up sites on Cable as well. |
|
|
to ragingwolf
Sadness in Kitchener ping wikipedia.org -n 100
Pinging wikipedia.org [208.80.154.224] with 32 bytes of data:
...
Ping statistics for 208.80.154.224:
Packets: Sent = 100, Received = 58, Lost = 42 (42% loss),
Approximate round trip times in milli-seconds:
Minimum = 235ms, Maximum = 252ms, Average = 240ms
|
|
|
to Trollnado
London, Ontario here issues similar to what was happening on the weekend. Lots of packet loss and slow connectivity. Tracing route to www.netflix.com [67.216.222.14]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 16 ms 7 ms 8 ms 10.125.128.1
3 15 ms 19 ms 15 ms 209.148.244.101
4 13 ms 23 ms 14 ms gw01.hnsn.phub.net.cable.rogers.com [66.185.80.25]
5 13 ms 21 ms 15 ms 2120.ae1.bdr04.tor.man.teksavvy.com.packetflow.ca [69.196.136.68]
6 14 ms 18 ms 13 ms xe-3-0-1.cr1.tor1.ca.nlayer.net [69.31.143.141]
7 54 ms 54 ms 56 ms ae10-565.cr1.nyc3.us.nlayer.net [69.22.142.218]
8 76 ms 76 ms 74 ms ae1-50g.ar2.nyc3.us.nlayer.net [69.31.95.154]
9 * 153 ms 146 ms as7843.xe-1-0-4.ar2.nyc3.us.nlayer.net [69.31.94.14]
10 50 ms 51 ms 50 ms 107.14.17.221
11 57 ms 68 ms 55 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
12 115 ms 115 ms 115 ms ae15.tr00.clevohek.mwrtn.rr.com [66.109.6.71]
13 70 ms 68 ms 74 ms Unknown.UNGVWIYKVL-DAR1.mw.twcbiz.com [65.189.182.91]
14 76 ms 60 ms 71 ms rrcs-67-52-56-10.west.biz.rr.com [67.52.56.10]
15 61 ms 74 ms 59 ms 67.216.222.14
Trace complete.
|
|
sbrook Mod join:2001-12-14 Ottawa |
to ragingwolf
It's nothing to do with what happened at the weekend ... this is a fibre failure on Hurricane Electric's links in the US. HE is a major transit provider. |
|
creed3020 Premium Member join:2006-04-26 Kitchener, ON |
to ragingwolf
Ahh this explains my my interwebs was failing very hard yesterday evening while I was trying to stream a show. I was trying everything within my network to see what the heck was going on.
I just gave up and used my LTE phone to tether. It's just as fast my rCable home connection but needs more usage to be effective. |
|
TSI Alan Premium Member join:2012-11-22 Chatham, ON |
to ragingwolf
The damaged main transit link has been repaired. Your internet speeds should be returning to normal.
Thank you for your patience and understanding. |
|