Rewindex

CompaniesDescopeIncidents

Descope: Elevated error level

unknownStatus: monitoringStarted Not resolved6 updatesdescopestatus.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents

Descope’s incident blames AWS as the cause. (hop 1, posted −11 min vs AWS’s own post)

“…Elevated error level We are currently investigating this incident.. AWS implemented a fix, error level seem to go down drastically We are currently monitoring the result. . Console is recovering parti…”

Swipe sideways to see the whole diagram.

blamed Twilioblamed Webflowblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com +151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite +27Later45 vendors, 44 blamed AWSRudderStack, Airbyte, Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did not name AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minDescope (this incident)posted −11 min
blamed Twilioblamed Webflowblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com+151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite+27Later45 vendors, 44 blamed AWSRudderStack, Airbyte,Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did notname AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minDescope (this incident)posted −11 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["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Descope (this incident)<br/>posted −11 min"]:::me
  before --- 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: APIConsole US 🇺🇸 →

Timeline of updates

  1. investigating

    We are currently investigating this incident..

  2. identified

    We are continuing to work on a fix for this incident. We have identified related to issue on AWS cloud provider.

  3. identified

    Impact on another provider (Vercel) is impacting also console.

  4. identified

    Console is recovering partially .

  5. monitoring

    AWS implemented a fix, error level seem to go down drastically We are currently monitoring the result. .

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