Las Vegas went black a couple of minutes ago.
this is being worked on.
more updates will follow.
This will be marked as resolved as the location will be closed.
Customers have been emailed about the options available.
[2020-08-13] Currently experiencing issues with ipv6 from the containers. It's working from the host node but if you try and reach something on the outside, you will get "Destination unreachable: Address unreachable". Working on the issue. [2020-08-13 23:48 CET] - Rebooting France Node3 after applying some changes. [2020-08-16] After ... Read More »
Due to the issues mentioned in the previous announcement, the node will be shut down and then restarted to make sure the RAID is rebuilt properly.
Sorry for the inconvenience, it has to be done to make sure the service is stable and the RAID can rebuild properly.
West Virginia node is currently offline. investigating. [UPDATE 2020-08-06 15:50 CET] Still, no reply from the Datacenter, limited access has been required and it looks like there is a network issue at the moment. Trying to get a reply from the DC, will report status as soon as I know more. [UPDATE 2020-08-06 21:39 CET] server is ... Read More »
With the latest update from Virtuozzo and the way Virtualizor has implemented the template system, there is a problem reinstalling containers at the moment. The reinstall fails without much information to the end-user, the underlying issue is in part the update from Python2 to Python3 and some template files are empty or missing. I’m ... Read More »
The node is rebooting as this announcement is written. Service should be restored shortly. [UPDATE] reboot is done, outgoing ipv4 is currently not working. Troubleshooting is ongoing. As this is primarily an ipv6 service, use that in the mean time. [UPDATE] Got noticed at 19:21 CET today (2020-07-27) that outgoing ipv4 connections from ... Read More »
Due to a memory lock, a reboot of the Singapore Node is needed.
Services will be restored shortly.
The DC are having connectivity issues. Should be back online shortly.
A physical move of the BG node is prepared as this is written.
The expected downtime is approx. 4 hours.
this Announcement will be updated when the node is back online.
the node is back online and a health check has been performed.
if you have any issues, open a ticket.
fsck is running on the old node.
Will be back online soon