Rewindex

CompaniesDescopeIncidents

Descope: Seeing elevated amount of http errors of 520 status code

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

Cloudflare outage, Jun 22, 2026 · 9 vendors, 9 incidents

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

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareSprout Social, LeverDescope (this incident)posted −51 min
same windowCloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareSprout Social, LeverDescope (this incident)posted −51 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/>2 vendors, 2 blamed Cloudflare<br/>Sprout Social, Lever"]:::blames
  root --> h1
  me["Descope (this incident)<br/>posted −51 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

Timeline of updates

  1. investigating

    We are currently investigating this incident. seems related to our CDN provider, seems to be only affecting small number of requests .

  2. monitoring

    seeing error level back to normal.

  3. 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