Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Burst again
Burst again
| Posted by John[H4Y], 06-29-2006, 09:55 AM |
|
Oh no.. packet loss!!
|
| Posted by macdonaldp, 06-29-2006, 10:00 AM |
|
What ip addresses are you getting packet loss on? I've pinged burst.net and it seems to be fine from my end.
|
| Posted by John[H4Y], 06-29-2006, 10:05 AM |
|
Try pinging burst.net again. You will see the packetloss.. Seems they are already aware of the issue.
|
| Posted by macdonaldp, 06-29-2006, 10:06 AM |
|
Nope. Tried here http://www.dnsstuff.com/tools/ping.ch?ip=burst.net as well as on my home machine. No packet loss at all.
|
| Posted by Equonix, 06-29-2006, 10:07 AM |
|
Looks like theres problems with BTN.
Tracing route to burst.net [66.96.192.201]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 9 ms 10.36.64.1
3 8 ms 7 ms 10 ms gsr01-sl.blueyonder.co.uk [62.30.65.33]
4 19 ms 19 ms 20 ms 195.188.230.93
5 11 ms 11 ms 11 ms 195.188.230.26
6 11 ms 11 ms 13 ms 194.117.136.233
7 10 ms 12 ms 10 ms 194.117.136.146
8 50 ms 12 ms 256 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
9 * * * Request timed out.
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
|
| Posted by macdonaldp, 06-29-2006, 10:11 AM |
|
Well I must not be having problems from my end to burst because when I do a trace it doesn't time out.
Tracing route to burst.net [66.96.192.201]
over a maximum of 30 hops:
1 26 ms 23 ms 24 ms 68.150.21.1
2 25 ms 23 ms 23 ms rc2ar-ge9-0-1.ed.shawcable.net [64.59.189.35]
3 24 ms 24 ms 23 ms rc1ar-ge12-0-0.ed.shawcable.net [66.163.70.17]
4 43 ms 41 ms 41 ms rc1bb-pos13-0.vc.shawcable.net [66.163.76.161]
5 45 ms 47 ms 47 ms rc1wt-pos4-0-0.wa.shawcable.net [66.163.76.126]
6 47 ms 48 ms 47 ms ge3-0.cr02.sea01.pccwbtn.net [198.32.180.13]
7 113 ms 112 ms 114 ms pos5-2.cr01.phl02.pccwbtn.net [63.218.30.45]
8 115 ms 113 ms 113 ms hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net [63.218.3
1.6]
9 117 ms 119 ms 119 ms ge1-oc48-1-0-ctsi.rtr0.scr1.hostnoc.net [66.197.
191.1]
10 115 ms 119 ms 119 ms burst.net [66.96.192.201]
Trace complete.
I'm sure a BurstNET rep will chime in here to clarify things.
Last edited by macdonaldp; 06-29-2006 at 10:15 AM.
|
| Posted by bhaputi, 06-29-2006, 10:18 AM |
|
At this point it would definitely matter which connection you come in over. We are being attacked again by some bored script-kiddy. Our Toplayers are stopping it for the most part, but the connections that the flood is coming in over are seeing some loss - at this point it seems to be isolated to Yipes.
|
| Posted by bhaputi, 06-29-2006, 11:15 AM |
|
This has been taken care of. We were being flooded, mainly over our Yipes connection, causing issues for some customers who connect via Yipes. Everything should be back to normal now.
|
| Posted by John[H4Y], 06-29-2006, 11:17 AM |
|
Thank you Dan.
|
Add to Favourites 
Print this Article
Also Read
Nixcom is down (Views: 1015)
Shared Hosting
Shared Hosting
