Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Burst.net down?
Posted by Kjtocool, 06-18-2013, 08:32 PM I run a dedicated box with Burst.net and it's offline, I tried going to Burst.net to open a support ticket, and it's down as well. Can anyone confirm?
Posted by bear, 06-18-2013, 08:36 PM I can reach Burst, but I have a server that's popping in and out for the last 15 minutes or so.
Posted by Patrick, 06-18-2013, 08:36 PM Yeah, our NAGIOS is going crazy with alerts... awesome.
Posted by HostcrateCEO, 06-18-2013, 08:40 PM My servers are acting as if they are up but I am receiving notifications they are down and also licensing errors. I will be contacting them myself now.Quote:
Originally Posted by KjtocoolI run a dedicated box with Burst.net and it's offline, I tried going to Burst.net to open a support ticket, and it's down as well. Can anyone confirm?
Posted by RobM, 06-18-2013, 08:41 PM only 1 colo going crazy every now and then others doing ok. I just talk to my NY office and they are reporting the hwng.net loop not doing so hot...
I am seeing the same in PA lot's of timeouts / fails on hwig.net route.
Posted by Senator B, 06-18-2013, 08:49 PM Down for about 45 minutes here.
Posted by MaxLock, 06-18-2013, 09:00 PM Completely out of breath, I can not access the site burst.net
Region: Brazil
Posted by MaxLock, 06-18-2013, 09:40 PM https://twitter.com/search/realtime?q=burstnet&src=typd
Posted by lemon09, 06-18-2013, 09:47 PM It is down from some international location. It is accessible in US.
Posted by HostcrateCEO, 06-18-2013, 09:50 PM Ours are located in the US and are experiencing the same issues. Half my clients can access their accounts via the control panel, the other half cannot. Some are receiving licensing errors as we use the WHMSonic software, others aren't.Quote:
Originally Posted by lemon09It is down from some international location. It is accessible in US.
Posted by Senator B, 06-18-2013, 09:54 PM Last I checked, my server and I are in the US, and I can't access anything. Not even responding to pings.Quote:
Originally Posted by lemon09It is down from some international location. It is accessible in US.
Posted by FRH Lisa, 06-18-2013, 10:01 PM There appears to be an issue somewhere between Highwinds and Comcast. We have a lot of Comcast customers reporting that they are unable to reach servers in the Scranton datacenter, and all traceroutes from those customers die at unknown.hwng.net [205.185.198.130].
Our office uses FIOS, and we can hit the DC just fine. Same on our 4G Verizon hotspots. I don't know what's going on behind the scenes, but it appears to be ONLY affecting Comcast customers and other ISPs that route through Highwinds. Can anyone else confirm?
Any other DCs fed by Highwinds reporting any trouble?
Posted by Purevoltage, 06-18-2013, 10:02 PM We noticed customers using Comcast had issues here however our other customers have not had issues. We've also done some MTR's from a few of our other locations in the US and none of them are showing issues.
Hopefully everything gets back up for you guys who are having issues and for our customers having some issues.
Posted by Kjtocool, 06-18-2013, 10:02 PM I am a FIOS customer at home. My servers with Burst.net are in the Scranton data center.
Posted by FRH Lisa, 06-18-2013, 10:05 PM Can you do a traceroute and see if you route through Highwinds (hwng.net [205.185.198.130])?Quote:
Originally Posted by KjtocoolI am a FIOS customer at home. My servers with Burst.net are in the Scranton data center.
Posted by Kjtocool, 06-18-2013, 10:08 PM They don't appear to.Quote:
Originally Posted by FRH LisaCan you do a traceroute and see if you route through Highwinds (hwng.net [205.185.198.130])?
Posted by Senator B, 06-18-2013, 10:09 PM Comcast subscriber here, can't access. Also can't access via Sprint Wireless right now, but various site checkers around the web are reporting that my site is up and responding. Odd.Quote:
Originally Posted by FRH LisaThere appears to be an issue somewhere between Highwinds and Comcast. We have a lot of Comcast customers reporting that they are unable to reach servers in the Scranton datacenter, and all traceroutes from those customers die at unknown.hwng.net [205.185.198.130].
Our office uses FIOS, and we can hit the DC just fine. Same on our 4G Verizon hotspots. I don't know what's going on behind the scenes, but it appears to be ONLY affecting Comcast customers and other ISPs that route through Highwinds. Can anyone else confirm?
Any other DCs fed by Highwinds reporting any trouble?
Posted by RobM, 06-18-2013, 10:10 PM Yep more PA customers on PTD now lost connections also. goes PTD -> Hwng.net and stops.
now getting coffee POT ready
Posted by FRH Lisa, 06-18-2013, 10:13 PM Where is your connection dying off?Quote:
Originally Posted by KjtocoolThey don't appear to.We keep an old P4 Netburst around here for the sole purpose of heating water for the French press. Going to fire up prime95!Quote:
Originally Posted by RobMYep more PA customers on PTD now lost connections also. goes PTD -> Hwng.net and stops.
now getting coffee POT ready
Posted by Senator B, 06-18-2013, 10:15 PM FWIW, the Sprint connection also dies at unknown.hwng.net. Lovely.
Posted by hostinginsiders, 06-18-2013, 10:17 PM This is where traceroutes end from both my home connection in Germany and Softlayer's Dallas, TX datacenter. However, I still can access the server using some proxy servers.
6 unknown.hwng.net (205.185.198.130) 34.612 ms * *
Posted by FRH Lisa, 06-18-2013, 10:19 PM Confirmed up from Dallas TX, Reston VA, Verizon Wireless 4G LTE, and Verizon FIOS. Confirmed down via Comcast. Yuck.
Posted by hostinginsiders, 06-18-2013, 10:21 PM Nope can't reach Burst from Softlayer's Dallas, TX DC.
Did I mention it's 4 AM over here (Germany)
Posted by gordonrp, 06-18-2013, 10:22 PM about 50/50 not just some:Quote:
Originally Posted by lemon09It is down from some international location. It is accessible in US.
http://d.pr/i/BdyE/4Q6iWdb1
Posted by Purevoltage, 06-18-2013, 10:23 PM We're able to reach it without issues from Dallas in CoreXchange
Posted by XLT_Frank, 06-18-2013, 10:24 PM I am unable to access Burst, my colo, and my VPS. Code:3 11 ms 11 ms 9 ms te-3-3-ur01.princefrdrck.md.bad.comcast.net [68. 85.134.225] 4 10 ms 25 ms 12 ms xe-11-0-2-0-ar04.capitolhghts.md.bad.comcast.net [68.87.129.1] 5 21 ms 18 ms 19 ms he-5-3-0-0-10-cr01.ashburn.va.ibone.comcast.net [68.86.93.141] 6 13 ms 12 ms 13 ms be-14-pe04.ashburn.va.ibone.comcast.net [68.86.8 4.218] 7 43 ms 12 ms 24 ms comcast-9-2.r1.dc.hwng.net [66.208.229.246] 8 27 ms 27 ms 44 ms 3-1.r1.at.hwng.net [69.16.191.126] 9 39 ms 48 ms 49 ms 3-1.r1.mi.hwng.net [209.197.0.210] 10 39 ms 40 ms 39 ms unknown.hwng.net [205.185.198.130] 11 41 ms 48 ms 38 ms unknown.hwng.net [205.185.198.134] 12 94 ms 93 ms 95 ms xe0-01.gwy01.laca02.hostnoc.net [64.120.243.118] 13 * * * Request timed out. 14 * * * Request timed out. 15 * ^C
Posted by hostinginsiders, 06-18-2013, 10:27 PM Yeah now the traceroute is ending in 64.120.243.118 for me too. This is Burst's DC. Seems like they have some sort of network issue.
Posted by FRH Lisa, 06-18-2013, 10:29 PM We're able to reach our servers in Scranton from DataBank in Dallas. Just for curiosity's sake, if you can't reach Scranton, can you post where your connection is dying?
Posted by HostcrateCEO, 06-18-2013, 10:37 PM A lot of customers are receiving the following in their trace routes
8 37 ms 61 ms 47 ms e2-4.r1.ch.hwng.net [209.197.0.33]
9 67 ms 82 ms 63 ms 3-1.r1.at.hwng.net [69.16.191.126]
10 79 ms 73 ms 78 ms 3-1.r1.mi.hwng.net [209.197.0.210]
11 73 ms 72 ms 75 ms unknown.hwng.net [205.185.198.130]
12 67 ms 71 ms 74 ms unknown.hwng.net [205.185.198.134]
13 123 ms 137 ms 136 ms 64.120.243.118
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.
Posted by Onra Host, 06-18-2013, 10:42 PM We have a few of our server colo'd at Burst.net
Most of our client base can reach their servers just fine, however we do have three users (two using Comcast) reporting problems connecting; one is from Dallas, another from Florida, and the last from Amsterdam. Through traceroutes they all seem to get hung up at "unknown.hwng.net [205.185.198.130]".
At our office locations in Tampa and San Diego, both use FiOS and both are connecting just fine.
Posted by techjr, 06-18-2013, 10:43 PM Hopefully this gets resolved soon. I haven't been doing active monitoring for awhile but I don't recall any outages or network issues with them in quite awhile.
Posted by FRH Lisa, 06-18-2013, 10:45 PM Our experience with Burst has always been very good, so I'm sure they're doing everything they can to get the ball rolling again. We have a ticket in and we (and our customers) are patiently waiting. Hopefully it will come sooner rather than later.Quote:
Originally Posted by techjrHopefully this gets resolved soon. I haven't been doing active monitoring for awhile but I don't recall any outages or network issues with them in quite awhile.
Posted by HostcrateCEO, 06-18-2013, 10:49 PM Same here.Quote:
Originally Posted by FRH LisaOur experience with Burst has always been very good, so I'm sure they're doing everything they can to get the ball rolling again. We have a ticket in and we (and our customers) are patiently waiting. Hopefully it will come sooner rather than later.
Posted by Kjtocool, 06-18-2013, 11:13 PM I've been with them for years, never seen something like this.
Posted by HostcrateCEO, 06-18-2013, 11:34 PM Same here. Hopefully they can resolve this as soon as possible.Quote:
Originally Posted by KjtocoolI've been with them for years, never seen something like this.
I know some clients of mine have reported that they can now access when they couldn't before so hopefully they get this figured out shortly.
Posted by incitonetworks, 06-18-2013, 11:41 PM I am having problems too
Posted by Kjtocool, 06-19-2013, 12:05 AM Seems resolved for me.
Posted by incitonetworks, 06-19-2013, 12:15 AM Resolved for me now
Posted by HostcrateCEO, 06-19-2013, 12:15 AM Same on our side now.
Posted by evohost Canada, 06-19-2013, 12:17 AM Up and running for me. Lets see if it stays that way.
Posted by FRH Lisa, 06-19-2013, 12:17 AM I don't have the luxury of having a Comcast account to play with (FIOS here), but isup.me is now reporting that sites are up when I test them. That's a big improvement.
Posted by Senator B, 06-19-2013, 12:30 AM Working via Comcast now.
Posted by Onra Host, 06-19-2013, 12:31 AM Just got this email:
Hello,
Zayo's fiber provider has advised us that there is a fiber outage in Plymouth Meeting, PA. A truck hit a bridge and snagged the aerial fiber cable. They do have a crew onsite but there is no ETR at this time. Additional equipment is currently on route to the location to assist with the necessary repairs. Further updates will be provided on our forum at http://forums.burst.net/forumdisplay...rvice-Advisory
Posted by falconae, 06-19-2013, 01:03 AM My vps in LA just dropped, can't access the CP.
Posted by falconae, 06-19-2013, 01:21 AM It wouldn't let me edit my post above.
*editing to say my CP is working and I can rdp into my server. And some is it up sites are reporting everything is fine.... But tracert from my house dies at 64.120.243.142 like others have seen
Posted by thinkingmachines, 06-19-2013, 01:31 AM I have a Windows VPS in Miami. I was just about to write that I can't access it from Sweden, but right now I can access it again.
Anyway .. can a fiber outage in PA affect the datacenter i Miami?
Posted by hostinginsiders, 06-19-2013, 04:13 AM The past 3-4 years have been pretty perfect. They had nearly 100% uptime. However, before that they have had quite a few issues like that.Quote:
Originally Posted by FRH LisaOur experience with Burst has always been very good, so I'm sure they're doing everything they can to get the ball rolling again. We have a ticket in and we (and our customers) are patiently waiting. Hopefully it will come sooner rather than later.
I have been a customer of theirs since early 2004.
Not a big deal. Let's hope things will stay good now.
Posted by WizzSupport, 06-19-2013, 04:38 AM They have pretty strong network setup and awesome admins on the role I am sure things will get right pretty quick!
Posted by nikolakidman, 06-19-2013, 04:41 AM BurstNET has Joe Marr as main network engineer, the guy is a real rock in what he is doing. Pretty sure, If Joe Marr get on it, It will be behind us in no time.
Posted by realvaluehosting, 06-19-2013, 05:13 AM Seems gonna take many hours to fix this.
Posted by cikul, 06-19-2013, 06:02 AM No response from their staff for my ticket about this problem
Posted by hostinginsiders, 06-19-2013, 06:03 AM What do you mean? Is it still down in some areas? Here it has been back up for hours.Quote:
Originally Posted by realvaluehostingSeems gonna take many hours to fix this.
Posted by realvaluehosting, 06-19-2013, 06:21 AM Yes, servers in LA seems still down.Quote:
Originally Posted by hostinginsidersWhat do you mean? Is it still down in some areas? Here it has been back up for hours.
Issues like this ( " A truck hit a bridge and snagged the aerial fiber cable " ) is def. going to take many hours to get fixed.
Posted by gingir, 06-19-2013, 07:59 AM Do burstnet team monitor these forums?
Posted by realvaluehosting, 06-19-2013, 08:02 AM You mean WHT?
Burst do have WHT account(s)... but not sure that they frequently visit WHT and/or monitor WHT posts.
Posted by gingir, 06-19-2013, 08:04 AM OK thanks, I asked because I have an issue with them too.Quote:
Originally Posted by realvaluehostingYou mean WHT?
Burst do have WHT account(s)... but not sure that they frequently visit WHT and/or monitor WHT posts.
A different type of issue however.
Posted by XLT_Frank, 06-19-2013, 08:23 AM Assuming they can read them. :-)Quote:
Originally Posted by realvaluehostingYou mean WHT?
Burst do have WHT account(s)... but not sure that they frequently visit WHT and/or monitor WHT posts.
I am back up though.
Posted by realvaluehosting, 06-19-2013, 08:24 AM You are lucky
Posted by splitice, 06-19-2013, 09:50 AM Chicago still down everywhere, or at least my node. 9 hours and counting.
Grr...
Posted by BullyGoat, 06-19-2013, 09:58 AM Quote:
Originally Posted by spliticeChicago still down everywhere, or at least my node. 9 hours and counting.
Grr...
Me too. This. Sucks. Really. Really. Bad.
I make my money from these sites and they've been down for 12+ hours. I moved from GoDaddy because of their problems in Nov 2012. Burst had been awesome up until now. They say its because of a truck accident in PA but how could that affect Chicago servers? Is Chicago the only one still down?
Posted by realvaluehosting, 06-19-2013, 10:14 AM LA is also having issues
Posted by nkawit, 06-19-2013, 11:19 AM This is what we got from them, their LA DC appears to be unreachable outside the US.Quote:
We apologize for this inconvenience. Currently we are experiencing an issue with Zayo, which is one of our providers.
Zayo's fiber provider has advised us that there is a fiber outage in Plymouth Meeting, PA. A truck hit a bridge and snagged the aerial fiber cable. They do have a crew onsite but there is no ETR at this time. Additional equipment is currently on route to the location to assist with the necessary repairs. Further updates will be provided on our forum at http://forums.burst.net/forumdisplay...rvice-Advisory
Thank you for being a valued BurstNET customer.
Posted by BullyGoat, 06-19-2013, 11:27 AM Mine is in Chicago and it just came back up! I also got the same message.
Posted by nkawit, 06-19-2013, 11:28 AM Everything just came back up here too
Posted by falconae, 06-19-2013, 12:21 PM Mine have been back up, but my monitoring sites keep on pinging alerts and then all clears. So it's intermittent in other areas of the country.
The last alert I got was about 15 minutes ago so it's definitely progress
Posted by nkawit, 06-19-2013, 12:28 PM Got this a few mins ago.Quote:
Zayo has reported to us that the fiber cut has been restored at this time. If you see any further issues with this please let us know by replying to this ticket.
Posted by nibb, 06-20-2013, 04:13 AM Im not sure why you guys are impressed that its down.
This is normal in Burst.net
I have a VPS in Miami with them for like 3 months and its down like 1 to 3 hours a week.
Right now its down as well.
Here is the Pingdom uptime reports form the last 7 days:
99,37%
Downtime 1h 5m
Number of Downtimes 19
Yes, 19 downtimes in the last week.
And when its not down, it loses like packets, at least once a day for a few minutes.
By the way im not complaining, for the price I pay I completely understand this is what you get and I expected to get 1 or 2 hours of downtime per week since this is not critical in any way. I would not put anything that requires 99% uptime in their networks. What is funny is that for those prices they actually have an SLA:
http://www.burst.net/sla.php
I would be claiming credits each month in my case as I they failed to meet once 99% so far. They are actually at 98% in best cases.
This is true for almost 9 out of 10 cheap providers I tested, they all have packets loss and bad uptimes.
Burst is no exception. If you want at least 99.9% in a 365 days for the network, with Burst you are not going to get it ever.
Posted by Dant27, 06-20-2013, 04:36 AM The individual node your VPS resides on may be having problems, but we have servers with them in multiple locations and the Burst network is rock solid. Prior to yesterdays outage I can't remember the last time there was any significant network downtime and we've been with them for years.Quote:
Originally Posted by nibbIm not sure why you guys are impressed that its down.
This is normal in Burst.net
I have a VPS in Miami with them for like 3 months and its down like 1 to 3 hours a week.
Right now its down as well.
Here is the Pingdom uptime reports form the last 7 days:
99,37%
Downtime 1h 5m
Number of Downtimes 19
Yes, 19 downtimes in the last week.
And when its not down, it loses like packets, at least once a day for a few minutes.
By the way im not complaining, for the price I pay I completely understand this is what you get and I expected to get 1 or 2 hours of downtime per week since this is not critical in any way. I would not put anything that requires 99% uptime in their networks. What is funny is that for those prices they actually have an SLA:
http://www.burst.net/sla.php
I would be claiming credits each month in my case as I they failed to meet once 99% so far. They are actually at 98% in best cases.
This is true for almost 9 out of 10 cheap providers I tested, they all have packets loss and bad uptimes.
Burst is no exception. If you want at least 99.9% in a 365 days for the network, with Burst you are not going to get it ever.
Posted by nibb, 06-20-2013, 05:31 AM Yes this would be the case except I had the same problems in other providers with similar prices as well, including very cheap cloud ones. Change nodes does not really help when its a network issue.Quote:
Originally Posted by Dant27The individual node your VPS resides on may be having problems, but we have servers with them in multiple locations and the Burst network is rock solid. Prior to yesterdays outage I can't remember the last time there was any significant network downtime and we've been with them for years.
Again im not complaining, but my guess if that if you never had problem is because you are not actually monitoring your servers in a very picky way. I not only have pingdom but my own system to avoid false positives which are rather as picky as it can right until a ICMP packet tracing, in the case of burst, in Pingdom at least I set alerts only in case of over 10 minutes of outages, otherwise I would get them every day, and since I know they come back after a few minutes, no harm down.
Once you go into 1 minute monitoring, and even monitor packet 24 hours, there is a world difference between one provider and another. I would not use them for VOIP or latency sensitive services at all.
The problems I detect, are not node problems, they are network issues, like high latency as well and its not node specific. Of course I could just have bad luck, but usually on my experience in very budget providers, changing node does nothing, the problems re-appear eventually.
This is to be expected, im happy with the service for what I pay which is not even a cup of coffee in some places, so no complain here.
I just wanted to point it out, in case someone wonders why they are down. Also, I just found this post randomly, and several locations of them have issues, with connections going on and off all the time. The same thing some experience here and posted already, I do almost every week for at least 3 months now.
Its not the server going down, but the network severely losing packets, then losing them 100%, it usually starts with high latency, then packets loss, then complete loss, then it comes back after 5 minutes, then it goes again off after an hour.
Im sure as any huge providers, they have different uptimes as networks and servers they have, so some could have a great experience. My experience is actually great so far, for the price, 1 or 2 hours downtime per week is not that bad comparing them other budget providers which are even worst.
I don´t run anything critical, so downtime is not an issue with them in my case.
Posted by falconae, 06-26-2013, 04:30 PM My monitors flagged my server at 1PM pst.
and am getting System Configuration Error going to their service.burst site
Posted by F-DNS, 06-26-2013, 04:50 PM I've been in and out of service.burst.net all day today (probably 20+ times) and not seen 1 problem with it.Quote:
Originally Posted by falconaeand am getting System Configuration Error going to their service.burst site
Posted by falconae, 06-26-2013, 05:29 PM Burst's NOC said that the Dev's are working on an issue and should have it sorted within the hour
Posted by Trentos, 07-16-2013, 10:01 PM I have 2x VPS with burst net and they have been intermittently offline for the last 5 days. I am preparing go go elsewhere.Quote:
Originally Posted by KjtocoolI run a dedicated box with Burst.net and it's offline, I tried going to Burst.net to open a support ticket, and it's down as well. Can anyone confirm?
Posted by XLT_Frank, 07-17-2013, 08:16 AM Have you submitted a ticket with them? What have they said was the problem?Quote:
Originally Posted by TrentosI have 2x VPS with burst net and they have been intermittently offline for the last 5 days. I am preparing go go elsewhere.
Posted by Wira_Soenaryo, 07-18-2013, 11:49 PM My VPS in LA still down until now..
Node : vserver3007.laca01.hostnoc.net
Any ETA when this will be resolved?
Have submit support ticket, still not replied until now.
Posted by desynced, 07-20-2013, 05:15 AM Oh, I'm not the only one that's been having numerous issues with BurstNet lately I see.
Currently everything I have with Burst is up, but have been having quite a few problems with uptime lately. What's been going on? I've been happy with them for over a year now, but the last two months have been interesting from support response times to down times.
Posted by falconae, 07-20-2013, 11:46 AM Ours has been up throughout these latest reports (in LA too) but we had some hiccups earlier in the month caused by 1 user abusing the node and another user getting flooded.
I had 1 ticket that took awhile to be answered so I just kept on updating it with up and down updates for my vps.
Turns out this is why it went unanswered, apparently if you updated, reply or change the status of your ticket it gets put back to the bottom of the queue.
Posted by PremiumHost, 07-22-2013, 03:14 AM How long has it been down?Quote:
Originally Posted by Wira_SoenaryoMy VPS in LA still down until now..
Node : vserver3007.laca01.hostnoc.net
Any ETA when this will be resolved?
Have submit support ticket, still not replied until now.
Posted by Wira_Soenaryo, 07-22-2013, 04:03 AM Well... its down for about 4 hours I guess...
But the ticket respond just received the next day with information someone abused the server node.
Add to Favourites Print this Article