Rewindex

CompaniesDescopeIncidents

Descope: Elevated error rates are reported which seem to be related to CDN/edge provider

unknownStatus: resolvedStarted Resolved (2.5 h)4 updatesdescopestatus.com (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Descope’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +53 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Descope (this incident)posted +53 min
same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Descope (this incident)posted +53 min
Descope is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Descope (this incident)<br/>posted +53 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: API US 🇺🇸 →

Timeline of updates

  1. investigating

    We are currently investigating this incident..

  2. identified

    we are seeing a recovery on latency and error rates .

  3. monitoring

    Edge provider implemented a fix and are currently monitoring the result..

  4. resolved

    This incident has been resolved..

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

Descope profileRecent Descope incidentsMarkdownJSON