Descope: Scheduled Caching Maintenance
Affected components: API
Timeline of updates
- identified
Maintenance is now in progress.
- completed
Maintenance has completed successfully.
- identified
We will perform scheduled maintenance on our caching infrastructure. No downtime is expected, and no action is required on your part. [support@descope.com](mailto:support@descope.com).
Changes Rewindex caught on this incident
- Incident silently edited: Scheduled Caching Maintenance
- Incident updated: Scheduled Caching Maintenance
- Incident updated: Scheduled Caching Maintenance
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6a2f3760ee3821c8…Version 2 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
77d9c73b5b8dd22e…Version 3 captured
In the 2026-10-25 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e81c14536c0c31fb…Version 4 captured
In the 2026-10-25 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d16dd9a03f0d88bb…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on descopestatus.com (opens in new tab).
Cite this
Maintenance posted by Descope, started 2026-10-25 05:30 UTC, resolved after 30 min, 3 update(s); edited after publishing.
- Title
- Scheduled Caching Maintenance
- Vendor
- Descope
- Date
- URL
- https://rewindex.com/company/descope/incidents/cmvijso2r08bb13nz40isklq1
Descope profileRecent Descope incidentsAll outages on October 25, 2026Descope in October 2026MarkdownJSON