Live  /  WorkOS  /  Incident

WorkOS: Intermittent 503 errors in certain regions

WorkOS · workos.comMinor incidentResolved2026-11-08 00:10 UTC
Public — what happened

Summary

WorkOS said a small share of requests sent through certain regions, mainly Ashburn, Virginia, were intermittently failing with 503 errors starting at 19:51 UTC on 2026-11-07. The company said it traced the problem to an upstream provider and worked with that provider through the evening, posting updates that the errors were continuing. At 00:02 UTC on 2026-11-08, WorkOS said the provider had mitigated the issue and error rates were back to normal, and the incident was marked resolved at 00:10.

Affected

Dashboard, AuthKit

As listed on WorkOS’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach WorkOS against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for WorkOS: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the WorkOS report →

More from WorkOS

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the WorkOS status & history page.

Related: WorkOS status & history. SquidGrid is not affiliated with WorkOS.