Burstnet Some IPs down

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Burstnet Some IPs down

Posted by jstand1, 01-30-2011, 04:51 AM
Anyone else have problem with some of their IPs not responding at Burst? Four of my IPs have been down since 5 PM CST and 5 hours after I open my ticket I finally get a response saying there's a network issue and that they're looking into it. It's 10 hours now....
Posted by DamienSB, 01-30-2011, 04:54 AM
I am also having a problem related to outgoing connectons. There is a notice in the forums, it seems they are working on it, although it is about 4AM EST so they are low staff. http://forums.burst.net/showthread.p...801-30-2011%29
Posted by DamienSB, 01-30-2011, 06:02 PM
It seems to be fixed now - but there was no response posted in the forums. Or did it randomly resolve and burst doesn't know what happend?
Posted by lorph, 01-30-2011, 06:21 PM
I have a server with Volume Drive (also in Scranton) and it keeps losing connection to the internet...
Posted by quadix, 01-30-2011, 06:32 PM
If you are having any network issues with us. Please open a support ticket.
Posted by lorph, 01-30-2011, 06:48 PM
I am buying it from someone colocated in your facility so I don't have a volumedrive account. I am pretty sure its not their fault because my IP is becoming randomly unroutable.
Posted by quadix, 01-30-2011, 06:55 PM
Please have your reseller contact us about the issue.
Posted by JayCTN, 01-30-2011, 11:09 PM
Problem continues to happen... Packets are playing ping-pong outbound from the server... Seems very strange, maybe some kind of IPS/ anti-ddos protection gone wrong? It's been almost 24 hours since they updated my ticket or the website.
Posted by jstand1, 01-30-2011, 11:55 PM
I'm having the same problem right now- again.
Posted by JavaV, 01-31-2011, 01:30 AM
We haven't had any issues that we noticed (50+ active services we monitor).
Posted by amotic, 01-31-2011, 01:58 AM
my vps still not fix,still cannot connect it, more 10 hours already. I have submitted ticket,now is waiting. my ip address 173.212.227.6x
Posted by Dsrv, 01-31-2011, 02:02 AM
Seem fine for me over here, only got about 74 IP's with them
Posted by bsdvps, 01-31-2011, 02:18 AM
Mine went down recently too I'm 173.212.220.x
Posted by JavaV, 01-31-2011, 02:35 AM
I take that back. We seem to have about 10~ VPS's down. Hope it gets fixed soon.
Posted by KMyers, 01-31-2011, 02:49 AM
Hello,
Posted by Dsrv, 01-31-2011, 02:56 AM
184.82.xxx.xx Great, now time to join the gang, 15 vm's now down
Posted by KMyers, 01-31-2011, 02:57 AM
Welcome to the club
Posted by JavaV, 01-31-2011, 02:57 AM
We just had a few more servers go down. Not good
Posted by Dsrv, 01-31-2011, 03:00 AM
The one previously posted, back now. I hope the other node don't go down next, burstnet have caused me some serious issues this last 2 months, clients screaming
Posted by JavaV, 01-31-2011, 03:03 AM
BurstNET has been very solid the past two months. What issues are you talking about? This is the first network outage they have since being with them (for about a year now - and not including the Thanksgiving power outage).
Posted by Dsrv, 01-31-2011, 03:05 AM
Not network, the server and the block I was on, the power was overloading in certain places so they had to change it of course. Then there is just a hand full of issues with a server I had, however we sorted it out eventually, they are very good, would recommend them to anyone. They keep me happy
Posted by KMyers, 01-31-2011, 03:10 AM
One of my VMs just came online, however the one I am really wanting is not reachable yet
Posted by JavaV, 01-31-2011, 03:13 AM
My apologies. I seem to get very defensive when it comes to burstnet and network issues (customers complaining/ accusing), because they have been *very* good for a long time.
Posted by ramnet, 01-31-2011, 03:20 AM
Burst's network has been glitching a fair bit lately. We will probably be relocating what little we have left hosted in their facility elsewhere with the rest of our gear.....all the issues lately with packet loss network glitches the explosion......just a bit much at once. Last edited by ramnet; 01-31-2011 at 03:32 AM.
Posted by UpdownUp, 01-31-2011, 03:27 AM
Great news, UpDownUp is Up again! (Scranton *2 were down) Hope everyone else is coming back now too... Last edited by UpdownUp; 01-31-2011 at 03:30 AM.
Posted by Dsrv, 01-31-2011, 03:28 AM
They are very good, at times, but still have many downfalls. But over the years I have seen many changes for the best, so I will keep faith for now.
Posted by JonFatino, 01-31-2011, 03:29 AM
I have a few vps in all BurstNet locations Some are 80% packet loss some are 100% packet loss in PA data center here is some ping graphs http://img201.imageshack.us/img201/5...rstpagraph.png But some of my vps just came back online 100% packet throughput. (Jan 30 2011 11:31 PST) Others still lots of loss. Looks like they are working on the issue. Last edited by JonFatino; 01-31-2011 at 03:33 AM.
Posted by scrapme, 01-31-2011, 03:42 AM
They are having tough time from last two days. No consistent uptime or support. For support you need to wait for hours.
Posted by KMyers, 01-31-2011, 03:55 AM
Hello, I just got the message below from Burst, which confirms they are aware (and maybe at fault) At this time, there is an issue within our network which may be causing packet loss and other problems with your connectivity. Our engineers are diligently working to resolve this and everything should be back to normal
Posted by scrapme, 01-31-2011, 04:03 AM
I am getting the same response from yesterday
Posted by Rick-WHSuite, 01-31-2011, 05:36 AM
We're seeing the same issues overnight. Its got to the point where I don't put a ticket in as I know it'll be a good 10 hours before I get a response, and by then its resolved...after the issues last month (granted, uncontrollable) and an issue where a drive failed and it took them a WEEK to resolve the situation, we've started relocating to another DC. Sure, it'll cost a bit more, but save a LOT in headaches.
Posted by JayCTN, 01-31-2011, 09:03 AM
It appears to be a very selective problem We have ~20 IPs we monitor, it's only happening on a single IP, and only from certain IPs... it's not acting like a standard routing issue.
Posted by shearerc, 01-31-2011, 09:04 AM
I'm at Burst LA - 184.82.2xx.xxx Massive 60-70% packetloss about 30 mins ago. Seems to have been fixed at time of this post. My guess is that they were making changes(improvement) to their routes and something went astray. Last edited by shearerc; 01-31-2011 at 09:08 AM.
Posted by JayCTN, 01-31-2011, 09:11 AM
Here is my frustration with Burst... Lack of communication, no updates in ~30 hours on either their forums or my open trouble ticket. It appears right this second the problem is resolved, but without an update who knows? I understand budget provider, but since when does budget provider = no update in 24+ hours on an outage?
Posted by Rick-WHSuite, 01-31-2011, 09:21 AM
Would have been nice if they would have notified customers. Instead they ignore them
Posted by bsdvps, 01-31-2011, 11:35 AM
Seemed like a routing issue
Posted by KMyers, 01-31-2011, 03:54 PM
Is anyone seeing a repeat?
Posted by scrapme, 01-31-2011, 03:55 PM
Oh man I think they are worst not Burst. Service again down.... any one else facing the issue right now?
Posted by scrapme, 01-31-2011, 03:56 PM
Yes... unfortunately
Posted by ramnet, 01-31-2011, 04:01 PM
Looks like their BGP feed dropped.
Posted by KMyers, 01-31-2011, 04:01 PM
What is your IP range
Posted by infracom2005, 01-31-2011, 04:03 PM
again 64.xxx and 184.xxx offline
Posted by scrapme, 01-31-2011, 04:05 PM
184.82.x.xx
Posted by Matthew_B, 01-31-2011, 04:22 PM
Down again for me 64.191.xxx etc
Posted by toma1708, 01-31-2011, 04:25 PM
Down for me too, no answer received until now (+3 hours down). 96.9.x.x Catalin
Posted by JavaV, 01-31-2011, 04:38 PM
We also seem to be experiencing some issues.
Posted by scrapme, 01-31-2011, 04:51 PM
Services are back online but don't know for how much time.
Posted by toma1708, 01-31-2011, 05:13 PM
For you probably, my server is still down and unfortunately, the tech support does not answer and no update is provided on the forums.
Posted by toma1708, 01-31-2011, 07:02 PM
Really speaking I did not expect to receive no answer to my tickets after almost 7 hours of downtime. No customer service reaction, no technical support reaction, nothing. What a waste!
Posted by JavaV, 01-31-2011, 07:04 PM
You sure it's not just your server now? Haven't had any problems now for a few hours.
Posted by toma1708, 01-31-2011, 07:08 PM
Please check 96.9.176.5, my monitoring says it's down, I can't connect and it is unreachable via traceroute from two Europe locations.
Posted by Rick-WHSuite, 01-31-2011, 07:08 PM
Unfortunately thats not rare - Burst are strange. One day you'll get a response within 5 seconds. The next it'll take 24+ hours. At this point I would say if you care about a fast response, find a new provider as Burst have proven over the years that this is something they lack - despite what they may try and swing on WHT. You cant complain too much though...the prices are/were a lot lower than the competition. Edit: also @toma1708 - 96.9.176.5 down for me from the UK.
Posted by toma1708, 01-31-2011, 07:12 PM
The prices are low if you receive a decent service, when you receive a 7 hours downtime and no support reaction, the price is quite high. Speaking about prices, you can find good offers by adding some extra $ (not much though)to the price paid to them.
Posted by Rick-WHSuite, 01-31-2011, 07:26 PM
If you compare Bursts prices to others on the east-coast they are a lot cheaper. Especially for hardware upgrades. How many providers do you know that offer Hardware RAID 10 for $14.95 extra /month? You get what you pay for I guess!
Posted by toma1708, 01-31-2011, 07:35 PM
I get less than I paid for the time being. The network issues are 2 weeks old, my only mistake is that I haven't moved this server too and trusted them. I'm paying the price now and have already 4 clients who canceled because of these issues. I assume they work to fix any issues they have but droping a line to a customer isn't too much (I think).
Posted by JavaV, 01-31-2011, 09:26 PM
Did you open a Reboot ticket to get a faster response? They normally respond within minuets when opening a ticket in the reboot department.
Posted by toma1708, 01-31-2011, 09:45 PM
Thanks, I'll try that.
Posted by toma1708, 01-31-2011, 09:58 PM
OPened a ticket 10 minutes ago, waiting ...
Posted by toma1708, 01-31-2011, 10:25 PM
Very sad. Ticket ... 374 - opened 10 hours ago - NO answer Ticket ... 924 - opened 7 hours ago - NO answer Ticket ...412 - opened 3.5 hours ago - answered, asking for the other tickets Ticket (reboot) - opened 40 minutes ago - NO answer yet
Posted by DamienSB, 01-31-2011, 10:42 PM
Well stop flooding the helpdesk. If they get to many tickets they will mass close them all and then nobody will get a response. Tickets are answered in the order as they get them (as every place does) so dont keep replying to the same ticket screaming OMG WHAT IS GOING ON because you are just bumping yourself down the list each time you make a ticket response.
Posted by toma1708, 01-31-2011, 10:49 PM
You're right, however, I wouldn't call 3 tickets for a server down for 10 hours a flood I have called, spoke to somebody from the support, keep my fingers crossed.
Posted by DamienSB, 01-31-2011, 10:55 PM
Yeah, 3-4 tickets alone isnt anything, but when you hvae 200 people doing that same thing... More than just your service is effected (as this thread proves). What did the person in support say?
Posted by toma1708, 01-31-2011, 11:05 PM
They rebooted the server and it came online, the route is still strange but at least I can access the machine.
Posted by DamienSB, 01-31-2011, 11:12 PM
The only problem i have is that sometimes the server cannot connect to others to sync such as rdate.cpanel.net, update and sometimes it wont connect to the other cpanel servers (xml-api), but other then that everything else is fine.
Posted by DamienSB, 02-01-2011, 02:52 AM
BAhh!!!!! The issue is back... root@server1 [~]# tracert www.stopforumspam.com traceroute to www.stopforumspam.com (208.91.135.54), 30 hops max, 40 byte packet 1 64-191-78-113.hostnoc.net (64.191.78.113) 1.103 ms 1.152 ms 1.290 ms 2 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.678 ms 0.721 ms 1.009 m s 3 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.469 ms 1.525 ms 1.644 m s 4 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.991 ms 1.048 ms 1.095 m s 5 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.666 ms 2.135 ms 2.782 m s 6 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 1.120 ms 0.669 ms 0.932 m s 7 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.640 ms 1.668 ms 0.394 m s 8 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.489 ms 0.511 ms 0.672 m s 9 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.462 ms 0.575 ms 0.705 m s 10 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.410 ms 0.439 ms 0.482 m s 11 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.379 ms 0.342 ms 0.367 m s 12 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.322 ms 0.371 ms 0.396 m s 13 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.445 ms 1.651 ms 1.779 m s 14 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.327 ms 0.562 ms 0.583 m s 15 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.958 ms 0.899 ms 0.987 m s 16 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.471 ms 0.400 ms 0.424 m s 17 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.357 ms 0.928 ms 0.985 m s 18 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.349 ms 0.409 ms 0.460 m s 19 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.458 ms 0.515 ms 0.564 m s 20 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.364 ms 0.496 ms 0.652 m s 21 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.557 ms 1.072 ms 1.097 m s 22 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.445 ms 0.494 ms 0.379 m s 23 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 2.217 ms 1.709 ms 1.950 m s 24 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.453 ms 0.448 ms 0.473 m s 25 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 1.213 ms 0.784 ms 0.809 m s 26 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.461 ms 0.513 ms 0.419 m s 27 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.849 ms 0.934 ms 0.419 m s 28 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.482 ms 0.534 ms 0.530 m s 29 xe1-03.agg02.sctn01.hostnoc.net (64.120.243.30) 0.629 ms 0.686 ms 0.704 m s 30 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 0.499 ms 0.587 ms 0.634 m s root@server1 [~]#
Posted by ramnet, 02-01-2011, 02:53 AM
Routing loop.....lovely.
Posted by KMyers, 02-01-2011, 02:54 AM
Ok, this is starting to get VERY OLD VERY Quickly, I wish Burst would comment on this post
Posted by jstand1, 02-01-2011, 02:56 AM
One of my IPs just went down again.... Come on man WTF?
Posted by DamienSB, 02-01-2011, 02:56 AM
I bet its because somebody ****ed up somthing. This is the second routing/network related issue ive had in the last 6 months. The first time a set of (5) IPs randomly droped from the vlan, as they said. Also, i wonder if homeless people get knock knock jokes...
Posted by DamienSB, 02-01-2011, 02:59 AM
Im to lazy to actuley read the whole thing: http://burst.net/policy/sla.shtml but does the outages from this fall under "exceptions" or does it break the SLA?
Posted by KMyers, 02-01-2011, 03:00 AM
This is the 4th time in the past 48 hours. My stuff there is seeing around 70% uptime in the past 48 hours.
Posted by KMyers, 02-01-2011, 03:05 AM
As this outage is "within" the burst network, I am filing for the SLA credit (once secure.burst.net comes back online as it is also impacted )
Posted by DamienSB, 02-01-2011, 03:12 AM
It also seems they have an SSL error on there website. secure.burst.net xD
Posted by scrapme, 02-01-2011, 03:25 AM
Agaaaaaaain down How they are running business from so long with such a pathetic services. I am a new user on their board and I dont think will continue once my contract is expired.
Posted by DamienSB, 02-01-2011, 03:36 AM
you have a contract with burst? they dont make you sign contracts... you can leave at any time.
Posted by scrapme, 02-01-2011, 03:40 AM
With contract I mean the pre-paid amount for long term.
Posted by DamienSB, 02-01-2011, 03:52 AM
bad move eh? lol i baught only the IP address alocations long term, everything else is monthly, because the IP's were cheaper by year and wasnt enough to where it wouldnt matter if i left them hanging for months.
Posted by HostJedi, 02-01-2011, 04:04 AM
That is no longer in usage. . .
Posted by HostJedi, 02-01-2011, 04:07 AM
There is nothing wrong with our services, or our network/routing performance. Obviously, there is something going on behind the scenes, causing these issues you have been experiencing, which we are not discussing publicly here for a reason. I can tell you there is nothing wrong internally with our network or routing, but any further details will have to wait for a bit yet. It will make sense soon enough... . .
Posted by HostJedi, 02-01-2011, 04:09 AM
These issues are NOT 2 weeks old, and this only has been sporadic thru the course of the past weekend. . .
Posted by HostJedi, 02-01-2011, 04:10 AM
We cannot yet, and for good reason, which will make sense soon enough, once we can explain the issue in further detail. It is for our clients own good that information is not being made public yet. . .
Posted by KMyers, 02-01-2011, 04:15 AM
Hello,
Posted by DamienSB, 02-01-2011, 04:24 AM
Then why do you link to it?
Posted by HostJedi, 02-01-2011, 05:06 AM
Can you supply the specific link/page you are seeing this please? We'll have the HTML updated on that... Thanx... . .
Posted by HostJedi, 02-01-2011, 05:07 AM
Generic answer from our support techs for a reason. I have PM'd you, and I'm sure you understand why now... . .
Posted by KMyers, 02-01-2011, 05:08 AM
Your SLA Form is housed there (it was also linked to by yout support team) https://secure.burst.net/orders/db/sla/form.shtml
Posted by HostJedi, 02-01-2011, 05:15 AM
Ahh...OK, thanks..we'll get that patched up. It's functional, just the cert expired.
Posted by Rick-WHSuite, 02-01-2011, 05:33 AM
Read your PM from Burst - It'll all make sense after that
Posted by KMyers, 02-01-2011, 05:34 AM
It did (Ten Chars)
Posted by roro, 02-01-2011, 12:23 PM
I cant access my server from Mexico 1 1 ms 1 ms 1 ms home [192.168.1.254] 2 9 ms 11 ms 9 ms dsl-servicio-l200.uninet.net.mx [200.38.193.226] 3 40 ms 41 ms 40 ms bb-mex-vallejo-50-tge0-1-0-0.uninet.net.mx [201. 125.61.62] 4 40 ms 41 ms 41 ms bb-dallas-bryan-10-pos0-15-2-0.uninet.net.mx [20 1.125.72.26] 5 40 ms 41 ms 84 ms 12.90.228.17 6 42 ms 43 ms 41 ms cr1.dlstx.ip.att.net [12.122.100.6] 7 40 ms 41 ms 41 ms ggr6.dlstx.ip.att.net [12.122.139.109] 8 67 ms 66 ms 66 ms 192.205.36.182 9 67 ms 66 ms 66 ms te2-4.ccr02.dfw01.atlas.cogentco.com [154.54.6.6 1] 10 71 ms 70 ms 70 ms te0-1-0-1.ccr22.iah01.atlas.cogentco.com [154.54 .5.138] 11 73 ms 72 ms 72 ms te7-8.ccr02.atl01.atlas.cogentco.com [66.28.4.89 ] 12 74 ms 72 ms 72 ms te0-1-0-6.ccr22.dca01.atlas.cogentco.com [154.54 .7.210] 13 77 ms 78 ms 76 ms te3-3.ccr01.phl01.atlas.cogentco.com [154.54.31. 58] 14 76 ms 78 ms 76 ms te3-4.ccr01.phl03.atlas.cogentco.com [154.54.0.1 90] 15 81 ms 82 ms 80 ms 38.104.114.214 16 * * * Tiempo de espera agotado para esta solicitud. 17 88 ms 88 ms 88 ms ec1-25.gwy02.sctn01.hostnoc.net [96.9.191.141] 18 * * * Tiempo de espera agotado para esta solicitud. 19 *
Posted by KMyers, 02-01-2011, 12:31 PM
It appears to be happening once more.
Posted by roro, 02-01-2011, 12:33 PM
This SUCKS!!!!!!!!!!!!!!!!!!!!!!!!!!
Posted by Rick-WHSuite, 02-01-2011, 12:44 PM
Yup happening on a couple of our IP ranges too.
Posted by JavaV, 02-01-2011, 12:46 PM
All the best for BurstNET to get this resolved. I know what they are going through, and how much work, and probably money they are putting into resolving this issue.
Posted by shearerc, 02-02-2011, 02:01 AM
Hmm I wonder what of sort of issue they are going through now that can't be revealed to the public...
Posted by ramnet, 02-02-2011, 02:06 AM
I happen to know what the issue is and while I'll respect Burst's wish for it not to be posted in public on webhostingtalk I find it pathetic that they feel this way and I don't think their keeping this particular situation private is preventing any further harm to Burstnet.
Posted by HostJedi, 02-02-2011, 02:12 AM
Then you are naive and know nothing about dealing with such matters... Nor could you even make an educated statement like that without possibly knowing any details/specifics of the matter either. Blah...complete hogwash from you...meant to do nothing but incite others and flame. . .
Posted by ramnet, 02-02-2011, 02:14 AM
You could certainly generalize the situation and make a statement without getting into any specifics. But it's your problem not mine so .... good luck with that.
Posted by HostJedi, 02-02-2011, 02:17 AM
In our judgment, which is far more advanced and knowledgeable about the specifics/details of the issue than yours, NO, we couldn't and shouldn't, as doing so could only be problematic. By tomorrow I would expect we can release a little information, as issue should be mute by then. . .
Posted by ramnet, 02-02-2011, 02:25 AM
Well...glad to hear it then. I guess I can't blame you too much for being paranoid after all....lesser hosts would probably have a much tougher time taking care of things under the circumstances. PR-wise tho you should have just stayed silent instead of saying we know what the issue is and it's none of your business.....only serves to enrage the client base more when you answer them like that. Network issues bring back memories of the times before burstnet upgraded their network. In any case, looking forward to your official word. Last edited by ramnet; 02-02-2011 at 02:33 AM.
Posted by HostJedi, 02-02-2011, 02:33 AM
We never said it was "none of your business" to anyone... Though, if you are not a client, it isn't. And yes, this would definitely have affected a smaller host much much worse....possibly a business killer. Fortunately we have talented network engineering that has been able to deal with it as well as can be expected. . .
Posted by DamienSB, 02-02-2011, 02:35 AM
Theyre being held hostage by a monkey armed with coconuts and sand.
Posted by ramnet, 02-02-2011, 02:36 AM
I was paraphrasing And I'm a client of one of your clients so Good night and good luck.
Posted by ramnet, 02-02-2011, 02:48 AM
Only question is which one is the annoying monkey and which one is the 500 lb gorilla I'll bring the barrel organ Nice of you to sneak that in there ... don't take things so personal ... I'm an equal opportunity Typical after a lengthy evaluation a few months after turning up production services inside BurstNET the sh!t hits the fan......just my rotten luck I guess Last edited by ramnet; 02-02-2011 at 02:53 AM.
Posted by shearerc, 02-13-2011, 02:57 PM
So, with the prob seemingly gone by now, what does Burst has to say about what went on? Nothing in the forums.....
Posted by HostJedi, 02-14-2011, 02:22 PM
There was a large-scale coordinated DDOS attack from a well-known hacking conglomerate underway. They knew what they were doing, were very talented/knowledgeable on exactly what/where to attack, when, and how. They are known to be active on several public forums, including WHT---and we knew they were watching to see what info released and how to co-ordinate/adjust their attack methods based on such. We decided it was best to not give them any information to help them, and let it runs it's course, block as much and as best possible during the attack, without provoking them or giving them info on how to make it worse, or even let them know if they were being successful at it or not. . .
Posted by AdamD, 02-17-2011, 07:58 AM
Can anyone get the burstnet EU site to load? I just get a blank white page and my VPS has suddenly become inaccessible. http://www.burstnet.eu/ Seems to be back, but I couldn't ping either my VPS or the site.
Posted by BurstNET_CSM, 02-17-2011, 09:22 AM
We did not receive any tickets or phone calls in or around that time. So it was either a very minor hiccup at our datacenter (Not likely due to no tickets or calls), or there was a problem in your route to the site (Next time this happens, do a traceroute to your VPS and open a ticket with us if the problem seems to be at our end.
Posted by AdamD, 02-17-2011, 06:06 PM
Will do Thanks for that.