# Descope: Elevated error rate in connectors used in flows

- Impact (vendor’s label): unknown
- Status: resolved
- Started: 2025-10-20 14:45 UTC · Resolved: 2025-10-20 18:23 UTC · Duration: 3.6 h
- Updates: 4 · Affected components: API
- [Vendor status page: https://descopestatus.com/incident/cmgzb7bsi05dtl6heipaq4aio](https://descopestatus.com/incident/cmgzb7bsi05dtl6heipaq4aio)
- [Company: Descope](https://rewindex.com/company/descope.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1)
- This incident blames AWS as the cause. (hop 1, posted +7 h 34 min vs AWS’s own post)
- Evidence: “…rate in connectors used in flows We are currently investigating this incident. Related to AWS outage in lambda service. Fix was implemented by our cloud provider and we are currently monitoring the re…”

```mermaid
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 +7 h 34 min"]:::me
  later --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **investigating** 2025-10-20 14:45 UTC: We are currently investigating this incident. Related to AWS outage in lambda service.
- **identified** 2025-10-20 16:31 UTC: We are continuing to work on a fix for this incident. Issue related to high error rate on AWS lambda service, working on mitigating issue.
- **monitoring** 2025-10-20 17:53 UTC: Fix was implemented by our cloud provider and we are currently monitoring the result..
- **resolved** 2025-10-20 18:23 UTC: This incident has been resolved..


---
Canonical: https://rewindex.com/company/descope/incidents/cmgzb7bsi05dtl6heipaq4aio · Markdown: https://rewindex.com/company/descope/incidents/cmgzb7bsi05dtl6heipaq4aio.md · JSON: https://rewindex.com/api/v1/companies/descope/incidents/cmgzb7bsi05dtl6heipaq4aio · Generated 2026-10-20T00:19:29.993Z