Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > service.burst.net down?
service.burst.net down?
| Posted by HostingBig, 01-13-2010, 01:32 AM |
|
down for me |
| Posted by Dustin Cisneros, 01-13-2010, 02:06 AM |
|
Up for me.... |
| Posted by MattS, 01-13-2010, 02:44 AM |
|
it was down earlier but seems to be back up. Also seems like a network issue as my management company informed me that all monitoring alarms went off on all Burst servers, so yeah network related. |
| Posted by BurstNET, 01-13-2010, 04:50 AM |
NO, it was NOT network related.
We had our billing/ordering system down for an hour for an upgrade.
Not sure what you are monitoring, but the network has had no issues tonight.
http://www.hyperspin.com/publicreport/57207/7765
Test Status Last Upd Next Upd Upd Interval Jan Uptime Jan Downtime Jan Outage
BurstNET ping UP 03:47 AM 03:52 AM 5 min 100.000% 00min 0
.
. |
| Posted by Nick H, 01-13-2010, 05:01 AM |
Quote:
|
Originally Posted by BurstNET
Not sure what you are monitoring, but the network has had no issues tonight.
|
Just coincidence then that my helpdesk was flooded with monitoring alerts regarding BurstNet servers (and only BurstNet servers) last night then?
Just because your HyperSpin that monitors ONLY your company website says you were up doesn't mean there wasn't a routing issue or network issue elsewhere in the datacenter. |
| Posted by MattS, 01-13-2010, 05:26 AM |
http://img22.imageshack.us/img22/343/hmmfb.jpg
Could be a carrier or routing issue then (blacked out are client servers). It was yesterday not tonight, so my bad for that. Either way it's up now. |
| Posted by Nick H, 01-13-2010, 05:28 AM |
Quote:
|
Originally Posted by Nick H
Just coincidence then that my helpdesk was flooded with monitoring alerts regarding BurstNet servers (and only BurstNet servers) last night then?
|
And they're off again! |
| Posted by BurstJoeM, 01-13-2010, 07:46 AM |
Very strange,
Only thing I have is a problematic access layer switch between 12:01AM and 12:21AM EST. The impact would have been limited to about 30 customers. service.burst.net would not have been involved.
I don't see any issues in our NMS, so it is possible that this was an external problem with one of our carriers. If anyone opened a ticket and supplied a traceroute last night, PM your ticket number. |
| Posted by Nick H, 01-14-2010, 03:28 AM |
Quote:
|
Originally Posted by BurstJoeM
Only thing I have is a problematic access layer switch between 12:01AM and 12:21AM EST. The impact would have been limited to about 30 customers. service.burst.net would not have been involved.
|
That's right around when it started. If it crops up again I'll ticket you guys with tracert's. |
| Posted by XFactorServers, 01-14-2010, 01:06 PM |
Quote:
|
Originally Posted by BurstNET
NO, it was NOT network related.
We had our billing/ordering system down for an hour for an upgrade.
Not sure what you are monitoring, but the network has had no issues tonight. http://www.hyperspin.com/publicreport/57207/7765
Test Status Last Upd Next Upd Upd Interval Jan Uptime Jan Downtime Jan Outage
BurstNET ping UP 03:47 AM 03:52 AM 5 min 100.000% 00min 0
.
. |
This is monitoring your own site... doesn't mean you don't have issues elsewhere. |
| Posted by BurstNET, 01-14-2010, 05:08 PM |
Quote:
|
Originally Posted by XFactorServers
This is monitoring your own site... doesn't mean you don't have issues elsewhere.
|
Yes, but it means the network as a whole is/was not down.
All to often people claim a provider as a whole, or their network, is down, when just one server is down, or just a single switch having an issue.
.
. |
| Posted by prologan, 01-14-2010, 05:33 PM |
Quote:
|
Originally Posted by BurstNET
Yes, but it means the network as a whole is/was not down.
All to often people claim a provider as a whole, or their network, is down, when just one server is down, or just a single switch having an issue.
.
.
|
Thanks for clarifying. I am sure it helps the people who ARE affected rest easier knowing that everyone else is online... 
edit: especially when it is phrased as if nobody could possibly be experiencing any isolated issues as your first post was. |
| Posted by BurstNET, 01-14-2010, 05:45 PM |
This thread was about service.burst.net, our billing/ordering system being down for maintenance, and people trying to turn it into a network issue, which it was not. Simple maintenance in the middle of the night for an hour, nothing more. This was NOT a network issue, and did NOT affect clients' service. Please stay on topic.
.
. |
| Posted by Nick H, 01-14-2010, 07:41 PM |
Quote:
|
Originally Posted by BurstNET
just a single switch having an issue.
|
Which is still a problem within your network |
| Posted by N|Kitmitto, 01-14-2010, 08:14 PM |
If this did not affect clients servers then why did one client post reports about multiple servers being down and why did Nick H say he got reports saying his customers at BurstNET went down? This was not a fact of just one server or just two. More than likely not even the same cabinet. Because ONE website was up, this means you're entire network was up?
I think BurstNET should stop being so eager to prove everyone wrong and to admit to their mistakes. It's amazing that a company with your attitude as the main business name on WHT still has business with WHT customers. |
| Posted by BurstNET, 01-14-2010, 10:45 PM |
Quote:
|
Originally Posted by Nick H
Which is still a problem within your network
|
Sure it is, but it does NOT mean the network is down.
.
. |
| Posted by Nick H, 01-14-2010, 11:13 PM |
Quote:
|
Originally Posted by BurstNET
Sure it is, but it does NOT mean the network is down.
.
.
|
Nobody said the network was down. If you re-read the post you'll see that Matt said "network issue" -- which you confirmed to be true. |
| Posted by BurstNET, 01-15-2010, 12:26 AM |
Quote:
|
Originally Posted by N|Kitmitto
I think BurstNET should stop being so eager to prove everyone wrong and to admit to their mistakes. It's amazing that a company with your attitude as the main business name on WHT still has business with WHT customers.
|
Sorry, but we do not tolerate nonsense. You may not like that, but that is how we approach the childish/immature nature of WHT.
We have been doing this for nearly two decades, and obviously are doing something right based on our continuous growth and longevity...
We had one distribution switch down for a brief period of time. We did NOT have a network-wide issue. It affected a very small amount of servers, and was rectified very quickly. Distribution switches fail, in every budget hosting network---it's a fact.
This has absolutely nothing to do with our core network, our border network, or our network as a whole---which has nothing short of phenomenal uptime. To claim this was a network issue, to make it look like the network as a whole had an issue, is nonsense.
.
. |
| Posted by BurstNET, 01-15-2010, 12:29 AM |
Quote:
|
Originally Posted by N|Kitmitto
If this did not affect clients servers then why did one client post reports about multiple servers being down and why did Nick H say he got reports saying his customers at BurstNET went down? This was not a fact of just one server or just two. More than likely not even the same cabinet. Because ONE website was up, this means you're entire network was up?
|
If these servers were not on the same distribution switch, then his monitoring was incorrect. These had to be on the same distribution switch that failed, or they were not down for a short period. The only other possible reason was the network he monitors from was having issues, or the route between his monitoring network and our network had issues.
We did not have a network-wide issue, and nothing beyond one switch was having an issue, other than maintenance on a single server of our own (service.burst.net).
.
. |
| Posted by BurstNET, 01-15-2010, 12:33 AM |
Quote:
|
Originally Posted by Nick H
Nobody said the network was down. If you re-read the post you'll see that Matt said "network issue" -- which you confirmed to be true.
|
When people say "network issue" they incorrectly come to conclusion the entire network was down, when that was not the case. Although a distribution switch is technically network gear, we do not consider that to mean the network is down. We consider that to be a subset of servers/clients being down. Claiming that the network is down, when only a distribution switch failed, is in accurate, and just an attempt to make a provider look bad.
.
. |
| Posted by MattS, 01-16-2010, 04:14 AM |
Quote:
|
Originally Posted by BurstNET
When people say "network issue" they incorrectly come to conclusion the entire network was down, when that was not the case. Although a distribution switch is technically network gear, we do not consider that to mean the network is down. We consider that to be a subset of servers/clients being down. Claiming that the network is down, when only a distribution switch failed, is in accurate, and just an attempt to make a provider look bad.
.
.
|
Do you really always assume? 
I never implied that the network is/ was down. I just said there's an issue occurring at least on my side. And in this case, it was a switch so it'd affect whoever was on that switch with me (partial network issue or in idiot terms since we all love idiots - one piece of the pie was defective and missing something.
As for the making the "provider look bad" comment and it being "inaccurate", I feel that was a little low of a blow there. I have servers with you and if I thought you sucked I would be out of there already. |
| Posted by BurstNET, 01-16-2010, 03:00 PM |
The postings here are completely off-topic, and this whole thread is pointless.
service.burst.net was down for maintenance for an hour, and did not need/warrant an outage thread.
Contact us directly if something like that is inaccessible, rather than aggravating your provider by jumping straight to WHT.
That will not get you in our good graces...
.
. |
| Posted by webhostmaniac, 01-16-2010, 04:56 PM |
Quote:
|
Originally Posted by BurstNET
The postings here are completely off-topic, and this whole thread is pointless.
service.burst.net was down for maintenance for an hour, and did not need/warrant an outage thread.
Contact us directly if something like that is inaccessible, rather than aggravating your provider by jumping straight to WHT.
That will not get you in our good graces...
.
.
|
Good Graces? Why would a company treat a customer differently for their own mistakes. You should be monitoring your switches, When the switch fails you should email the customers on that switch and provide an eta. A company as as your self for two should have enough money for switch monitoring software and maybe auto notifications to clients or maybe an employee to mass mail customers located on that switch which in fact is very easy in whmcs to setup a group and put all those customers on a group and call that group "switch 1" and mail all of those customers with a simple click of a button. Also attitude from a company of your size is very unprofessional. You guys should tone it down a bit. I am fully taking the customers side in this thread because of the tone of your posts allows me to believe the customer is right. Good luck with future sales burstoutofcontrol.net |
| Posted by BurstNET, 01-16-2010, 07:07 PM |
Quote:
|
Originally Posted by zetamaster55
Good Graces? Why would a company treat a customer differently for their own mistakes. You should be monitoring your switches, When the switch fails you should email the customers on that switch and provide an eta.
|
You are missing the whole point.
This thread is about service.burst.net being down, not something else completely off-topic.
The poster ran here to complain about it, rather than contact us directly first.
It happened to have been down for maintenance, which we would have informed him, if he bothered to contact us before jumping the gun.
That is just not right. 
Our comment about that not getting in our good graces, is in relation to this individual, not the switch issue that was posted off-topic later on.
CONTACT YOUR PROVIDER, BEFORE POSTING/COMPLAINING ON WHT----IT IS ONLY THE FAIR/PROFESSIONAL THING TO DO FOR SUPPORT ISSUES.
This has nothing to do with a switch being down or not the same evening, which was a completely different issue, don't merge the two into one.
It is questionable whether that affected the other client that posted here into this thread off-topic.
If all his server he reported down where on the same switch, then it may have, but if not, it is likely to have been something on his end or between him and us.
We do monitor all our switches, that is how we knew about it, and were able to replace it so quickly.
We do not notify our clients when a distribution switch fails, we just simply fix the problem.
Our clients do not pay for such higher end services as instant notifications of such an issue, and it is not feasible/realistic for our company to provide such at such low pricing. If a client requires this, he probably wants a higher end, possibly fully managed solution, from a provider that specializes in such---we do not, it is not our niche of the market.
.
. |
| Posted by webhostmaniac, 01-17-2010, 07:30 PM |
Quote:
|
Originally Posted by BurstNET
This has nothing to do with a switch being down or not the same evening, which was a completely different issue, don't merge the two into one.
It is questionable whether that affected the other client that posted here into this thread off-topic.
If all his server he reported down where on the same switch, then it may have, but if not, it is likely to have been something on his end or between him and us.
We do monitor all our switches, that is how we knew about it, and were able to replace it so quickly.
We do not notify our clients when a distribution switch fails, we just simply fix the problem.
Our clients do not pay for such higher end services as instant notifications of such an issue, and it is not feasible/realistic for our company to provide such at such low pricing. If a client requires this, he probably wants a higher end, possibly fully managed solution, from a provider that specializes in such---we do not, it is not our niche of the market.
.
.
|
This actually seems pretty reasonable to me. |
| Posted by todo1419, 01-18-2010, 01:14 AM |
its true, if one switch/server has issues people assume that the entire network or the entire service is offline "OMG!", give them a break guys we had the exact same thing happen to us, one server was offline or having problems for a short period and then the entire "GET EM`WHT" following jump on to make it bigger than it actually is. When actually we run 4 or 5 servers and only one had some issues.
Best advise is contact your provider first, see whats going on. If they dont answer within a timly manner then you can blast them on a hosting forum (evil). If the support area is down try good old email, i know for a fact that burst have support@ custserv@ etc.. or better yet.. call them.
My 2 cents! |
| Posted by larry2148, 01-18-2010, 01:27 AM |
|
Clearly it looks like there was probably some issues with routes going to the Burst.net network - not an issue with their network itself. This can still cause client outages and thus the alerts but there's nothing Burst can really do so I don't see what the big commotion in this whole thread is about? |
| Posted by BurstNET_CSM, 01-18-2010, 11:19 AM |
Which brings us back to the initial point: contact your provider before running to WHT and posting that things are down.
The OP needed to simply create a ticket or call us, and would have been alerted to the fact that service.burst.net was down for maintenance. But by posting here, the OP created a threadjack about what happens when a switch goes bad. There was no point for this post, and it should be closed, as the reason for starting it was resolved an hour later on the 13th. |
Add to Favourites 
Print this Article
Also Read
Enotch down (Views: 1076)
Shared Hosting
Shared Hosting
