Postmortem -
Read details
Apr 23, 17:32 UTC
Resolved -
The incident was caused by an internal configuration error during routine preparation of new infrastructure. A single AWS flag was incorrectly set, which applied non-production-ready changes to the production environment. Because these changes were propagated across all resources, our regional failover did not activate as expected.
Apr 20, 16:00 UTC