- Level
- confirmed
- Worst impact
- Maintenance
- Components
- API
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.Check that everything you run on Descope came back after the window closed 2026-07-26 03:00 UTC.
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: Maintenance Duration: 9 minutes Affected Components: API Jul 26, 03:09:05 GMT+0 - Completed - Maintenance has completed successfully. Jul 26, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 25, 22:56:48 GMT+0 - Identified - **There is no traffic impact at all.** The database architecture utilizes high-availability, redundant clusters, allowing traffic to route seamlessly through secondary instances during the update. All live authentication flows, user registrations, token validations, and Descope Console operations will continue to function normally without disruption. [support@descope.com](mailto:support@descope.com)
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-e1b849e10c
Is this Descope maintenance still going on?
No, it ended 2026-07-26 03:00 UTC.
How long did it last?
0m, from 2026-07-26 03:00 UTC to 2026-07-26 03:00 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.