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% |
Network wide port blocks
Due to recent reflection exploits involving ports 111 (portmap/NFS), 161 (snmpd), and 389 (ldap), we've implemented a network-wide filter at our network edge to avoid your services running on these ports from being exploited and used to attack other computers on the internet.
We understand that this may be disruptive to your usage, and we can provide guidance on how to adjust these services to use different ports so that you may continue to enjoy uninterrupted connectivity.
These services are not installed on our VPS by default, so if you do not recognize any of the above services or ports, you're likely not affected by this action and this message is informational only.
New Jersey Maintenance
Thursday, 04 October 2018, 15:58 - We've just been briefed that our provider in New Jersey has scheduled a 30 minute maintenance window that may have service impacts for our clients on the nj1 node. See notice below:
Event Type: Network Upgrade
Start Time: 10/9/2018 12AM EST
End Time: 10/9/2018 12:30AM EST
Location(s): Piscataway, NJ
Device(s): c8-10-b4-1.pnj1
Client Affecting: Yes
Event Summary: Important maintenance will be performed on one or more devices that may affect network connectivity to your services.
Intermittent connectivity affecting all Dallas nodes
Thursday, 27 September 2018, 18:24 - We're aware of the issue, and are attempting to follow up with our connectivity provider. Further updates will be posted to this issue as we receive them.
Thursday, 27 September 2018, 18:33 - Our provider has confirmed that this was a misconfigured network-wide-filter applied on our upstream port(s). The rogue change has now been rolled back, services are back online.
We apologize for any inconvenience caused.
NJ Maintenance
ukhighram3 offline
dalstorage4 disk array rebuild
Dallas connectivity
nj1 downtime
Connectivity Problem in Dallas
nj1 connectivity
FW intermittent network issues
Kernel panic on dalhighram10
Dallas network errors
nj1 network connectivity
dalstorage1 unreachable
dalhighram25 unreachable
Dallas network problems
Tuesday, 06 February 2018 11:34 - We're receiving reports of an unexpected partial routing failure somewhere, or similar network issue. Please don't stop/start/reboot your VPS, it won't fix the issue. When opening a ticket to inform us that your VPS is offline, could you please send a TEXT traceroute between yourself and your service with us? This will assist us with resolving the issue.
Tuesday, 06 February 2018 11:59 - The issue should have been rectified now. We'll update the announcement with a RFO.
Friday, 02 March 2018, 10:46 - Formal RFO is available at the following link: https://d.pr/f/RN2AjO
ukhighram2 issues
Storage VPS Line Meltdown and Spectre Maintenance
Reboot for Meltdown / Spectre patching
Today, Saturday January 6th, 2018, we will be rebooting host nodes serving all VPSDime Linux VPS to execute a new kernel patched against the recently discovered Meltdown and Spectre exploits.
No doubt that in recent days you have noted news that two vulnerabilites have been discovered in all CPUs, ranging back to the development of speculative execution on modern processors over 20 years ago. Although both attacks are based on the same general principle, Meltdown allows malicious programs to gain access to higher-privileged parts of a computer's memory, while Spectre steals data from the memory of other applications running on a machine. Nearly every modern computer in use is vulnerable at some level.
Our virtualization vendor for the Linux VPS product has recently produced a patch to mitigate these two issues, and this patch has been generally accepted by the computing community at large as being an effective method to ensure that the exploit is ineffective. At this time there is no evidence that the exploit has been applied to gain access to other systems, either on our host nodes or elsewhere.
Due to the grievous nature of these attacks, we are updating all host nodes and rebooting them immediately to execute the new kernel. Note that all vendors of kernel live patching are either taking a very long time to implement a live patch (CloudLinux's Kernelcare) or have directly stated that a live patch won't be available (Canonical's Livepatch). Therefore, a reboot of the host node is mandatory in this situation.
We apologize for the inconveience that you will experience due to this, however, please note that we are committed to the utmost stability and security of your virtual machines.
There are some key points to note:
- We'll use this page to make further announcements regarding this reboot action. So please follow up with this page for the updates.
- All VPS will be gracefully shut down, similar to how the "shutdown -h now" or "halt" command works inside your VPS' operating system.
- This update and reboot action will make absolutely no changes to your VPS whatsoever. No changes will be made to your configuration, software, applications, data, or anything else regarding your VPS directly. All VPS will be checked that they are running after the reboot, however, if an application or software you've installed is not responding, please log in to your VPS and troubleshoot your software and make sure your services are running before opening a ticket.
- Barring any unexpected issues, we expect no more than 30 minutes per host node to reboot. This is the time for VPS to shut down and host node to complete a reboot; your VPS may take a bit longer to boot after the host node comes back online. Your patience is appreciated.
Please note that we are unable to provide a certain time frame for your VPS to be shut down because we are going to apply the security patch on one host node at a time. Again, we apologize for the inconvenience of a reboot.
If you have any questions or concerns regarding this, please click here and open a ticket with us.
============
We're working through the reboots now.
If you view your service and see "This node is locked", the node has not yet been rebooted.
If you view your service and see the usual start/stop/reboot buttons and traffic/memory/load graphs, the reboot action has been completed for that node and any services on that node will remain online.
============
All the nodes in Dallas, TX but 2 have been rebooted on Saturday January 6th, 2018.
============
Sunday January 7th, 2018:
We are continuing to reboot the nodes in our other locations today.