Yet another burst.net outage? Now Shaw clients can't access burst.net

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Yet another burst.net outage? Now Shaw clients can't access burst.net

Posted by RedTechie, 06-02-2011, 11:21 PM
Any others on Shaw not able to access burst.net's services? I have clients from Canada complaining. Right after it leaves Shaw's network their connection dies.

Quote:

1 <1 ms <1 ms <1 ms 10.5.1.1
2 <1 ms <1 ms <1 ms 192.168.100.1
3 10 ms 20 ms 27 ms *.*.*.*
4 88 ms 78 ms 65 ms 64.59.157.227
5 90 ms 46 ms 58 ms rc2bb-tge0-4-2-0.vc.shawcable.net [66.163.69.57]
6 63 ms 61 ms 59 ms rc3ar-pos0-15-5-0.ed.shawcable.net [66.163.77.221]
7 81 ms 75 ms 72 ms rc1we-tge0-1-0-0.ed.shawcable.net [66.163.70.29]
8 88 ms 99 ms 96 ms 66.163.78.70
9 126 ms 122 ms 128 ms rc1sh-pos1-0-0.mt.shawcable.net [66.163.77.170]
10 133 ms 138 ms 109 ms rc1hu-pos2-0-0.ny.shawcable.net [66.163.76.54]
11 * * * Request timed out.
12 * * * Request timed out.

Posted by DeltaAnime, 06-02-2011, 11:27 PM
OK over here on Telus

Francisco
Posted by RedTechie, 06-02-2011, 11:29 PM
DeltaAnime: Correct, we have a Teamspeak server running and the clients from Telius are fine. It's only Shaw, from what I am seeing. It may be a Shaw related problem but not sure.
Posted by RedTechie, 06-02-2011, 11:32 PM
DeltaAnime: But out of curiosity could you please post your route to burst.net?
Posted by DeltaAnime, 06-02-2011, 11:56 PM

Quote:

C:\Users\Francisco>tracert burst.net

Tracing route to burst.net [66.96.192.202]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 7 ms 7 ms 6 ms d205-250-240-254.bchsia.telus.net [205.250.240.254]
3 6 ms 5 ms 6 ms 154.11.44.206
4 7 ms 6 ms 7 ms 75.154.209.19
5 13 ms 13 ms 12 ms 75.154.209.6
6 * * * Request timed out.
7 * * * Request timed out.
8 12 ms 13 ms 12 ms 204.225.243.22
9 * * * Request timed out.
10 113 ms 129 ms 112 ms vl0019.gwy02.sctn01.hostnoc.net [63.218.31.42]
11 105 ms 105 ms 107 ms xe1-02.agg01.sctn01.hostnoc.net [64.191.19.2]
12 132 ms 127 ms 127 ms burst.net [66.96.192.202]

Trace complete.

Telus blocks out a bunch of hops but i'm assuming it's routing through the west coast

Francisco
Posted by RedTechie, 06-02-2011, 11:58 PM
DeltaAnime: Thanks!

It looks like the problem may have stabilized now. It may have well just been Shaw's NY hop as it's the hop that is directly adjacent to burst.net's core router.