Hyonix - Status Page

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

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

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.

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.

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.

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.

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.