WORKOS · Vendor
NO FIX YET
WorkOS had a five-minute incident in which SSO sign-in requests were slow and a small number failed with HTTP 500 or 408 errors. It was an availability problem, with no sign that data was exposed or accessed.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Companies that let staff sign in to their apps through WorkOS-powered SSO may have seen failed or slow logins between 09:48 and 09:53 UTC on November 13, 2026. The incident is resolved and the sources describe no action for customers.
Not affected if no-workos-sso
Who cares saas, security, sso, workos
Unknown from the sources.
No fix yet, per the sources.
From 09:48 to 09:53 UTC on November 13, 2026, SSO sign-in requests were slow, and a small number failed with HTTP 500 errors or 408 timeouts. The slowdown affected SSO authorization, identity provider callbacks and token exchange.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.