Hyonix - Notice history

Operational

Hyonix Panel - Operational

Hyonix Backend - Operational

Hyonix API - Operational

Operational

Los Angeles, California (LAX1) - Operational

Dallas, Texas (DAL1) - Operational

Ashburn, Virginia (IAD2) - Operational

New York, New York (NYC2) - Operational

Miami, Florida (MIA1) - Operational

London, United Kingdom (LON1) - Operational

Amsterdam, Netherlands (AMS2) - Operational

Hong Kong, Hong Kong (HKG1) - Operational

Tokyo, Japan (TYO1) - Operational

Sydney, Australia (SYD1) - Operational

Frankfurt, Germany (FRA10) - Operational

Toronto, Canada (TOR10) - Operational

Chicago, Illinois (CHI1) - Operational

Singapore, Singapore (SIN1) - Operational

Las Vegas, Nevada (LAS10) - Operational

Bend, Oregon (PDX10) - Operational

Salt Lake City, Utah (SLC10) - Operational

Detroit, Michigan (DET1) - Operational

Pittsburgh, Pennsylvania (PIT10) - Operational

Seattle, Washington (SEA10) - Operational

Charlotte, North Carolina (CLT10) - Operational

Phoenix, Arizona (PHX10) - Operational

Dublin, Ireland (DUB10) - Operational

Operational

Los Angeles, California (LAX1) - Operational

Dallas, Texas (DAL1) - Operational

Ashburn, Virginia (IAD2) - Operational

New York, New York (NYC1) - Operational

New York, New York (NYC2) - Operational

Miami, Florida (MIA1) - Operational

London, United Kingdom (LON1) - Operational

London, United Kingdom (LON-THN) - Operational

Slough, United Kingdom (LON5) - Operational

Amsterdam, Netherlands (AMS2) - Operational

Amsterdam, Netherlands (AMS-NIKHEF) - Operational

Hong Kong, Hong Kong (HKG1) - Operational

Tokyo, Japan (TYO1) - Operational

Sydney, Australia (SYD1) - Operational

Frankfurt, Germany (FRA10) - Operational

Toronto, Canada (TOR10) - Operational

Chicago, Illinois (CHI1) - Operational

Singapore, Singapore (SIN1) - Operational

Notice history

View current status

Nov 2026

Emergency Security Maintenance – Windows Hypervisor Host Nodes
ResolvedMajor outage32 hours 43 minutes
  • ResolvedUTC

    All host nodes have been patched, and our final checks are complete.

    What happened
    On 10 November, Microsoft released security updates fixing more than 1,000 vulnerabilities across its products, including eight Critical vulnerabilities in Windows Hyper-V, the virtualization platform our host nodes run on:

    Potential impact
    Several of these vulnerabilities could allow an attacker inside one virtual server to break out and gain access to the host node. From there, an attacker could potentially:

    • Access, steal or change data on any server on that host node

    • Delete servers and their data entirely

    • Shut down or disrupt every server on that host node

    • Install malicious software on the host node

    What we did
    Our customers trust us with their servers and data, and keeping them secure is a responsibility we take seriously. That’s why we applied Microsoft’s November 2026 security updates to all host nodes as soon as possible, closing these vulnerabilities. All host nodes are now protected.

    We’ll shortly be sending customers an email with more details about these vulnerabilities and why we carried out this maintenance immediately.

    We’re also reviewing our notification process following the email delivery issue during this maintenance, to make sure this doesn’t happen again.

    We still strongly recommend installing the latest Windows updates on your own server, as this month’s updates also fix Critical vulnerabilities in Windows components that may run on it.

    Thank you for your patience and understanding. If you notice any issues with your server, please open a support ticket.

  • MonitoringUTC

    Patching is now complete in all locations. Our team is running final checks and wrapping up the maintenance.

    If your server is still unreachable or you notice any issues, please try the troubleshooting steps in our previous update first: check that your server is running, and check whether it’s stuck on the Windows Recovery screen. If the problem continues, please open a support ticket and we’ll help as soon as we can.

    We’ll share more details about the vulnerabilities and this maintenance once our final checks are complete.

    Thank you for your patience and understanding throughout this maintenance. We know it has been disruptive, and we truly appreciate your support.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • New York, New York (NYC2): In Progress

    Europe

    • Frankfurt, Germany (FRA10): Completed

    Expected completion: By 1:00 PM GMT+8 (05:00 UTC).

    We’ll keep updating this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    We’re receiving a much higher number of support tickets than usual, so responses may take longer than normal. Many common questions are answered in our earlier “Answers to common questions” update on this page. We’ll reply to every ticket as soon as we can, and we appreciate your patience.

    If your server is in a completed location but is still unreachable, please try the following steps before opening a ticket:

    1. Check that your server is running

    • A very small number of servers did not start automatically after maintenance.

    • Go to your server dashboard and check your server’s status. If it’s stopped, start it, and you can use it as normal.

    • Guide: How to start or stop your Windows VPS

    2. Check whether your server is stuck on the Windows Recovery screen

    • If your server couldn’t be shut down cleanly (for example, because a running process blocked the shutdown), it was powered off, and Windows may open the Recovery screen on the next start.

    • Go to your server dashboard and open the console. If you see the Windows Recovery screen, click Continue to start Windows normally.

    • Guide: How to access the server console

    If your server is still unreachable after these steps, please open a support ticket and we’ll help as soon as we can.

  • IdentifiedUTC

    We’ve resumed patching in New York and Frankfurt. Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • New York, New York (NYC2): In Progress

    Europe

    • London, United Kingdom (LON1): Completed

    • Frankfurt, Germany (FRA10): In Progress

    Expected completion: By 1:00 PM GMT+8 (05:00 UTC).

    We’ll keep updating this list as each location progresses. If you have any questions, please open a support ticket.

  • MonitoringUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Ashburn, Virginia (IAD2): Completed, except for one host node (see note below)

    • New York, New York (NYC2): On Hold

    Europe

    • London, United Kingdom (LON1): In Progress

    • Frankfurt, Germany (FRA10): On Hold

    Note on Ashburn: One host node in this location has a hardware failure, and we’re waiting for a datacenter technician to resolve it. Customers with servers on this node will be notified separately.

    Patching in New York and Frankfurt is currently paused and is expected to resume by around 08:30 (GMT+8). We’ll post another update when patching resumes in these locations.

    We’ll keep updating this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Ashburn, Virginia (IAD2): In Progress

    • New York, New York (NYC2): On Hold

    Europe

    • London, United Kingdom (LON1): In Progress

    • Amsterdam, Netherlands (AMS2): Completed

    • Frankfurt, Germany (FRA10): In Progress

    We’ll update this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Ashburn, Virginia (IAD2): In Progress

    • New York, New York (NYC2): On Hold

    • Miami, Florida (MIA1): Completed

    • Chicago, Illinois (CHI1): Completed

    Europe

    • London, United Kingdom (LON1): On Hold

    • Amsterdam, Netherlands (AMS2): In Progress

    • Frankfurt, Germany (FRA10): In Progress

    We’ll update this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Dallas, Texas (DAL1): Completed

    • Ashburn, Virginia (IAD2): In Progress

    • New York, New York (NYC2): On Hold

    • Miami, Florida (MIA1): In Progress

    • Chicago, Illinois (CHI1): In Progress

    Europe

    • London, United Kingdom (LON1): On Hold

    • Amsterdam, Netherlands (AMS2): In Progress

    • Frankfurt, Germany (FRA10): In Progress

    We’ll update this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Los Angeles, California (LAX1):Completed

    • Dallas, Texas (DAL1): In Progress

    • Ashburn, Virginia (IAD2): In Progress

    • New York, New York (NYC2): On Hold

    • Miami, Florida (MIA1): In Progress

    • Chicago, Illinois (CHI1): On Hold

    • Bend, Oregon (PDX10): Completed

    Europe

    • London, United Kingdom (LON1): On Hold

    • Amsterdam, Netherlands (AMS2): In Progress

    • Frankfurt, Germany (FRA10): In Progress

    Asia Pacific

    • Hong Kong (HKG1): Completed

    • Sydney, Australia (SYD1):Completed

    We’ll update this list as each location progresses. If you have any questions, please open a support ticket.

  • UpdateUTC

    Locations completed in earlier updates have been removed from this list. Servers in those locations are back to normal operation.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Los Angeles, California (LAX1): In Progress

    • Dallas, Texas (DAL1): In Progress

    • Ashburn, Virginia (IAD2): On Hold

    • New York, New York (NYC2): On Hold

    • Miami, Florida (MIA1): In Progress

    • Chicago, Illinois (CHI1): On Hold

    • Bend, Oregon (PDX10): In Progress

    Europe

    • London, United Kingdom (LON1): On Hold

    • Amsterdam, Netherlands (AMS2): On Hold

    • Frankfurt, Germany (FRA10): On Hold

    Asia Pacific

    • Hong Kong (HKG1): In Progress

    • Tokyo, Japan (TYO1): Completed

    • Singapore (SIN1): Completed

    • Sydney, Australia (SYD1): In Progress

    We’ll update this list as each location progresses. If you have any questions, please open a support ticket.

  • IdentifiedUTC

    Patching has resumed. We’re now posting progress by location so you can follow the location your server is in.

    Status key:

    • Completed: All host nodes in this location have been patched.

    • In Progress: Patching is under way in this location.

    • On Hold: Patching is currently paused in this location.

    North America

    • Los Angeles, California (LAX1): In Progress

    • Dallas, Texas (DAL1): In Progress

    • Ashburn, Virginia (IAD2): On Hold

    • New York, New York (NYC2): On Hold

    • Miami, Florida (MIA1): On Hold

    • Toronto, Canada (TOR10):Completed

    • Chicago, Illinois (CHI1): On Hold

    • Las Vegas, Nevada (LAS10): Completed

    • Bend, Oregon (PDX10): In Progress

    • Salt Lake City, Utah (SLC10): Completed

    • Detroit, Michigan (DET1): Completed

    • Pittsburgh, Pennsylvania (PIT10): Completed

    • Seattle, Washington (SEA10): Completed

    • Charlotte, North Carolina (CLT10): Completed

    • Phoenix, Arizona (PHX10): Completed

    Europe

    • London, United Kingdom (LON1): On Hold

    • Amsterdam, Netherlands (AMS2): On Hold

    • Frankfurt, Germany (FRA10): On Hold

    • Dublin, Ireland (DUB10): Completed

    Asia Pacific

    • Hong Kong (HKG1): In Progress

    • Tokyo, Japan (TYO1): In Progress

    • Singapore (SIN1): In Progress

    • Sydney, Australia (SYD1): In Progress

    We’ll update this list as each location progresses

  • UpdateUTC

    We’ve received many questions about this maintenance. Here are answers to the most common ones.

    1. Can you schedule a time for my server, or notify me before it goes down?

    • Unfortunately, no. Scheduling each server individually or sending a notice before each restart would slow down the maintenance considerably.

    • Our priority is to patch all host nodes as quickly as possible to reduce the security risk for every customer.

    2. How can I track progress for my server?

    • We’ll post progress by location instead of as an overall percentage, so you can follow the location your server is in.

    3. How do I know if my server has been patched?

    • A quick way to check is your server’s uptime. If the uptime was reset during the maintenance and your server has now been running for more than 2.5 hours, its host node has most likely been patched.

    • For a definite answer, please check the progress update for your server’s location on this page.

    • Our support team can also confirm this for you once they’ve received updates from our infrastructure team. Please expect slower responses because of the high number of tickets right now.

    4. When will the maintenance be finished?

    • We can’t give a completion time yet as several factors are involved, including the unexpected issues we’ve run into so far.

    • We’re doing everything we can to complete the maintenance as quickly as possible.

    5. Is there anything I should do in the meantime?

    • Your server may restart without further notice, so please save your work regularly or wait until the maintenance is complete to resume working.

    • If you run time-sensitive or real-time activities on your server, we strongly recommend pausing them until the maintenance is complete. This will help prevent losses if your server is interrupted.

    6. Will you share more details about the vulnerabilities?

    • Yes. We’ll publish more detailed information about the vulnerabilities once the maintenance is complete.

    We sincerely apologize for the disruption. We understand how important it is for your server to run without interruption, and we only carry out maintenance like this as a last resort, when it’s necessary to protect your servers and data.

    If you have any other questions, please open a support ticket.

  • MonitoringUTC

    Progress has been slower than expected because of unexpected issues with a few host nodes. Our team is working to fix these and bring the affected servers back online as soon as possible.

    We’d like to stress that this is not routine maintenance. Until each host node is patched, these vulnerabilities could put the security of customer servers and data at risk. We would not carry out disruptive maintenance on such short notice unless it was necessary to protect our customers.

    We have also temporarily paused patching on the remaining host nodes until all notification emails have been delivered, so every customer has a chance to prepare before their server is restarted. Servers on host nodes that haven’t been patched yet are not affected while patching is paused.

    Progress: About 40% of host nodes have been patched.
    Patching expected to resume: Around 19:45 (GMT+8)

    We’ll post another update when patching resumes. We apologize for the extended disruption. If you have any questions, please open a support ticket.

  • UpdateUTC

    We’ve just learned that our notification emails about this maintenance were not delivered because of an error with our email service provider. Our team is now resending them with an alternative method to make sure all customers are informed.

    We apologize to anyone who was affected by the maintenance without receiving notice. This status page remains the most up-to-date source of information, and we’ll keep posting updates here as patching continues.

    If you have any questions, please open a support ticket.

  • UpdateUTC

    As we continue patching, a few host nodes did not install the patch successfully on the first attempt and need to be patched again. We’ve updated the expected maintenance time to reflect this.

    Progress: About 35% of host nodes have been patched.
    Updated expected impact: Up to 2.5 hours per server. Most servers are back online within about 1 hour, but servers on the affected host nodes may take longer.

    Your server will start again automatically once its host node has been patched. We’ll keep this page updated as patching continues.

    We apologize for the extended disruption. If you have any questions, please open a support ticket.

  • UpdateUTC

    After extensive testing of the security patches on our host nodes, we’ve found that customer servers will need to be restarted. In past Windows updates, we’ve always been able to save each server’s state and restore it afterwards, and we expected the same this time. However, after this patch is applied, servers can no longer be restored from a saved state.

    We will begin applying the patches to our live host nodes immediately. To protect your data, we will attempt a clean shutdown of each customer server, where possible, before patching its host node. Your server will start again automatically once patching is complete.

    What this means for you:

    • Any unsaved work on your server will be lost. Please save your work and close important applications before maintenance.

    • Applications and services that aren’t set to start automatically will need to be started manually after your server comes back online.

    • If you prefer, you can shut down your server yourself before maintenance.

    Start: Immediately
    Expected impact: About 40–60 minutes per server.

    We apologize for any inconvenience this may cause. Microsoft has rated these vulnerabilities as Critical, and applying the patches promptly is essential to keeping your servers and data secure. We also strongly recommend installing the latest Windows updates on your own server as soon as possible.

    If you have any questions, please open a support ticket.

  • IdentifiedUTC

    Microsoft has just released security updates for several Critical vulnerabilities affecting Windows Server, including the Hyper-V platform our host nodes run on. To protect customer workloads, we are applying these updates to all host nodes on an emergency basis.

    Start: Immediately
    Expected impact: About 40–60 minutes per server. We’re patching host nodes in batches, so not all servers will be affected at the same time.

    Your server will be unreachable during maintenance. It will not be restarted, and everything running on it will continue as normal once maintenance is complete.

    Recommended action: Depending on the Windows features and services running on your server, these vulnerabilities may also affect it. We strongly recommend installing the latest Windows updates on your server as soon as possible.

    We’ll post an update here when all host nodes are patched. If you have any questions, please open a support ticket.

Oct 2026

No notices reported this month

Previous

Sep 2026 to Nov 2026

Next