Descope: Elevated error level

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-20 07:00 UTC and 2025-10-20 07: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.

resolvedOct 20, 2025, 7:00 AM UTC
Type: Incident Duration: 2 hours and 26 minutes Affected Components: API, Console, US 🇺🇸 → Oct 20, 09:25:46 GMT+0 - Monitoring - AWS implemented a fix, error level seem to go down drastically We are currently monitoring the result. Oct 20, 09:25:46 GMT+0 - Resolved - This incident has been resolved. Oct 20, 08:24:58 GMT+0 - Identified - Console is recovering partially Oct 20, 08:18:38 GMT+0 - Identified - Impact on another provider (Vercel) is impacting also console Oct 20, 07:29:06 GMT+0 - Identified - We are continuing to work on a fix for this incident. We have identified related to issue on AWS cloud provider Oct 20, 07:00:00 GMT+0 - Investigating - We are currently investigating this incident.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Descope still down?

No, this incident was resolved 2025-10-20 07:00 UTC. For Descope's live state, see https://down.guide/descope.

How long did it last?

0m, from 2025-10-20 07:00 UTC to 2025-10-20 07:00 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.