Skip to main content
Descope

Scheduled RedisUpgrade

Maintenance Lasted 0m · started · Descope's page

Level
confirmed
Worst impact
Maintenance
Components
API, Console, API, API, API

What to do

  • Check whether you use Descope API, Console, API, API and 1 more. 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-08-02 06: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

  1. resolved

    Type: Maintenance Duration: 30 minutes Affected Components: API, Console, API, API, API Aug 2, 06:29:47 GMT+0 - Completed - Maintenance has completed successfully. Aug 2, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 31, 16:28:27 GMT+0 - Identified - We will be migrating our Redis caching layer to perform planned infrastructure upgrades. **There is no traffic impact at all.** Core authentication APIs, active user sessions, and the Descope Console will remain fully operational throughout the window.

    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-a6002654d5

Is this Descope maintenance still going on?

No, it ended 2026-08-02 06:00 UTC.

How long did it last?

0m, from 2026-08-02 06:00 UTC to 2026-08-02 06:00 UTC, by the times Descope posted.

What was affected?

Descope named API, Console, API, API and 1 more.

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.