On April 16, 2026, at approximately 1:17 AM ET, the Cloud Host supporting one or more of your services experienced a critical shutdown due to a hardware failure. This resulted in an unplanned service interruption for the affected servers.
Our investigation began immediately at approximately 1:17 AM ET. After determining that the incident was caused by a critical hardware failure, our Engineering team began recovery efforts using available VM backups at approximately 4:00 AM ET.
All affected servers were restored from the most recently available backup, dated Wednesday, April 15, 2026, at 6:00 PM ET. Services were fully restored for all affected servers by approximately 6:00 AM ET, resulting in a total service interruption of approximately 5 hours and 43 minutes.
Actual downtime may vary by server, as some affected servers were restored earlier than others.
Our investigation determined that the interruption was caused by a hardware failure involving the storage drive backplane within the affected Cloud Host.
This failure caused the host to stop recognizing the installed storage drives, which resulted in the hypervisor crashing and the affected Cloud services becoming unavailable.
To reduce the risk of further disruption, the affected host was removed from active service and marked so that no additional servers could be created on, or migrated to, that system.
To restore service as quickly as possible, our Engineering team restored the affected servers from the most recently available backups and brought them online on known-good Cloud Hosts.
Our Engineering team will fully service and evaluate the affected host before it is considered for any future production use.
No customer workloads will be returned to this system unless and until the evaluation is complete and the host is confirmed fit for continued production operation.
We apologize for the disruption this incident caused and appreciate your patience, understanding, and continued trust.