 | Can't access battle.netHello,
I can't seem to access battle.net tonight. Someone else on another ISP can, though. Here's my tracert:
Tracing route to www.battle.net [12.129.242.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 18 ms 17 ms 46 ms lo-100.erx02.tor.packetflow.ca [206.248.154.120]
3 17 ms 16 ms 16 ms 2110.ae0.bdr01.tor.packetflow.ca [69.196.136.34]
4 17 ms 21 ms 25 ms tge6-1.fr3.yyz.llnw.net [208.111.134.237]
5 80 ms 17 ms 16 ms xe-1-1-0-350.tor10.ip4.tinet.net [77.67.69.69]
6 40 ms 86 ms 41 ms xe-11-0-0.chi10.ip4.tinet.net [89.149.182.89]
7 * * * Request timed out.
-- SHARPSHARK |
|
 InssomniakThe GlitchPremium join:2005-04-06 Cayuga, ON kudos:1 | Working here (web site) on TSI DSL |
|
 Anon | reply to SHARPSHARK I am experiencing the same timeout at xe-11-0-0.chi10.ip4.tinet.net DSL with MLPPP. |
|
 Anon | Teksavvy seems to be having routing issues, hopefully it's fixed soon. |
|
 d3athTeksavvy Lover. join:2007-11-17 Windsor, ON | reply to SHARPSHARK I can't also access bluehost.com. Keeps timing out. Anyone from Teksavvy can confirm routing issue? |
|
 Anon | The auto recording on the tech support line says they are. |
|
 | reply to SHARPSHARK Oh My God, I am not getting my WoW fix, and it is Dark Moon Faire week, that's it I am heading to my room to assume the fetal position.  |
|
 | and I can't seem to access speedtest.net to check if it's still fast  |
|
 | reply to SHARPSHARK Ahhhh much better now, my wife patted me on the head and said there, there and gave me some hot chocolate, think I will go play Skyrim now. |
|
|
|
 | reply to Tenshi I am also having issues with routing tonight. |
|
 | reply to SHARPSHARK Routing issues here too on DSL. It's been going on for a couple of days. |
|
 odis172Premium join:2010-01-18 Nepean, ON | reply to SHARPSHARK As of about an hour ago, I could no longer access logmein.com Took me an hour of troubleshooting my computer/router/firewall/dns before I checked here :P |
|
 SpikePremium join:2008-05-16 Toronto, ON | reply to SHARPSHARK Been having issues with imgur.com and supermicro.com all day today. |
|
 | reply to SHARPSHARK Good to know it's not just me. I can't reach a bunch of sites right now. |
|
 | reply to SHARPSHARK Can't reach monoprice.com either...
Tracing route to monoprice.com [173.203.17.209] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 9 ms 8 ms 18 ms 10.124.7.1 3 18 ms 20 ms 20 ms 67.231.222.25 4 7 ms 8 ms 24 ms fallowfield1.cable.teksavvy.com [24.246.55.22] 5 16 ms 16 ms 15 ms fallowfield1.cable.teksavvy.com [24.246.55.17] 6 14 ms 22 ms 15 ms 10gigabitethernet1-1.core1.tor1.he.net [209.51.161.193] 7 31 ms 27 ms 27 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105.213.150] 8 * * * Request timed out. 9 * * * Request timed out. |
|
 | reply to SHARPSHARK Also just spent an hour troubleshooting my network before coming here. 
It also affects TSI themselves - their blog is only partly loading. |
|
 1 edit | reply to SHARPSHARK can't access Screwattack.com...
Ping statistics for 50.57.7.208: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Administrator>tracert www.screwattack.com
Tracing route to screwattack.com [50.57.7.208] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 128.128.128.17 2 7 ms 6 ms 5 ms 10.245.192.65 3 21 ms 23 ms 19 ms 10.170.172.121 4 22 ms 24 ms 23 ms 10.170.170.205 5 23 ms 23 ms 20 ms 10.170.171.217 6 10 ms 11 ms 11 ms 69-165-174-206.dsl.teksavvy.com [69.165.174.206]
7 19 ms 20 ms 22 ms 69-165-174-202.dsl.teksavvy.com [69.165.174.202]
8 18 ms 20 ms 19 ms 10gigabitethernet1-3.core1.tor1.he.net [216.66.3 6.97] 9 44 ms 33 ms 41 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105. 213.150] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 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. |
|
 | reply to Tenshi I thought I'd check speedtest too, to find out why everything was so slow.
No such luck.
Tracing route to www.speedtest.net [74.209.160.12] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 26 ms 13 ms 15 ms 10.125.107.129 3 19 ms 22 ms 27 ms gw01.mtth.phub.net.cable.rogers.com [66.185.89.3 3] 4 12 ms 12 ms 11 ms kitchener2.cable.teksavvy.com [69.165.168.226] 5 17 ms 16 ms 16 ms kitchener2.cable.teksavvy.com [69.165.168.225] 6 23 ms 16 ms 17 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121] 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 92 ms 76 ms * six.netriver.net [206.81.80.160] 11 80 ms 227 ms 81 ms static-74-209-160-12.lynnwood.netriver.net [74.2 09.160.12]
Trace complete. |
|
 | reply to SHARPSHARK I'm in Kitchener, and I've also seen a lot of sites timing out, like monoprice.com and imgur.com (as mentioned above). Tracert follows:
Tracing route to imgur.com [23.21.183.50] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms unknown [192.168.1.1] 2 7 ms 7 ms 8 ms 10.125.103.1 3 16 ms 15 ms 15 ms 69.63.254.193 4 9 ms 22 ms 17 ms kitchener2.cable.teksavvy.com [69.165.168.226] 5 19 ms 12 ms 14 ms kitchener1.cable.teksavvy.com [24.246.55.33] 6 12 ms 17 ms 13 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121] 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 39 ms 40 ms 39 ms equinix02-iad2.amazon.com [206.223.115.35] 12 35 ms 35 ms 36 ms 72.21.220.43 13 * 33 ms 33 ms 72.21.222.145 14 38 ms 34 ms 34 ms 216.182.224.201 15 * * * Request timed out. 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.
Not fun. |
|
 | i'm not able to access many sites tonight that route over he.net it seems to time out after that for example tfw2005.com |
|