Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Burst.net's Outage - 64.191.xx.xx range possibly affected
Burst.net's Outage - 64.191.xx.xx range possibly affected
| Posted by RDOSTI, 10-11-2009, 06:44 AM |
64.191.xx.xx Outage seems to be going on. Network is extremely slow-on and off. Tech support has informed me it is "possible" that there is a localized network issue.
This is currently passed an hour. I am awaiting an update from Burst and hopefully good news soon. Is anyone else being affected at this time? |
| Posted by NWSTech, 10-11-2009, 06:57 AM |
|
im on VD's network with 64.191.50.xxx ips range and my servers up although it has been a bit unstable last few days |
| Posted by RDOSTI, 10-11-2009, 07:33 AM |
|
Its been solved or so I beieve. This may be closed. (localized issue) |
| Posted by roro, 10-12-2009, 12:38 PM |
I cant upload files, its extremely slow!
Im in 66 range |
| Posted by 314Hosting, 10-26-2009, 05:11 AM |
|
This net rang was down again few minutes ago. |
| Posted by ishan, 10-26-2009, 07:24 AM |
|
We faced this both times. Only 1 server in this range. There was a long downtime yesterday in another range. Is the NEW NETWORK already going bad? |
| Posted by BurstNET, 10-26-2009, 09:57 PM |
Network has NOT been down, though there has been a few large ddos attacks the past few days. Possibly you were coming in across one of the circuits with heavy incoming ddos traffic...
.
. |
| Posted by ishan, 10-26-2009, 11:44 PM |
Here is what your support says (Oct 13th)-
-----------------------------------------------
(Matt W)
-----------------------------------------------
There was a network issue on Sunday. Our networking department was informed and was able to get it resolved.
Then again on Oct 25th-
-----------------------------------------------
(Jamey B.)
-----------------------------------------------
We have an issue with one of our major switches, Our networking department is working on replacing one of the boards to get our clients back online. You should be back up within the hour.
Both downtimes around 2 hours. |
| Posted by BurstNET, 10-26-2009, 11:49 PM |
Neither of those were network-wide issues, I am aware of them. They were localized to specific distribution switches. To say burstnet was down, or the network was down, is inaccurate.
Proof: http://www.hyperspin.com/publicreport/57207/7765
And those 20 minutes were due to the burst.net server, which is what is being monitored, down for some maintenance.
.
. |
| Posted by ishan, 10-26-2009, 11:51 PM |
|
Even though they were not network wide (which is true, as we could access support), they were still downtimes & 4 hours in a month is not good for business. |
| Posted by BurstNET, 10-26-2009, 11:57 PM |
Quote:
|
Originally Posted by ishan
Even though they were not network wide (which is true, as we could access support), they were still downtimes & 4 hours in a month is not good for business.
|
We have NOT had 4 hours downtime on any particular portion of our network either. Maybe you had an issue on a specific service you have, due to some cause/problem, but it was not a entire network portion. I don't know details of your particular situation, but I do know no particular portion of our network, even for the distribution switch that failed.
.
. |
| Posted by ishan, 10-27-2009, 12:03 AM |
This thread is not flame burstnet, or we wouldnt have servers with you. There were problems which we faced, 2 of roughly 2 hours each. You can see the 2 tech replies above. I am not going to reply again to this post, but you need to buck up the service instead of trying to prove yourself.
The support & sales departments have been outstanding, but these 2 downtimes have made october a bad month (earlier months were really good.)
As above posts say , the 64.191.xx.xx range & not the whole network has had 2 downtimes & another in the vps section.
Ishan
|
| Posted by BurstNET, 10-27-2009, 12:16 AM |
Quote:
|
Originally Posted by ishan
This thread is not flame burstnet, or we wouldnt have servers with you. There were problems which we faced, 2 of roughly 2 hours each. You can see the 2 tech replies above. I am not going to reply again to this post, but you need to buck up the service instead of trying to prove yourself.
The support & sales departments have been outstanding, but these 2 downtimes have made october a bad month (earlier months were really good.)
As above posts say , the 64.191.xx.xx range & not the whole network has had 2 downtimes & another in the vps section.
Ishan
|
When a statement is made that the network is down, or a network outage, we have to correct the falsehood. You may have a service that had some issues, but that is localized to you, and not a "network issue".
It is absolutely impossible that 64.191.xx.xx was all down. The block is not serviced on just one portion of the network, The block is completely spread throughout our entire facility, just like every other IP block we own. Maybe some ISP upstream or something blocked the route to 64.191.xx.xx temporarily...that would be a possible explanation, and something we have seen before. However, without a complete network outage, there is no way 64.191.xx.xx was down, and not any other ranges at the same---just not possible.
.
. |
| Posted by BurstNET, 10-27-2009, 12:20 AM |
There is absolutely nothing wrong with our network or service levels provided this month. One distribution switch outage (can, and will, happen anywhere and at any time, to any provider...distribution switches typically are not redundant, while aggregation switches, including ours, are...), and a couple ddos attacks that slowed things abit without taking us down, do not make for a bad month of service. We have had near perfect service on our network since it was upgraded/replaced, and that has not changed, and neither of these things influence that whatsoever.
.
. |
| Posted by w4Net, 10-27-2009, 12:24 AM |
We have IP's on the 64.191.x range and I can confirm we had no downtime at all.
We never had any clients email in nor did we have to contact Burst. So I am going to go with Burst on this one that either an ISP blocked the route or it was an issue with your service. |
| Posted by BurstJoeM, 10-27-2009, 10:02 PM |
|
Can anyone who is having problems provide any details (times, traceroutes, etc)? I havent recieved any tickets, so I have nothing to go on.on. |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
