As you guys have noticed today server is again down, this time same reason of nullrouting the ip, but this time burst.net acted in an unprofessional manner not notifying us or our provider volumedrive that they had done that, resulting in almost entire day now of downtime. We are working to get this issue resolved, and hoping to move to new location within a week’s time, either will stick with current provider (they are opening new facility in NY) or just get a new provider itself, so we do not have to worry about Burst.net and its unprofessionalism.

Sorry for the issue, but sorries don’t really cut it all the time, if only i had any control over how Burst.net should be run this would not be happening at all. Still awaiting reasons as to why null routing took place in the first place.

Change is inevitable ! Unless they can reimburse us or can provide a professional explanation !!

Sorry for the downtime, but we are not sure what happened, was it the not so expert in server management, company that we got services from or if it was our new provider itself.

We are waiting for the datacenter to reboot the server. When its back online we cannot say at this time, hopefully the datacenter will reboot it quickly, cause right now we are at their mercy to reboot the server.

Sorry once again.