Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

WorkOS Outage History

Every past WorkOS outage tracked by IsDown, with detection times, duration, and resolution details.

There were 110 WorkOS outages since July 2020. The 30 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 16, 2026

April 2026: Increased 429 Errors on /directory_users endpoint

Detected Apr 16, 2026 4:54 PM EDT · Resolved Apr 16, 2026 7:12 PM EDT · Duration about 2 hours

WorkOS experienced elevated HTTP 429 (Too Many Requests) error rates on the /directory_users endpoint for 2.3 hours. The issue impacted API requests to this endpoint, causing rate limiting errors for users attempting to access directory user data. The problem was resolved after deploying a fix, with error rates returning to normal levels.

Minor March 27, 2026

March 2026: Elevated Dashboard Errors

Detected Mar 27, 2026 5:57 PM EDT · Resolved Mar 27, 2026 7:18 PM EDT · Duration about 1 hour

WorkOS experienced a Dashboard issue where the custom branding editor's CSS code editor and JWT editor were unavailable for 1.4 hours. The functionality was restored and the service team confirmed the impact was resolved.

Minor March 17, 2026

March 2026: Elevated API Errors

Detected Mar 17, 2026 11:18 AM EDT · Resolved Mar 17, 2026 12:59 PM EDT · Duration about 2 hours

WorkOS experienced elevated API errors and increased latency for 1.7 hours. The issues affected API functionality and response times across their services. The incident was resolved after services returned to normal operation.

Major February 24, 2026

February 2026: Elevated API Errors

Detected Feb 24, 2026 5:11 AM EST · Resolved Feb 24, 2026 6:17 AM EST · Duration about 1 hour

WorkOS experienced elevated API errors and increased latency for 1.1 hours, impacting their API services. The engineering team identified the root cause and implemented a fix. All services returned to normal operation and the incident was resolved.