Service Status Icon

Service Status

Check our service status and past incidents

Overall Service Status

100%

Up

All services are operating normally at this time.

Last Incident


Status: Resolved - Posted at: 25th July 2025 - 12:18

All Regions

Data Center Current Last Day Last Month Last Year
Dallas DC Icon
Dallas, TX
Up 100% 100% 100%
Seattle DC Icon
Seattle, WA
Up 100% 100% 100%
New Jersey DC Icon
Piscataway, NJ
Up 100% 100% 100%
Los Angeles DC Icon
Los Angeles, CA
Up 100% 100% 100%
London Datacenter Icon
London, UK
Up 100% 100% 100%
Maidenhead Datacenter Icon
Maidenhead, UK
Up 100% 100% 100%
Netherlands Datacenter Icon
The Netherlands
Up 100% 100% 100%

Past Incidents

Resolved

Outage in Dallas

Posted at: 28th September 2015 - 22:07

Our datacenter is reporting an issue with one of their switches: https://twitter.com/InceroStatus/status/648695085387747328?lang=en

This has killed connectivity to the nodeXssd and dalyearly servers, along with daldb. This announcement will be updated as we know more.

=====

 

This is now resolved, and all services should now be back online: https://twitter.com/InceroStatus/status/648706618335473664

Resolved

Downage in Dallas. We are working on the situation.

Posted at: 15th July 2015 - 05:37

Several nodes in Dallas are currently down. Our technicians are working to bring them back as soon as possible.
Resolved

ukpure2 reboot

Posted at: 3rd July 2015 - 11:14

ukpure 2 requires an emergency reboot and will be going down.

Update: server rebooted and appears to be back online
Resolved

seapure1 is unresponsive

Posted at: 21st June 2015 - 10:23

seapure1 is currently unresponsive and we are working on it.

Update: This is resolved. However, some of the VPS's got auto suspended due to extreme load on the server. These are now unsuspended.
Resolved

seapure1 is rebooted

Posted at: 16th May 2015 - 04:34

Due to a kernel panic, we have rebooted seapure1 and your VPS should come back online in the following minutes.
Resolved

ukpure1 is rebooted

Posted at: 15th May 2015 - 17:12

Due to a lock up, we have rebooted ukpure1 node. Your VPS should come back online in the following minutes.
Resolved

Network issues with LA servers

Posted at: 9th April 2015 - 23:23

Our upstream in LA is currently encountering some network issues. We are looking into it.
Resolved

dalpure3 reboot

Posted at: 8th April 2015 - 06:56

We are emergency rebooting dalpure3. It should come back in 10 minutes.

Update: All VPS's are back online.
Resolved

Major LA Packetloss

Posted at: 5th April 2015 - 12:46

Investigating High Packetloss in our LA location. At this time it appears to be DC wide.

This appears to be resolved now
Resolved

node3 outage

Posted at: 29th March 2015 - 01:01

We're currently investigating an outage of our node3 server in LA.

Update: This is resolved.
Resolved

dalwest2 high packetloss

Posted at: 22nd March 2015 - 17:35

We are investigating high packetloss on node dalwest2.

Packetloss should be resolved. Cause was incoming DDOS
Resolved

vlan outage in Dallas

Posted at: 11th February 2015 - 20:38

2015-02-11 2039 CST: We are acknowleding a vlan outage in Dallas at the moment. We're engaging the datacenter to look into the issue. If your server is "down" and this announcement does not say [SOLVED], yes, your server is on this vlan.

2015-02-11 2055 CST: From the datacenter, this encompasses more than just us. Their twitter feed: https://twitter.com/InceroStatus

2
015-02-11 2102 CST: Datacenter fixed issue, network back online. 
Resolved

rebooting dalpure7

Posted at: 16th January 2015 - 20:42

We are rebooting dalpure7 at the moment. Your VPS should come back online in 10 minutes.

We are frequently having lock ups on this node and we are planning to migrate VPS's to a new node soon.

Update: All VPS's are back online.
Resolved

dalstorage3 kernel panic

Posted at: 14th January 2015 - 01:20

We have faced yet another kernel panic on dalstorage3. The server is rebooting.

We are going to send a replacement for this server and migrate the data.

Update: The server is offline. We are working on a solution.

Update: The server was keep rebooting itself. We are thinking that this was due to half applied patches by Kernel care. The last kernel has been reinstalled to avoid this issue. We are hoping this would resolve the problems on this node.

Update: Unfortunately, this looks like an hardware issue. We are going to have to replace the mainboard and the memory of this server, since it can't stay online.

Update: We're still working through the situation. We're working to boot the system so that we can disable the VM filesystem, and then remove one of the hardware components that seems to be causing issues.

Update: We have replaced the motherboard, CPUs and the memory on the server. After doing fsck 3 times which took around 20 hours alone, the server has booted and is currently booting the VPS's.

Resolved

Network Issue affecting Dallas

Posted at: 13th January 2015 - 21:16

We are facing a network issue that's affecting dalstorage2 dalstorage3 dalstorage4 dalpure7 and dalpure8.

This will be fixed in a few minutes.

Update: 21:18: We are back up.
Resolved

dalstorage3 is offline

Posted at: 11th January 2015 - 03:26

dalstorage3 is offline and we are working on it.

Update: The server has kernel paniced. We have rebooted it and it's currently running fsck.

Update: The serer has booted, it's booting VPS's. Your VPS should come online in the following 20 minutes of this post (3:56 AM CST)
Resolved

dalstorage3 is rebooted, back online

Posted at: 9th January 2015 - 15:44

15:44 :investigating.
Node appears to have kernel panicked

 

15:48: node back online, VMs are booting

Resolved

dalstorage4 failure, replacement

Posted at: 8th January 2015 - 08:09

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

===

Resolved

Planned storage VPS server move in progress

Posted at: 7th January 2015 - 10:33

Further to the email we sent out regarding the server move for dalstorage2 and dalstorage3, this is currently ongoing. We'll update this announcement when complete.

Update: dalstorage3 is shut down and is being physically moved at the moment.

Update: dalstorage2 is also shut down and is being physically moved.

Update: Both servers are moved. VPS's are booting on dalstorage2. dalstorage3 has all VPS's booted.

Update: All VPS's are online.
Resolved

dalpure6 is down

Posted at: 6th January 2015 - 07:39

We are aware that dalpure6 is down. We are working on it.

Update: It was a kernel panic. We have rebooted the server and your VPS should come back online soon.

Update: Now, the node is having a network issue. We are working on it.

Update: This issue is resolved. It was caused by multiple 10G DDoS attacks to multiple IPs that our filtering couldn't handle.

Contact Technical Support: