Retell AI: AWS outage causing some login issues, and history and analytics issue. Calls are NOT impacted.
AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents
Retell AI’s incident blames AWS as the cause. (hop 1, posted +11 h 51 min vs AWS’s own post)
“…AWS outage causing some login issues, and history and analytics issue. Calls are NOT impacted. This incident has been resolved. Starting from Oct 20 1am PST, the AWS outage has caused some login issue…”
Swipe sideways to see the whole diagram.
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["Retell AI (this incident)<br/>posted +11 h 51 min"]:::me
later --- meFull 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: Dashboard
Timeline of updates
- identified
Starting from Oct 20 1am PST, the AWS outage has caused some login issues, and call history and analytics issues. Regular calls are NOT impacted. Once the AWS outage is over, we will backfill the analytics.
- monitoring
The AWS outage has been resolved. We are going to backfill analytics, and keep a close eye on it.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 17:03 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
704f5ba673232e08…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).