Advance - US Region - 502 Bad Gateway Errors
Timeline · 2 updates
- resolved Apr 08, 2026, 03:15 PM UTC
Our engineers have identified a load spike in the US region causing 502 Bad Gateway errors across the region.
- postmortem Apr 08, 2026, 03:16 PM UTC
A system outage occurred when a routine resource scale-up triggered an unexpected de-provisioning of our environment by AWS. Services are now stable. We are currently investigating the underlying cause with AWS support to ensure this does not recur.