Burst.NET down [merged]

Portal Home > Knowledgebase > Articles Database > Burst.NET down [merged]

Posted by Mark L, 03-20-2006, 03:23 PM
Burst.net doesn't work - neither does my server.
Posted by DediZoneSales, 03-20-2006, 03:23 PM
Hi, I am having issues pinging burst.net or any of their servers. They appear to be down?
Posted by kapot, 03-20-2006, 03:24 PM
YEAHHH BABY !!! Its down !
Posted by Mark L, 03-20-2006, 03:25 PM
Yeap. I made a thread. How I am searching: Searching for burst.net A record at d.root-servers.net [128.8.10.90]: Got referral to K.GTLD-SERVERS.net. [took 12 ms] Searching for burst.net A record at K.GTLD-SERVERS.net. [192.52.178.30]: Got referral to dns.burst.net. [took 214 ms] Searching for burst.net A record at dns.burst.net. [66.96.193.2]: Timed out. Trying again. Searching for burst.net A record at dns.burst.net. [66.96.193.2]: Timed out. Trying again. Searching for burst.net A record at dns.burst.net. [66.96.193.2]: Timed out. Trying again. Searching for burst.net A record at dns.burst.net. [66.96.193.2]: Timed out. Trying again. Searching for burst.net A record at dns1.burst.net. [66.96.194.2]: Timed out. Trying again. Searching for burst.net A record at dns.burst.net. [66.96.193.2]: Timed out. Trying again. Alerts going off like crazy
Posted by DediZoneSales, 03-20-2006, 03:26 PM
Yep, it looks like a DC outage. Would be nice if we can get an update SOON.
Posted by Mat-d-rat, 03-20-2006, 03:26 PM
Ditto, can'g ping my server of bursts, normally I can make burst's network, but not this time! Must be big!
Posted by Mark L, 03-20-2006, 03:27 PM
Yeah nocster/unrestricted is gone too.
Posted by DediZoneSales, 03-20-2006, 03:28 PM
None of their staff is reachable, Thats abit worrying. Lets hope it wont last long.
Posted by Mark L, 03-20-2006, 03:30 PM
Looks like a dns issue.....I cannot trace burst or anything.
Posted by RyanD, 03-20-2006, 03:32 PM
yup, all of burst is out for us. luckily it's only our secondary dns hosted there.
Posted by pmak0, 03-20-2006, 03:35 PM
$ traceroute juni.aaanime.net traceroute to juni.aaanime.net (64.191.55.247), 30 hops max, 38 byte packets 1 ev1s-64-246-46-1.ev1servers.net (64.246.46.1) 0.472 ms 0.345 ms 0.257 ms 2 ivhou-207-218-245-18.ev1.net (207.218.245.18) 0.537 ms 0.471 ms 0.364 ms 3 ivhou-207-218-223-3.ev1.net (207.218.223.3) 0.702 ms 2.394 ms 1.152 ms 4 ge-0-2-0.r00.hstntx01.us.bb.verio.net (129.250.10.69) 7.028 ms !N 1.609 ms !N 1.277 ms !N Why's the traceroute stopping so early?
Posted by anand247sm, 03-20-2006, 03:36 PM
same here, all boxes are unreachable
Posted by Ryan Smith, 03-20-2006, 03:38 PM
Down here too. Lets hope for an update soon :-(
Posted by ewindisch, 03-20-2006, 03:39 PM
So it seems I'm not the only one....
Posted by sirius, 03-20-2006, 03:41 PM
!N means the network is unreachable. Sirius
Posted by anand247sm, 03-20-2006, 03:41 PM
burst.net, nocster, all there sites are down. aim support is offline trying to call them now.
Posted by glace, 03-20-2006, 03:45 PM
Down here three...
Posted by Mark L, 03-20-2006, 03:45 PM
Still dead. Doesn't look like a 5-10 minute thing
Posted by glace, 03-20-2006, 03:47 PM
Burst use DNS servers within their network so it's not a surprise that their domain doesn`t resolve. I think it has been down for around 25 minutes so far. Usually Burst downtimes that take longer than a minute or two take around 30 to 60 minutes.
Posted by richardhay, 03-20-2006, 03:47 PM
From the techs: They had a new GigE turned on this morning, but are unsure if this problem is related to that. No eta as of yet.
Posted by Mark L, 03-20-2006, 03:49 PM
They don't know what the problem is after 30 minutes? lol *sigh*
Posted by glace, 03-20-2006, 03:53 PM
This scares me, too...
Posted by Mainard, 03-20-2006, 03:54 PM
My site is down. I hate life. I want to die along with my hosting.
Posted by Mark L, 03-20-2006, 03:55 PM
Great first post.
Posted by glace, 03-20-2006, 03:56 PM
Hm...do you mean that serious ?
Posted by DediZoneSales, 03-20-2006, 03:58 PM
Hi Anybody have any luck in reaching their support staff?
Posted by GordonH, 03-20-2006, 03:58 PM
Their IP's are not being routed at all now. Routes must have expired. They are all timing out for me long before Pittsburgh.
Posted by Mark L, 03-20-2006, 03:59 PM
I'm timing out after three hops, at 12.118.112.25.
Posted by glace, 03-20-2006, 03:59 PM
What does that mean ?
Posted by anand247sm, 03-20-2006, 04:01 PM
hmm... they say their network department is working on it. no ETA.
Posted by glace, 03-20-2006, 04:01 PM
I'm timing out after the first hop
Posted by AlexAT, 03-20-2006, 04:01 PM
Seems Burst is down for more than 1 hour.
Posted by Empty Promis3s, 03-20-2006, 04:01 PM
Considering how well I know him he is serious. He has terrible mood swings. Kinda like a girl who is PMSing.
Posted by jmhost, 03-20-2006, 04:02 PM
Main quit being silly. :p I can't get any hops to my server, It just says It's unable to resolve the target system. All dead.
Posted by Mark L, 03-20-2006, 04:03 PM
My alerts went off at 2:21, so it has been over 40 minutes.
Posted by si2040, 03-20-2006, 04:03 PM
Well I think everyone needs some compenstaion from Burst.Net as this has happened too frequently over the past two months and is not acceptable.
Posted by Arsalan, 03-20-2006, 04:04 PM
I think he is suffering from PDS.. thats Post Downtime Stress.... no time to laugh, but what the heck *lol*
Posted by kapot, 03-20-2006, 04:04 PM
Pack your belongings and start moving somewhere else! Oh wait, I cant do that My servers are still down !
Posted by GordonH, 03-20-2006, 04:05 PM
Well its a bit like DNS. All the ISP's have copies of each others routing tables. Normally they keep trying for quite a while but if it goes on too long the expire the table and have to wait for a new one. The reason i said that was that normally if burst goes down it stops somewhere near Pittsburgh. I am in the UK and I am getting no further than Washington (Level 3). This means the route doesnt know where to go from there, or it could be an outage in Washington but thats unlikley as it would be affecting more than Burst.
Posted by Matt, 03-20-2006, 04:05 PM
Threads merged
Posted by jmhost, 03-20-2006, 04:05 PM
No one Is going to get It though, I should know. I went with them through the 2003? 2004? february outtage where It was all dead for 2 days and then came back and the cPanel licenses were expired for everyone, no one got any money or anything for that.
Posted by glace, 03-20-2006, 04:05 PM
Two years ago they had a lot more of those downtimes... Their network performance is a lot better now (but by far not as good as EV1 or other DCs)
Posted by AlexAT, 03-20-2006, 04:06 PM
SiteUptime shows 45 minutes but I have 3rd party information that it was long before.
Posted by glace, 03-20-2006, 04:08 PM
Yes, I've heard about the Feb outage (it must have been 2004). I haven`t been with them at that time but the Feb outage became a legend. I've read a lot about it on WHT.
Posted by Mark L, 03-20-2006, 04:08 PM
I live in MI, and I'm going dead in NJ. How does that work out? lol
Posted by glace, 03-20-2006, 04:09 PM
I am monitoring from two locations and both say it has been down since around 2:20
Posted by RobM, 03-20-2006, 04:12 PM
Don't even say that
Posted by AlexAT, 03-20-2006, 04:13 PM
I won't argue. I have no such monitoring for my backup server there.
Posted by mauricioperez, 03-20-2006, 04:16 PM
Is the problem the network (routers, switchs ...) around burs.net ?
Posted by cbwass, 03-20-2006, 04:21 PM
As usual in these situations untill someone from the NOC decide to tell use what is the problem we can only guess.
Posted by Homeblock, 03-20-2006, 04:21 PM
Is Burst downtime common? This is the first I have noticed my server being down.
Posted by ewindisch, 03-20-2006, 04:22 PM
Its a standard response to say, "no ETA yet", or "we don't know what the problem is yet". This doesn't mean that they *don't* know, but an issue of internal communications (the guy fixing it may be too busy to actually discuss the issue), or it may be some external factor and they want to make sure that they have all their facts straight before going public with it. (If, say, a fiber line was cut -- how was it cut? how can they prevent it? etc) I'll wait another 2 hours before I start to panic. (but I won't be happy)
Posted by Mark L, 03-20-2006, 04:22 PM
Well, short outages, but not really over an hour (aka this) are common. edit: I am surprised you will let two hours go by before you start to. This started right when school let out for USA, and there is a traffic increase after ~3PM I have seen.
Posted by jmhost, 03-20-2006, 04:23 PM
Burst's uptime has Improved alot In the past year, and I'm happy with my service. Despite being with them through the 2 day outtage In 2004, I'm still happy. This Is the first hour+ outtage that was unplanned I've had since I don't know when, so yeah, they are pretty good.
Posted by ewindisch, 03-20-2006, 04:23 PM
This is about the time I noticed an outage too -- perhaps a little earlier; however, I received calls from clients before then, indicating problems. It seems that some routes may have been dropped prior to the mass-outage around 2:20pm.
Posted by glace, 03-20-2006, 04:26 PM
It happens occasionally. It used to be a lot more common two years ago. But during the last 6 months it hasn`t been that bad.
Posted by HostJedi, 03-20-2006, 04:27 PM
We had a route processor card fail on a core router. Services should restored shortly.
Posted by Mark L, 03-20-2006, 04:27 PM
Woot an update.
Posted by si2040, 03-20-2006, 04:27 PM
Yes I think I am..just a bit too long..been about 40 min??
Posted by glace, 03-20-2006, 04:29 PM
It's been down for around 70 minutes
Posted by Mark L, 03-20-2006, 04:29 PM
Close to that yeah.
Posted by mauricioperez, 03-20-2006, 04:29 PM
In others NOCs downs, the problem was attribuited to network devices...
Posted by richardhay, 03-20-2006, 04:31 PM
I wish burst could have redundant core routers... Several outages seem to have been attributed to such equipment.
Posted by Homeblock, 03-20-2006, 04:31 PM
I don't think we should necessarily expect them to come to WHT with an update.
Posted by Mark L, 03-20-2006, 04:33 PM
How else would they let us know? Their entire network is dead.
Posted by Homeblock, 03-20-2006, 04:36 PM
Perhaps you are right. I just feel that WHT isn't the definitive source for updates. I would have hoped they had some redundant DNS backups setup so they could notify with their website. Not everyone knows about WHT.
Posted by Mark L, 03-20-2006, 04:41 PM
True. But this is the largest web hosting forum. They did update, it's just the fact that -everything- was down...still is, but I don't see what else they could have done with contacting us. Their support ticket system etc is all dead.
Posted by glace, 03-20-2006, 04:42 PM
Like their customers have recommended for many years they should host their message board outside of their network so when their network is down the message board is still up... But they don`t do that and probably aren`t ever going to do it.
Posted by glace, 03-20-2006, 04:51 PM
Hey, it seems to be back...
Posted by Mark L, 03-20-2006, 04:52 PM
Back up, an hour and a half later.
Posted by richardhay, 03-20-2006, 04:53 PM
Everything's back up... here...
Posted by AlexAT, 03-20-2006, 04:54 PM
1.5+ hours of downtime and my servers are up. Thanks God.
Posted by anand247sm, 03-20-2006, 04:55 PM
network seems to be back up now.
Posted by ewindisch, 03-20-2006, 04:57 PM
I agree with an earlier poster... Burst.net sorely needs redundant routers. Unfortunately, such equipment is not cheap.
Posted by richardhay, 03-20-2006, 05:03 PM
What worries me is that this appears to be the same issue that burst had on the 13th that caused 20-30 minutes of downtime then. From the burst forums: "March 13th, 2006 We had a problem with one of the GigabitEthernet line cards in one of our service routers today, causing approx. 20-30 minutes of packet loss and/or latency for a portion of our network." I hope that the faulty line card (if it is indeed the same line card) has been pulled and replaced. Richard
Posted by RobM, 03-20-2006, 05:17 PM
A company that listed as a Inc 500 that claims 2 million can afford to spend a few dollars to get better rollover gear.
Posted by Arsalan, 03-20-2006, 05:31 PM
Hopefully this should be the last time this issue occurs.
Posted by bhaputi, 03-20-2006, 05:35 PM
http://forums.burst.net/showthread.php?t=3923
Posted by bhaputi, 03-20-2006, 05:38 PM
Richard, No reason to worry with that. The faulty line card from last monday was just that - a gigabit ethernet line card, and it was pulled and replaced last monday. The issue today was with the route processor card, a different type of card altogether, which has also now been removed and replaced.
Posted by richardhay, 03-20-2006, 05:50 PM
Dan: Thanks for the detailed explanation--and I apologize for my inability to read (ie. I mixed up the two types of card). Thanks and take care... Richard