Descope: Scheduled Database Cluster Optimization
Affected components: API
Timeline of updates
- identified
Maintenance is now in progress.
- completed
Maintenance has completed successfully..
- identified
We will be performing routine maintenance and performance tuning on our primary database clusters. 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.
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 this record existed by then and has 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-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
671fa788aa07dfaa…
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-07-12 03:00 UTC, resolved after 17 min, 3 update(s).
- Title
- Scheduled Database Cluster Optimization
- Vendor
- Descope
- Date
- URL
- https://rewindex.com/company/descope/incidents/cmrds54wc02ic0ks35uo01vun
Descope profileRecent Descope incidentsAll outages on July 12, 2026Descope in July 2026MarkdownJSON