- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 9of 100
What to do
Check whether you use Descope 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-06-22 13:33 UTC and 2026-06-22 13:33 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: API Jun 22, 14:34:33 GMT+0 - Resolved - This incident has been resolved. Jun 22, 14:23:00 GMT+0 - Monitoring - seeing error level back to normal Jun 22, 13:33:00 GMT+0 - Investigating - We are currently investigating this incident. seems related to our CDN provider, seems to be only affecting small number of requests
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-8d4af11293
Is Descope still down?
No, this incident was resolved 2026-06-22 13:33 UTC. For Descope's live state, see https://down.guide/descope.
How long did it last?
0m, from 2026-06-22 13:33 UTC to 2026-06-22 13:33 UTC, by the times Descope posted.
What was affected?
Descope named 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.