Service Status

Resolved

dalstorage4 outage

5/30/2017 17:34 PM - Node dalstorage4 lost connectivity. Upon checking the serial console we found a kernel panic occured. 
5/30/2017 17:59 PM - All VPS are back onine.

Resolved

dalhighram17 degraded performance

We are aware of a performance degradation on dalhighram17. Our engineers are investigating the issue.

Resolved

lapure5 emergency reboot

05/03/2017 06:23 AM CST - We are going to reboot lapure5 to fix the high load average issue on it which was caused by a bug in KernelCare. We utilize KernelCare to do rebootless kernel upgrades but unfortunately a bug in the software is causing lock ups during the patching process. 
We will update this announcement once all VPS's are back online again.

05/03/2017 07:07 AM CST - All the VPS's are booted up now and we have confirmed the issue has been resolved.

Resolved

Dallas network connectivity (RFO Added)

04/26/2017 10:24 CST - We're aware of the network connectivity issue in Dallas and are working on the situation now. We'll update this announcement as we have more information.

04/26/2017 10:30 CST - We have pointed and resolved the issue. It will take around 5 mins before your VPS to come online if it's not already.

04/26/2017 10:54 CST - Everything should be back online now. A full Reason For Outage (RFO) report will be sent to ones who are affected shortly. We are sorry for the inconvenience.

Reason for Outage

This morning at around 10 AM CST we upgraded our Dallas core network switch and added an additional 10 Gbit capacity.

During the switchover to our new core switch, some VPS took longer than others to re-ARP into the VLAN. We had expected this to be transparent to all the customers based on the dry runs and tests we have processed during the previous weeks, but had a hard time getting the VLAN ARPed quickly enough.

Unfortunately, due to the slow re-ARP'ing, some of the IPs had around 5-25 minutes of downtime.

With this upgrade we now have full diverse path fibers configured to failover to avoid any interruptions due to physical factors.

We now also announce IPs under our own ASN, and can connect directly to other peering partners or carriers.

We can assure you that there won't be any more upgrades like these in the future as with this new setup, we have the ability to handle the new upgrades completely transparent.

We apologize for the inconvience that this unexpected network outage caused, however, we're committed to doing everything we can to ensure a consistent and reliable service at a great price.

If you have any questions or comments, please don't hesitate to inquire.

Resolved

Premium VPS line scheduled kernel upgrade

As scheduled, we are currently upgrading Linux Kernel's of the Premium VPS line host nodes.

Update: This has been done. Everything is back online.

Resolved

ukpure7 Maintenance

06 March 2017 14:40 PM - Due to an unexpected hardware issue with ukpure7 VPS node, we are going to perform emergency maintenance on it at 22:00 GMT today, around 1.25 hours from now.

Your VPS will be shut down at around 21:50 GMT to prepare the node for the maintenance. Your data and IP address will not change.

We expect the server to be back online in around 30 minutes after the maintenance begins.

We are sorry for the inconvenience caused by this but unfortunately we have to perform this to avoid further performance degradation of the node.

06 March 2017 16:00 PM - The VPS node is now powered off and we are awaiting for the datacenter techs to perform the maintenance.

06 March 2017 16:16 PM - The maintenance was completed with success. The server is now booting back up.

06 March 2017 16:22 PM - All the VPS's are now online. You may face slowness for a few minutes before the server catches its breath.

07 March 2017 01:40 AM - The server had a kernel panic. We are working on it.

07 March 2017 02:06 AM - We have brought the server back online. The VPS's are booting now. With the data we have, we are suspecting a bad memory module causing this. We will be monitoring the node.

07 March 2017 02:17 AM - All the VPS's are back online now. We have detected errors on some memory modules on the server. We are coordinating with the datacenter technicans to get them replaced to avoid further kernel panics.

07 March 2017 02:23 AM - We just had another kernel panic at the moment.

07 March 2017 02:58 AM - We are awaiting an update from the datacenter staff. We are not booting the server back again to avoid further kernel panic incidents.

07 March 2017 04:20 AM - The memory sticks have been replaced but we still see the same errors on the same DIMM slots. It looks like the motherboard is actually the faulty one here.

07 March 2017 04:56 AM - The datacenter has notified us that they are going to replace the server keeping its SSDs in. This wasn't something we wanted because of its risks but due to communication issues, they have gone ahead with it and we are waiting for an update from them now.

07 March 2017 05:15 AM - The datacenter has assured us that it'd be safe to do it and it'd be the best way to rule out any hardware issues. So we are at the capable hands of theirs and we are waiting for an update.

07 March 2017 05:56 AM - The datacenter has notified us that the server is booted but the network is not up, yet. We are working on getting the networking up at the moment.

07 March 2017 06:16 AM - We were able to get the networking working and booted the containers and then we have faced another kernel panic. Once we compare the memory module serials, it turned out that the datacenter staff has misunderstood our request and replaced the wrong memory modules 4 hours ago. We are finally waiting for them to take the server down once again and replace the correct memory modules now. The confusion occured because the datacenter staff didn't pay enough attention to the memory locations when we worded them starting from 0 and instead they thought the numbers we were mentioning were starting from 1. Even though there was a paranthesis mentioning this, it was unfortunately overlooked.

07 March 2017 06:51 AM - Finally the correct bad memory modules were swapped and we confirmed that we do not see any more error messages now. We are booting VPS's up at the moment. Please allow a few minutes for the slowness to pass.

07 March 2017 07:07 AM - All the VPS's confirmed online. We continue to monitor the server. A RFO will be emailed to all affected customers.

Resolved

All Premium VPS nodes rebooted

We had to upgrade the kernel of all Premium VPS nodes due to the CPU lockups we were getting with the old kernel. We are sorry for the inconvenience.

Resolved

dalstorage4 downtime

 02 March 2017 18:49 PM - We are aware that dalstorage4 is down at the moment. We are currently troubleshooting.

 02 March 2017 20:12 PM - We were able to boot the server and we are running fsck on the storage at the moment.

 02 March 2017 21:36 PM - fsck process has been completed succesfully. We are starting the VPS's on the node now.

 02 March 2017 22:01 PM - All the VPS's except a few have been booted. The others are calculating the quota at the moment.

Resolved

Amazon SES Issues

Due to issues with Amazon S3, our Amazon SES system which we use to send emails is not working at the moment. Please bare with us until this is resolved.

More information: https://status.aws.amazon.com/

Update 2:06 PM: We have switched to another SMTP provider for the time being.

UPdate 6:50 PM: We have switched back to Amazon SES.

Resolved

Dallas Network

26 January 2017, 11:55 - We are investigating the issue within our Dallas network. Please do not open a ticket as this would slow us down at the moment.

26 January 2017, 12:02 - The issue is related to our upstreams from what we understand so far.

26 January 2017, 12:19 - Connectivity has returned. We're awaiting confirmation of stability from the datacenter. 

Resolved

seapure5 maintenance

05 January 2017, 14:02 - The following maintenance is now in progress:

Hello,

You are receiving this message regarding work on our seapure5 server where you have active VPSDime service.

Tomorrow, Thursday January 5 2017, at 10 AM PST (UTC-8), we will be installing additional memory modules in this host node. We will begin shutting down the server approximately 20 minutes in advance to ensure a 10 AM start time with the technicians, so you can expect your VM to go down sometime between 9:40 and 10 AM PST (UTC-8). Please work to ensure your services are prepared to automatically start after a reboot action. Note that no customer data will be modified in any way by this operation.

We are specifying an hour of downtime total for this operation, although we expect it to be much less.

We apologize for the inconvenience, however we appreciate your understanding, and we are committed to providing you with the best service at a great price. Please don't hesitate to open a ticket if you have any questions or comments. Thank you.

-VPSDime Team

05 January 2017, 15:32 - This took longer than expected due to unforeseen problems, but is now complete and VMs are back online. 

Resolved

Rebooting seapure2

Due to soft lock up, we are rebooting seapure2. Your VPS should be online in the next 10 minutes.

Update 14:49: All the VPS's are back online and responsive.

Resolved

ukpure12 Emergency Maintenance

08 December 2016, 10:53 - The following notice was sent to affected clients:

Hello,

You are receiving this message regarding emergency work on our ukpure12 server where you have active VPSDime service.

This evening, Thursday December 8 2016, at 9 PM UK time, we will be replacing memory modules in this server that have begin alerting that they are failing. We are scheduling this for immediate replacement as the memory modules are no longer active in the memory pool, causing an increase in memory pressure on this particular server.

We will begin shutting down the server approximately 20 minutes in advance to ensure a 9 PM start time, so you can expect your VM to go down sometime between 8:40 and 9 PM UK time. Please work to ensure your services are prepared to automatically start after a reboot action. Note that no customer data will be modified in any way by this operation.

We are specifying an hour of downtime total for this operation, although we expect it to be much less.

We apologize for the inconvenience and the short notice on this, however the grievous situation mandates quick action. We appreciate your understanding, and we are committed to providing you with the best service at a great price. Please don't hesitate to open a ticket if you have any questions or comments. Thank you.

-VPSDime Team

08 December 2016, 14:42 - Server is going down now. 

08 December 2016, 15:37 - Maintenance is complete and the server is back online and booting customer VMs. Your VM will be online shortly if it's not already. 

Resolved

dalhighram4 outage

23 November 2016, 07:08 - we're investigating an outage of our dalhighram4 server now. 

23 November 2016, 07:19 - host node had a kernel panic. Server has been rebooted and is back online and booting containers now. 

23 November 2016, 07:40 - this has reoccurred, investigating further

23 November 2016, 08:09 - rebooted, all VMs except for two are back online. Yes, we know the node is in maintenance mode and currently locked. We'll be running it like this for awhile to ensure stability. 

23 November 2016, 08:27 - the cause has been identified and rectified. Server should be stable now. 

Resolved

UK outage

04 November 2016, 10:21 - We're investigating an outage of our UK services. We will provide more information on this announcement as we have it. 

04 November 2016, 10:27 - Network connectivity is back, awaiting confirmation from datacenter regarding stability and an RFO. 

04 November 2016, 10:58 - Datacenter has confirmed a short network outage lasting ~10 minutes, and have applied a fix to prevent a reoccurrence. 

Resolved

Offloaded MySQL Service Interruption

We are aware that PhpMyAdmin does not work on Offloaded MySQL service and are working on fixing it.

Your patience is greatly appreciated.

Resolved

seapure2 is rebooting

We are performing an emergency reboot on seapure2. VPS services will be going down for a few minutes.

Update 17:59 PM: Server has powered on.
Update 18:03 PM: Filesystem check is running.
Update 18:05 PM: VPS containers are starting to boot.
Update 18:10 PM: All VPS's are back online. You may encounter slowness for a few minutes.

Resolved

Offloaded MySQL outage

18:13 EST - We are aware of an outage affecting the offloaded MySQL service, we are taking a look at this now. Keep an eye on this announcement for updates.

21:58 EST - The service has now been restored and this issue is now resolved.

Resolved

Offlocated MySQL daldb2 outage

21 September 2016 | 7:54 PM - We have identified an issue with the offloaded MySQL server daldb2 in Dallas. 

21 September 2016 | 8:08 PM - The root cause of the outage has been identified and resolved. The MySQL service is restarting, this process will take a while due to the size of the database.

21 September 2016 | 20:14 PM - Server is back online now. Please open a ticket if you encounter any issues. 

Resolved

ukpure8 outage

 22 August 2016 | 08:08 AM - We are investigating an outage of our ukpure8 node at this time. We will update this announcement as we have more information.

 22 August 2016 | 08:25 AM - server is back online. Please let us know if you encounter any issues with it.