burst.net vps downtime

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > burst.net vps downtime

Posted by cyberls, 08-18-2011, 10:10 AM
burst.net rebooted a VPS more than 60 times in last 4 days due to a problem that is NOT from our side.

reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:58 (01:08)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:07 (01:12)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 09:54 (01:25)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:42 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:08 (01:45)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:58 (01:09)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:48 (01:18)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:37 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:16 (01:31)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 04:05 (01:11)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 03:24 (01:51)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 02:11 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 23:52 (03:31)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 22:41 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 20:37 (03:14)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 19:27 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 18:34 (02:03)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 18:34 (00:09)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 17:23 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 16:40 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:27 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:21 (01:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:08 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:25 (00:55)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 13:10 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 12:08 (02:15)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 10:55 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 08:20 (03:47)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 07:07 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 06:01 (02:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:47 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:06 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:53 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:34 (01:30)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:20 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:06 (01:27)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 15:42 (10:51)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:28 (01:13)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:30 (01:11)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 13:14 (01:14)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 10:28 (04:00)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 09:19 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 08:46 (01:42)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 07:36 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:59 (03:45)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:48 (01:10)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:31 (00:28)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:17 (01:12)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 22:02 (06:27)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 20:52 (01:09)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 17:52 (04:08)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 16:40 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 18:44 (23:06)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 17:33 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 08:22 (10:21)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:12 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:10 (01:11)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 05:57 (01:12)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 16:56 (14:13)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 15:41 (01:13)
reboot system boot 2.6.18-194.8.1.e Thu Aug 4 09:41 (9+07:14)

The VPS is still down, but no response from the technicians through tickets. Can someone advise on what can be done to get things back to normal ?
Posted by IraqiGeek, 08-18-2011, 11:00 AM
Hi Mate,

I had the same problem yesterday. Took several tickets and a thread here on WHT to get someone to look at the issue.

My VPS was down yesterday for 12 hours and then as good as unreachable for another 4 hours.

You are not alone in this situation, as you can see in my thread about the downtime
Posted by joshuamallow, 08-18-2011, 11:21 AM
For what its worth with all this burst.net hate going on today....My Scranton, PA VPS with Burst.net is great...fast, reliable, and no downtime at all that I've noticed.
Posted by cyberls, 08-18-2011, 11:47 AM
it was like that in the beginning, but not anymore
Posted by F-DNS, 08-18-2011, 11:48 AM

Quote:

Originally Posted by IraqiGeek

You are not alone in this situation, as you can see in my thread about the downtime

Different issue - Those messages come from a Linux system. It sounds like Burst really have their hands full today

Maybe we should arrange an airdrop of pizzas for the support guys (and a couple of cans of Guinness for the boss)
Posted by SerayaHost, 08-18-2011, 12:10 PM
Hello,

Seems that BurstNet has pretty a lot of issue seing that a lot of thread here on wht complaining their service.
But if I can see, their issue almost nearly not from their Scranton DC, but their other DC.
Posted by IraqiGeek, 08-18-2011, 12:14 PM
cyberls,

Where is your VPS located?
Posted by BurstNET_CSM, 08-18-2011, 12:50 PM
Can you please verify if this is a windows or linux vps? Also, have you opened a ticket with our support department?
Posted by F-DNS, 08-18-2011, 04:19 PM
@BurstNET_CSM - Whilst my guessing isn't on the best of form today (from the other thread ) that "reboot system boot 2.6.18-194.8.1.e" is the start of the name of a Linux kernel, so it's not Windows. He also mentioned "but no response from the technicians through tickets" (although that was then, it/they may be replied to now, of course).
Posted by BurstNET, 08-18-2011, 11:19 PM

Quote:

Originally Posted by F-DNS

@BurstNET_CSM - Whilst my guessing isn't on the best of form today (from the other thread ) that "reboot system boot 2.6.18-194.8.1.e" is the start of the name of a Linux kernel, so it's not Windows. He also mentioned "but no response from the technicians through tickets" (although that was then, it/they may be replied to now, of course).

Our Windows VPS servers actually run on top of Linux... ;-)
Regardless, we have tracked the issue down to a recent MS Windows Update failure going around, that kicked the heck out of our Windows nodes recently.
Most nodes are running better right now, and we are working on a permanent solution to avoid such a Microsoft failure affecting us in the future, and that should be in place by next we we expect.
.
.
Posted by cyberls, 08-19-2011, 02:36 AM
Here is a good picture of what happened -

A total of 77 reboots in a week :

reboot system boot 2.6.18-194.8.1.e Fri Aug 19 08:43 (00:05)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 07:33 (01:09)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 07:48 (00:54)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 06:40 (01:07)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 05:58 (01:49)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 04:51 (01:06)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 21:49 (08:08)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 20:42 (01:06)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 19:47 (02:00)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 17:11 (04:37)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 16:12 (05:36)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 14:54 (01:17)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 14:40 (01:31)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 13:23 (01:16)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 13:29 (01:09)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 12:12 (01:16)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 12:16 (01:12)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:58 (01:18)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:07 (01:12)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 09:54 (01:25)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:42 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:08 (01:45)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:58 (01:09)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:48 (01:18)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:37 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:16 (01:31)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 04:05 (01:11)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 03:24 (01:51)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 02:11 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 23:52 (03:31)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 22:41 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 20:37 (03:14)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 19:27 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 18:34 (02:03)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 17:23 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 16:40 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:27 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:21 (01:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:08 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:25 (00:55)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 13:10 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 12:08 (02:15)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 10:55 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 08:20 (03:47)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 07:07 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 06:01 (02:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:47 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:06 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:53 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:34 (01:30)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:20 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:06 (01:27)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 15:42 (10:51)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:28 (01:13)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:30 (01:11)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 13:14 (01:14)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 10:28 (04:00)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 09:19 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 08:46 (01:42)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 07:36 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:59 (03:45)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:48 (01:10)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:31 (00:28)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:17 (01:12)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 22:02 (06:27)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 20:52 (01:09)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 17:52 (04:08)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 16:40 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 18:44 (23:06)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 17:33 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 08:22 (10:21)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:12 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:10 (01:11)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 05:57 (01:12)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 16:56 (14:13)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 15:41 (01:13)

The technicians have failed to provide the reason for reboots.

Quote:

The VPS is currently online and responding to connections. Nothing has been done with this container from the main node since June, so I don't know why it was rebooted. You may find more information in the VPS logs.

Here are the logs just before a reboot :
Code:
top - 08:00:04 up 12 min,  1 user,  load average: 0.67, 0.42, 0.25
Tasks:  69 total,   2 running,  65 sleeping,   0 stopped,   2 zombie
Cpu(s): 13.1%us, 67.1%sy,  0.0%ni,  0.0%id, 19.8%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1048800k total,   242648k used,   806152k free,        0k buffers
Swap:        0k total,        0k used,        0k free,        0k cached
As you can see, there is no load caused from this VPS. But the reply from Burst states :

Quote:

This seems it has been suspended due to overusing resources. It seems that it was most likely caused by mysql.

vzctl exec 27088 pstree
Warning: Unknown iptable module: ipt_recent, skipped
init-+-clamd---{clamd}
|-cpanellogd---cpanellogd
|-cphulkd
|-cpsrvd-ssl---cpsrvd.so
|-crond
|-exim---exim
|-exim-+-exim---exim---exim
| `-exim
|-httpd-+-25*[httpd]
| `-leechprotect
|-mysqld_safe---mysqld---10*[{mysqld}]
|-named---bash---named---named---3*[{named}]
|-pstree
|-pure-authd
|-pure-ftpd
|-queueprocd
|-saslauthd---saslauthd
|-spamd---spamd
|-sshd
|-syslogd
|-tailwatchd---tailwatchd
|-udevd
`-xinetd

With a load of ~10

Is this VPS the 88th on a same hardware ?

And Burst do not give proper information about CPU on their website when they sell VPS-es . Their CPU core is limited to one.

# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 2400.123
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 4800.24
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

So that means, this VPS was causing only 0.67/4 = effective 0.1675 of CPU load.

Another VPS might be causing the load, but the technicians fail to find and fix it. Results are = every others on this node suffer. And I guess there should be many, many !

And while I am writing this, I see :
Code:
Broadcast message from root (Fri Aug 19 12:03:39 2011):

The system is going down for system halt NOW!
Posted by BurstNET, 08-19-2011, 03:42 AM

Quote:

Originally Posted by IraqiGeek

Hi Mate,

I had the same problem yesterday. Took several tickets and a thread here on WHT to get someone to look at the issue.

My VPS was down yesterday for 12 hours and then as good as unreachable for another 4 hours.

You are not alone in this situation, as you can see in my thread about the downtime

Your issue is different.
You had a Windows VPS which was having issues due to Microsoft Windows Updates failing..caused by Microsoft and a faulty update.
.
.
Posted by BurstNET, 08-19-2011, 03:49 AM
Quote:

Originally Posted by cyberls

Here is a good picture of what happened -
A total of 77 reboots in a week :
The technicians have failed to provide the reason for reboots.

There is no way that we rebooted your VPS intentionally that many times.
A few reboots at most, maybe, but that many, no way it was a human.
Obviously something is wrong there.
Quote:
Originally Posted by cyberls
Here are the logs just before a reboot :
Code:
top - 08:00:04 up 12 min,  1 user,  load average: 0.67, 0.42, 0.25
Tasks:  69 total,   2 running,  65 sleeping,   0 stopped,   2 zombie
Cpu(s): 13.1%us, 67.1%sy,  0.0%ni,  0.0%id, 19.8%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1048800k total,   242648k used,   806152k free,        0k buffers
Swap:        0k total,        0k used,        0k free,        0k cached
As you can see, there is no load caused from this VPS. :
I wouldn't say that....you are overusing our default defined resources on your VPS:
from the logs: "Fatal resource shortage: numiptent, UB 27088."
...I have now raised that up for you.
You are the only one with errors of the sort on that node, based on the logs.

Quote:

Originally Posted by cyberls

Is this VPS the 88th on a same hardware ?

No...there is less than a dozen on there.

Quote:

Originally Posted by cyberls

And Burst do not give proper information about CPU on their website when they sell VPS-es . Their CPU core is limited to one.

Every node we have is different.
Most of our newer nodes in the past year are all Dual Quad Core Xeon E56**.
The node this VPS is on, is one of our oldest, and the minimum config we use for basic VPS.

Another VPS might be causing the load, but the technicians fail to find and fix it. Results are = every others on this node suffer. And I guess there should be many, many !

And while I am writing this, I see :
Quote:
Originally Posted by cyberls
Code:
Broadcast message from root (Fri Aug 19 12:03:39 2011):
The system is going down for system halt NOW!
I would update your support ticket with details that the vps is rebooting constantly for no known reason. The support dept will get to the bottom of it...
.
.
Posted by BurstNET, 08-19-2011, 03:51 AM

Quote:

Originally Posted by SerayaHost

Hello,

Seems that BurstNet has pretty a lot of issue seing that a lot of thread here on wht complaining their service.
But if I can see, their issue almost nearly not from their Scranton DC, but their other DC.

Quote:

Originally Posted by joshuamallow

For what its worth with all this burst.net hate going on today....My Scranton, PA VPS with Burst.net is great...fast, reliable, and no downtime at all that I've noticed.

Most of the complaints here in the past 24-48 hours are all due to Windows VPS nodes getting overloaded due to failed Microsoft Updates caused by a defective update Microsoft passed thru. This was not our fault or doing, but of course gets blown up as "burstnet sucks" around WHT, as sensationalism is just how things are done around here. This is not the level of service we provide, and the cause had absolutely nothing to do with us really. We are working on a solution to make such things not affect our Windows VPS nodes so much in the future, but this was not something we caused, failed to do, or did wrong. You can thank Microsoft for these issues recently...
.
.
Posted by xashost, 08-19-2011, 12:54 PM
Does anyone know what this particular Windows update is? Does it affect most versions of Windows or not?
Posted by BurstNET_CSM, 08-20-2011, 03:24 PM
Hi everyone.

The exact issue here (Multiple multiple reboots) was twofold, and separate from the windows update issue.

Let's start off right: This is not a windows server but a Linux server. Somehow, the server had been set to reboot after a kernel panic (Not a thing you want your server set at IMHO). That was problem one. We didn't know of the issue because no server was "down", per se, and not one other client had brought this to our attention. The reboot feature has been turned off for the server.

Which brings us to point #2 - What was causing the kernel panics? We traced that to a singular user who was abusing the living bejeezus out of the server. We've seen to that as well.

So the OP should be seeing a fine running system again.
Posted by cyberls, 08-22-2011, 01:37 AM

Quote:

Ticket ID: 2824048
Status: OPEN
When Created: 08-17-2011 - 08:51AM
Elapsed Time: 5 days
Since Last Action: 3 days

ticket untouched for last 3 days !
Posted by cutabovehost, 08-22-2011, 01:46 AM
Glad to see the Burstnet response. It makes me feel more like they are working to change the negative things I had read by posters.
Posted by Matt R, 08-22-2011, 02:18 AM
Now if they could only activate our support accounts I'd be happy so I can actually open a ticket...

Sent BurstNET $529 for a years service two weeks ago only to find that a few days later, the host node horribly failed and lost all of our data backups from everything we migrated away from Softlayer that we'd built up from the past few years. Since we can't open tickets since their support system won't validate our accounts without working/matching email, we're boned.

What a great thing to find first thing in the morning after coming back into the country. Hopefully they'll mail a refund check or something once we finally manage to log in.
Posted by cutabovehost, 08-22-2011, 02:29 AM
Had that happen once before. Now I use multiple redundant backups, And test regularly. It really hurts when you loose your data.
Posted by Matt R, 08-22-2011, 02:41 AM

Quote:

Originally Posted by cutabovehost

Had that happen once before. Now I use multiple redundant backups, And test regularly. It really hurts when you loose your data.

I've still got hard copies of our SQL databases, so we've got the absolute most important stuff. It's just aggravating to deal with total failure on a "brand new server" in their "Premium VPS" line when paid annually only days after receiving it.

We barely had it long enough to take a backup of everything once set back up, not that it's an excuse for not taking a backup.
Posted by cutabovehost, 08-22-2011, 04:19 AM
Did you ever get the situation resolved yet?
Posted by BurstNET_CSM, 08-22-2011, 06:45 AM
Re: signing up at support.burst.net: please send your support requests (including one regarding this exact issue) to support@burst.net
Posted by cyberls, 08-22-2011, 11:36 PM
more downtime :

reboot system boot 2.6.18-194.8.1.e Mon Aug 22 11:28 (21:31)
reboot system boot 2.6.18-194.8.1.e Mon Aug 22 10:22 (01:05)
reboot system boot 2.6.18-194.8.1.e Mon Aug 22 01:56 (09:31)
reboot system boot 2.6.18-194.8.1.e Mon Aug 22 00:51 (01:04)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 21:13 (1+04:42)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 20:06 (01:06)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 12:49 (08:23)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 11:42 (01:06)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 08:57 (03:51)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 07:50 (01:06)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 02:14 (06:43)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 01:05 (01:08)
reboot system boot 2.6.18-194.8.1.e Sat Aug 20 00:02 (02:11)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 22:54 (01:07)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 16:37 (07:24)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 15:30 (01:06)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 15:12 (01:25)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 14:01 (01:11)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 14:16 (00:56)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 13:06 (01:09)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 13:19 (00:56)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 13:15 (00:02)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 12:07 (01:11)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 12:04 (01:14)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 10:54 (01:09)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 11:06 (00:57)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 09:55 (01:10)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 08:43 (02:22)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 07:33 (01:09)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 07:48 (00:54)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 06:40 (01:07)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 05:58 (01:49)
reboot system boot 2.6.18-194.8.1.e Fri Aug 19 04:51 (01:06)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 21:49 (08:08)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 20:42 (01:06)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 19:47 (02:00)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 17:11 (04:37)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 16:12 (05:36)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 14:54 (01:17)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 14:40 (01:31)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 13:23 (01:16)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 13:29 (01:09)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 12:12 (01:16)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 12:16 (01:12)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:58 (01:18)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 10:07 (01:12)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 09:54 (01:25)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:42 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 08:08 (01:45)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:58 (01:09)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 06:48 (01:18)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:37 (01:10)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 05:16 (01:31)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 04:05 (01:11)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 03:24 (01:51)
reboot system boot 2.6.18-194.8.1.e Thu Aug 18 02:11 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 23:52 (03:31)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 22:41 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 20:37 (03:14)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 19:27 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 18:34 (02:03)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 17:23 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 16:40 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:27 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 15:21 (01:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:08 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 14:25 (00:55)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 13:10 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 12:08 (02:15)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 10:55 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 08:20 (03:47)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 07:07 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 06:01 (02:18)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:47 (01:12)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 04:06 (01:53)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:53 (01:11)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 02:34 (01:30)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:20 (01:13)
reboot system boot 2.6.18-194.8.1.e Wed Aug 17 01:06 (01:27)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 15:42 (10:51)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:28 (01:13)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 14:30 (01:11)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 13:14 (01:14)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 10:28 (04:00)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 09:19 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 08:46 (01:42)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 07:36 (01:09)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:59 (03:45)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:48 (01:10)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 04:31 (00:28)
reboot system boot 2.6.18-194.8.1.e Tue Aug 16 03:17 (01:12)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 22:02 (06:27)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 20:52 (01:09)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 17:52 (04:08)
reboot system boot 2.6.18-194.8.1.e Mon Aug 15 16:40 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 18:44 (23:06)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 17:33 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 08:22 (10:21)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:12 (01:10)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 07:10 (01:11)
reboot system boot 2.6.18-194.8.1.e Sun Aug 14 05:57 (01:12)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 16:56 (14:13)
reboot system boot 2.6.18-194.8.1.e Sat Aug 13 15:41 (01:13)
reboot system boot 2.6.18-194.8.1.e Thu Aug 4 09:41 (9+07:14)
reboot system boot 2.6.18-194.8.1.e Mon Jul 25 21:29 (9+12:11)
reboot system boot 2.6.18-194.8.1.e Mon Jul 25 20:19 (01:09)
reboot system boot 2.6.18-194.8.1.e Sat Jul 23 04:22 (2+17:06)
reboot system boot 2.6.18-194.8.1.e Sat Jul 23 03:10 (01:11)
reboot system boot 2.6.18-194.8.1.e Thu Jul 14 01:17 (9+03:04)
reboot system boot 2.6.18-194.8.1.e Thu Jul 14 00:07 (01:10)
reboot system boot 2.6.18-194.8.1.e Wed Jul 13 18:27 (06:49)
reboot system boot 2.6.18-194.8.1.e Wed Jul 13 17:14 (01:13)
reboot system boot 2.6.18-194.8.1.e Sat Jul 9 17:08 (4+01:19)
reboot system boot 2.6.18-194.8.1.e Thu Jun 23 08:34 (16+08:33)
reboot system boot 2.6.18-194.8.1.e Thu Jun 23 07:12 (01:20)
reboot system boot 2.6.18-194.8.1.e Mon Jun 13 04:01 (10+04:31)
reboot system boot 2.6.18-194.8.1.e Mon Jun 13 02:50 (01:10)
reboot system boot 2.6.18-194.8.1.e Fri Jun 10 10:45 (2+17:15)
reboot system boot 2.6.18-194.8.1.e Fri Jun 10 09:33 (01:11)
reboot system boot 2.6.18-194.8.1.e Thu Jun 9 21:48 (12:56)
reboot system boot 2.6.18-194.8.1.e Thu Jun 9 20:28 (01:19)
reboot system boot 2.6.18-194.8.1.e Thu Jun 9 12:08 (09:38)
reboot system boot 2.6.18-194.8.1.e Thu Jun 9 10:48 (01:19)
reboot system boot 2.6.18-194.8.1.e Fri Jun 3 04:16 (6+07:50)
reboot system boot 2.6.18-194.8.1.e Fri Jun 3 03:05 (01:11)
reboot system boot 2.6.18-194.8.1.e Mon May 23 19:33 (10+08:43)
reboot system boot 2.6.18-194.8.1.e Mon May 23 18:17 (01:15)

Are we eligible for refund ?