Elevated API and AuthKit errors for some requests (Columbus, OH region)

What to do

• Check whether your product depends on WorkOS. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-01 15:30 UTC and 2026-10-01 15:30 UTC may need a replay.

• Subscribe to WorkOS's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=workos works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from WorkOS 1

1. resolvedOct 1, 2026, 3:30 PM UTC

   On October 1, 2026, from 11:34 to 11:40 AM EDT, our CDN provider had a network problem at its Columbus, Ohio location. Some requests to the WorkOS API (api.workos.com) and to AuthKit-hosted pages failed with HTTP 500 or 403 errors. Only requests routed through that location were affected. At the peak, about 8% of all API requests failed, including Audit Logs event ingestion, authentication and Vault decrypt calls. WorkOS systems stayed healthy the whole time and the provider fixed the problem by 11:40 AM EDT. Audit Logs event ingestion (POST /audit_logs/events) was the most affected endpoint: up to 21% of event submissions failed at the peak. Events from failed requests were not recorded. If your application did not retry them, resend any audit log events submitted between 11:34 and 11:40 AM EDT.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.