The following location has been upgraded and rebooted:
Core
IAD01 - Ashburn, VA, United States
One hypervisor in San Jose has experienced a hardware failure. We are migrating the affected virtual machines to other operational hosts.
Maintenance in Hong Kong is scheduled to continue tonight, October 17, local time (HKT, UTC+8).
We have also observed an issue affecting some virtual machines running Ubuntu 24.04, where CPU usage reaches 100% and the VM becomes unresponsive. We are manually restarting affected VMs one at a time. Users can also power off their VM through the control panel and then power it back on.
In progress
The following location has been upgraded and rebooted:
Core
IAD01 - Ashburn, VA, United States
One hypervisor in San Jose has experienced a hardware failure. We are migrating the affected virtual machines to other operational hosts.
Maintenance in Hong Kong is scheduled to continue tonight, October 17, local time (HKT, UTC+8).
We have also observed an issue affecting some virtual machines running Ubuntu 24.04, where CPU usage reaches 100% and the VM becomes unresponsive. We are manually restarting affected VMs one at a time. Users can also power off their VM through the control panel and then power it back on.
In progress
The following location has been upgraded and rebooted:
Core
NRT04 - Tokyo, Japan
Maintenance in Ashburn, San Jose, and Hong Kong is taking longer than initially expected due to additional work required at these locations. Downtime for each individual physical host is expected to be approximately 30 minutes at most.
Maintenance at all other locations is complete, and services have been restored. If your VM or service is not running, please try restarting it through the control panel. If the issue persists, please submit a support ticket.
Thank you for your patience and understanding.
In progress
The following locations have been upgraded and rebooted:
Core
BER03 - Berlin, Germany
SIN03 - Singapore
Edge
FRA13 - Frankfurt, Germany
In progress
The following locations have been upgraded and rebooted:
Core
EWR02 - Secaucus, NJ, United States
LAX02 - Los Angeles, CA, United States
MIA01 - Miami, FL, United States
In progress
The following locations have been upgraded and rebooted:
Core
AMS02 - Amsterdam, Netherlands
MCI01 - Kansas City, MO, United States
Edge
LOS01 - Lagos, Nigeria
LIS01 - Lisbon, Portugal
OSL02 - Oslo, Norway
WAW03 - Warsaw, Poland
In progress
The following locations have been upgraded and rebooted:
Edge
ZAG01 - Zagreb, Croatia
CPH02 - Copenhagen, Denmark
MIL02 - Milan, Italy
In progress
The following locations have been upgraded and rebooted:
Core
JNB01 - Johannesburg, South Africa
Edge
DUB02 - Dublin, Ireland
LED02 - St. Petersburg, Russia
PRG02 - Prague, Czech Republic
We are investigating a possible firmware issue at MIA01 - Miami, FL, United States, and are working to resolve it.
In progress
The following locations have been upgraded and rebooted:
Core
LON05 - London, United Kingdom
Edge
BRU02 - Brussels, Belgium
IST01 - Istanbul, Turkey
YUL04 - Montréal, QC, Canada
ZRH01 - Zürich, Switzerland
In progress
The following locations have been upgraded and rebooted:
Core
SEA02 - Seattle, WA, United States
In progress
Completed maintenance locations are now marked as operational. Maintenance remains in progress at the remaining locations.
In progress
The following locations have been upgraded and rebooted:
Edge
MAD02 - Madrid, Spain
MRS01 - Marseille, France
OTP01 - Bucharest, Romania
SOF01 - Sofia, Bulgaria
STO02 - Stockholm, Sweden
VIE01 - Vienna, Austria
In progress
The following locations have been upgraded and rebooted:
Core
MOW01 - Moscow, Russia
TPE01 - Taipei
FRA02 - Frankfurt am Main, Germany
Edge
ATH01 - Athens, Greece
KBP01 - Kyiv, Ukraine
KHV01 - Khabarovsk, Russia
BOD01 - Bordeaux, France
SAO03 - São Paulo, Brazil
Scheduled
We have identified a critical security issue affecting our hypervisors. We will perform emergency maintenance and reboot host nodes across all locations to address it.
Start time: October 17, 2026 at 00:00 UTC
End time: October 18, 2026 at 00:00 UTC
Impact duration: 24 hours
During this window, virtual machines will be shut down and unavailable while their host nodes are being serviced. Once maintenance on each host is complete, we will return its VMs to their pre-maintenance power state.
VMs running a custom operating system or boot configuration may require manual intervention to start successfully. If your VM does not boot after maintenance, use the Start action in the control panel. If the issue persists, please submit a support ticket.
We apologize for the disruption and appreciate your patience and understanding.