All services are operating normally at this time.
Data Center | Current | Last Day | Last Month | Last Year |
---|---|---|---|---|
Dallas, TX | Up | 100% | 100% | 100% |
Seattle, WA | Up | 100% | 100% | 100% |
Piscataway, NJ | Up | 100% | 100% | 100% |
Los Angeles, CA | Up | 100% | 100% | 100% |
London, UK | Up | 100% | 100% | 100% |
Maidenhead, UK | Up | 100% | 100% | 100% |
The Netherlands | Up | 100% | 100% | 100% |
dalstorage3 is rebooted, back online
15:44 :investigating.
Node appears to have kernel panicked
15:48: node back online, VMs are booting
dalstorage4 failure, replacement
08:09: Our dalstorage4 storage server is being rebooted for a filesystem check. This announcement will be updated when complete.
08:55: This didn't go quite as planned. We are working the situation and will provide more information when we can.
09:17: All clients on this server have been emailled the following:
===
Hello,
We are writing to you because you have active service on our "dalstorage4" server.
The reason for the message is to inform you of a disk controller or disk error with this server. This morning, the file system began throwing egregious errors. In an effort to salvage the situation, we rebooted the server to run fsck on the VM partition, only to discover that the disk array is no longer readable, and that fsck is throwing an error that every block is unreadable. Unfortunately, at this juncture it appears that your data is lost.
At this point, we've shipped a replacement server, which will be online tomorrow afternoon, relative to the United States.
We're offering two options:
1. We can recreate your VM tomorrow on the new server, and provide you with a full two months of credit for the issue.
2. We can provide a full refund back to your payment method.
Please note that we're unable to recover your data, and please do not open tickets regarding that. This has been a hard decision that we did not take lightly, and every effort has already been made to fully recover your data.
Please open a ticket with your choice, and if you have any other questions, please don't hesitate to task.
Thank you for your understanding,
-VPSDime Team
===
Planned storage VPS server move in progress
dalpure6 is down
node3 is being rebooted
dalpure1 is under DDoS attack
dalstorage3 downtime
node3 is rebooted
dalstorage2 is rebooting
lapure2 is having hardware issues
The issue started with a major packet loss on this node. We couldn't even get into the shell to check.
First, we have suspected a DDoS attack and alerted our datacenter. They told us that there was no attack.
Then we've gotten them to replace our cables as well as their cables to the top of the rack switch. This has not solved the problem.
Then we've gotten them to swap the network cable to the other ethernet port. Unfortunately, this has not solved the problem, either.
After eliminating the hardware issues, we have started to troubleshoot the issue (very slowly, due to the high load caused by the attack!) on the IPMI console further. And then we have realized that there was indeed an attack on one of the IPs which our DC failed to recognize.
We have nullrouted the target IP manually and the packet loss issue is gone.
Your VPS is currently up and running.
We are terribly sorry for the downtime this has caused you and we want to make it up to you. Please open a ticket to redeem $5 credit on your account for the trouble.
node1ssd kernel panic
Rebooting nj1
Rebooting Colocrossing Los Angeles Server
dalstorage3 Problem
Network problem in Los Angeles
Dallas issues
UK Maintenance
New Jersey Network Issues
node3 Los Angeles Network Issues
node3ssd ddos