- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Descope in us. 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 2025-11-18 12:22 UTC and 2025-11-18 12:22 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: 2 hours and 32 minutes Affected Components: API, US 🇺🇸 → Nov 18, 14:54:43 GMT+0 - Resolved - This incident has been resolved. Nov 18, 14:46:37 GMT+0 - Monitoring - Edge provider implemented a fix and are currently monitoring the result. Nov 18, 12:36:24 GMT+0 - Identified - we are seeing a recovery on latency and error rates Nov 18, 12:22:57 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-1cda46ccb9
Is Descope still down?
No, this incident was resolved 2025-11-18 12:22 UTC. For Descope's live state, see https://down.guide/descope.
How long did it last?
0m, from 2025-11-18 12:22 UTC to 2025-11-18 12:22 UTC, by the times Descope posted.
What was affected?
Descope named in us.
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.