# Sigma Computing: Error rates and latencies in the AWS US-EAST-1 Region impacting third party services

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-10-20 12:22 UTC · Resolved: 2025-10-20 07:00 UTC · Duration: -323 min
- Updates: 1
- [Vendor status page: https://stspg.io/bxr1kbcx50r2](https://stspg.io/bxr1kbcx50r2)
- [Company: Sigma Computing](https://rewindex.com/company/sigma-computing.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 +5 h 12 min vs AWS’s own post)
- Evidence: “…Error rates and latencies in the AWS US-EAST-1 Region impacting third party services Starting at 7:11 UTC, AWS reported increased error rates and latencies for multiple services in the US-EAST-1 Regio…”

```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["Sigma Computing (this incident)<br/>posted +5 h 12 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

- **resolved** 2025-10-20 07:00 UTC: Starting at 7:11 UTC, AWS reported increased error rates and latencies for multiple services in the US-EAST-1 Region. At 10:35 UTC, AWS declared the incident in the US-EAST-1 region mitigated. While Sigma's service was not impacted by the incident, third party services that Sigma uses were impacted. Customers may have experienced intermittent delays or failures when accessing or using cloud data warehouse services during the incident. Contacting Sigma Support via Live Chat or email was disrupted during the incident. Incident Start Time: 7:11 UTC Incident End Time: 10:35 UTC


---
Canonical: https://rewindex.com/company/sigma-computing/incidents/28rrh3vnlwy3 · Markdown: https://rewindex.com/company/sigma-computing/incidents/28rrh3vnlwy3.md · JSON: https://rewindex.com/api/v1/companies/sigma-computing/incidents/28rrh3vnlwy3 · Generated 2026-10-20T00:49:36.659Z