-
Maintenance
Scheduled Maintenance: Motherboard Replacement for AMD EPYC 5th Gen Host System (EPYC-501)
CompletedPlanned for:The replacement motherboard from ASRock has arrived. On Saturday, we will replace the defective motherboard in the EPYC-501 host system, thereby resolving the cause of the recurring reboots and “fatal hardware error” crashes that have occurred recently.
Timeframe: Saturday, August 1, 2026, 2:00 p.m. – 3:00 p.m.
Impact: All virtual servers on this host system will be shut down for the duration of the maintenance and will be unavailable. Data and configurations will be fully preserved—there will be no migration or reinstallation. Once the work is complete, we will automatically restart all systems.
We’ll keep you updated on the progress here on the status page and will notify you as soon as the maintenance is complete. Thank you for your patience over the past few days.
-
In progress (1 Monat ago)
We're now shutting down all EPYC501 VMs properly and starting the motherboard replacement.
-
In progress (1 Monat ago)
When booting up the new motherboard, the installed CPU is currently not being recognized. We assume that the factory-installed BIOS does not yet support the 5th-generation EPYC series, so we are first installing a BIOS update to the latest version.
Unfortunately, this means maintenance will take longer than planned. We’ll be able to provide a reliable new timeframe as soon as the update is complete and the system successfully initializes the CPU.
Until then, the VMs will remain shut down—of course, this will not affect any data or configurations.
We’ll post an update here with the latest progress. Thank you for your patience
-
In progress (1 Monat ago)
A quick update: We’re continuing to work on getting the new motherboard up and running. The BIOS update is in progress and is currently being verified—as soon as the board successfully initializes the CPU, we’ll reboot the systems.
Until then, the VMs remain shut down as usual; data and configurations are not affected.
We’ll post an update here as soon as there’s any news.
-
In progress (1 Monat ago)
Even after the BIOS update and several attempts—including testing with different component configurations and a CMOS reset—the new motherboard still does not recognize the CPU. We therefore assume that the replacement board is defective or incompatible.
To avoid further extending the downtime, we are now reinstalling the original motherboard and will then boot up the VMs. The new board is being returned to the retailer for inspection; as soon as a functional replacement is available, we will announce a new maintenance window in a timely manner.
Important: This means the original hardware issue will remain unresolved for the time being. Unexpected reboots may therefore occur again until the replacement can be completed.
We will notify you as soon as all VMs are back online.
-
Completed (1 Monat ago)
Update to the previous post: The EPYC-501 can no longer be run stably even with the original motherboard. The issue is therefore apparently more serious than initially assumed.
We have therefore migrated all VMs to other host systems in our EPYC series (3rd Gen). The VMs will restart there within the next few minutes—all data and configurations have been fully transferred.
EPYC-501 is being sent to the vendor for a full inspection. This will finally resolve the cause of the recurring crashes for the affected systems.
If your server is unreachable after it restarts, please contact Support.
We will provide a separate update here in the coming days regarding compensation for today’s downtime.
Affected: Host System - AMD EPYC 5th Gen Under maintenance -
24fire Status