- 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-10-30 13:55 UTC and 2025-10-30 13:55 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: 1 hour and 2 minutes Affected Components: Console, API, US 🇺🇸 → Oct 30, 14:01:00 GMT+0 - Resolved - This incident has been resolved. We will do a full post mortem, but from initial analysis it seems our internal queue system was overwhelmed from internal service creating very high amount of events in short period of time. Oct 30, 14:00:00 GMT+0 - Monitoring - Error level went down, seems like momentarily issue with queueing system Oct 30, 13:55: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-22d883b3bb
Is Descope still down?
No, this incident was resolved 2025-10-30 13:55 UTC. For Descope's live state, see https://down.guide/descope.
How long did it last?
0m, from 2025-10-30 13:55 UTC to 2025-10-30 13:55 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.