WorkOS: Intermittent 503 errors in certain regions
Affected components: AuthKitCore Services - AuthKitDashboardSupporting Services - Dashboard
Timeline of updates
- identified
We're seeing intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We've isolated this to an issue with an upstream provider and are working with them on a resolution.
- identified
We continue to see intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We will provide updates as they become available while we work with our upstream provider.
- identified
We continue to see intermittent 503 errors on a small fraction of requests routed through Ashburn, Virginia. We continue to work with the upstream provider.
- monitoring
Our upstream provider has mitigated the issue affecting those edge regions and 503 error rates have returned to normal.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Incident updated: Intermittent 503 errors in certain regions
- Incident updated: Intermittent 503 errors in certain regions
- Incident updated: Intermittent 503 errors in certain regions
- Incident updated: Intermittent 503 errors in certain regions
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0d31cbfbdcf99fa1…Version 2 captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
cc0755d5c5eb5dfd…Version 3 captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f59eedca0211785c…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.workos.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by WorkOS, started 2026-11-07 19:51 UTC, resolved after 4.3 h, 5 update(s); edited after publishing.
- Title
- Intermittent 503 errors in certain regions
- Vendor
- WorkOS
- Date
- URL
- https://rewindex.com/company/workos/incidents/95srzz0m0vv3
WorkOS profileRecent WorkOS incidentsAll outages on November 7, 2026WorkOS in November 2026MarkdownJSON