- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, API
- Down Index
- 11of 100
What to do
Check whether you use Descope API, API. 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-03-09 22:00 UTC and 2026-03-09 22:00 UTC may need a replay.Subscribe to Descope's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=descope works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Descope 1
- resolved
Type: Incident Duration: 15 minutes Affected Components: API, API Mar 15, 08:12:30 GMT+0 - Postmortem - The incident was caused by a regression in the middleware layer responsible for header parsing. The logic error prevented the middleware from correctly validating standard request headers, leading to a surge in 400 Bad Request responses. Full RCA will be delivered upon request, reach out to support for that. Mar 9, 22:15:00 GMT+0 - Resolved - This incident has been resolved. Mar 9, 22:00:00 GMT+0 - Investigating - We are currently investigating this incident.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-50646781e0
Is Descope still down?
No, this incident was resolved 2026-03-09 22:00 UTC. For Descope's live state, see https://down.guide/descope.
How long did it last?
0m, from 2026-03-09 22:00 UTC to 2026-03-09 22:00 UTC, by the times Descope posted.
What was affected?
Descope named API, API.
What caused it?
Descope hasn't published a root cause. If it does, it shows here.
Where does this come from?
Descope's official status page, https://descopestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.