On the 20th of July 2026, there was an issue with the wake-up functionality affecting Personal Editions. This occurred in all three regions (US East, Europe and Asia Pacific).
Users were unable to wake up their environments from hibernation. When attempting to wake up the environments, they either remained in hibernation or moved to a "waking up" state indefinitely, preventing access to applications.
This was caused by an issue in how our backend systems processed environment status updates. Due to messages being processed out of order, some environments' internal state was incorrectly reverted to 'hibernated' after they had already woken up successfully, even though the environment itself remained accessible on the backend. This caused the ODC Portal to keep showing an inaccurate 'hibernated' or 'waking up' status, and repeated wake-up attempts did not resolve it since the underlying state kept getting overwritten.
We identified the root cause on the 21st of July and deployed a code fix to correct the state synchronization. The fix started to be rolled out to all regions on 22nd of July and completed by the 23rd of July. All affected environments were woken up successfully.
We are implementing additional state verification checks to ensure the ODC Portal and backend systems remain in sync. A full technical review is underway to identify similar synchronization gaps across other features.
We apologize for any disruption caused and thank you for your patience.