rewindex

CompaniesDescopeIncidents

Descope: High error rate on Management API calls

unknownStatus: postmortemStarted Resolved (5 d)3 updatesdescopestatus.com (opens in new tab)

Affected components: APIAPI

Timeline of updates

  1. investigating

    We are currently investigating this incident..

  2. resolved

    This incident has been resolved..

  3. postmortem

    The incident was caused by a regression in the middleware layer responsible for header parsing. The logic error prevented the middleware from correctly validating standard request headers, leading to a surge in 400 Bad Request responses. Full RCA will be delivered upon request, reach out to support for that..

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.

Impact, status and times are the vendor’s own, as last archived. View on descopestatus.com (opens in new tab).

Descope profileRecent Descope incidentsMarkdownJSON