# Daily: Impact from the ongoing AWS us-east-1 outage
- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-10-20 12:57 UTC · Resolved: 2025-10-21 15:22 UTC · Duration: 26 h
- Updates: 4 · Affected components: Dashboard, Core Call Experience
- [Vendor status page: https://stspg.io/2llg402c3csd](https://stspg.io/2llg402c3csd)
- [Company: Daily](https://rewindex.com/company/daily.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 47 min vs AWS’s own post)
- Evidence: “…Impact from the ongoing AWS us-east-1 outage This incident has been resolved. AWS has resolved their incident. We're continuing to run the same call servers in us-east-1 as we were before the incident…”
```mermaid
flowchart LR
root["AWS us-east-1
posted 07:11 UTC"]:::root
before["Posted before AWS did
5 vendors, 4 blamed AWS
Salesforce, Descope, Ashby +2"]:::blames
root --> before
h1["Within an hour
18 vendors, 17 blamed AWS
Asana, Firebolt, Monday.com +15"]:::blames
root --> h1
h4["1 to 4 hours later
30 vendors, 29 blamed AWS
SingleStore, Loops, Buildkite +27"]:::blames
root --> h4
later["Later
45 vendors, 44 blamed AWS
RudderStack, Airbyte, Unbounce +42"]:::blames
root --> later
p0["Twilio
posted +15 min"]:::blames
root --> p0
k0["BigCommerce
+2 h 46 min"]:::hop2
p0 -->|"blamed Twilio"| k0
p1["Webflow
posted +4 h 37 min, did not name AWS"]:::timing
root -.-> p1
k1["Rootly
+10 h 23 min"]:::hop2
p1 -->|"blamed Webflow"| k1
p2["Baseten
posted +4 min"]:::blames
root --> p2
k2["Zed
+26 h 20 min"]:::hop2
p2 -->|"blamed Baseten"| k2
me["Daily (this incident)
posted +5 h 47 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
- **identified** 2025-10-20 12:57 UTC: AWS is addressing an issue with DynamoDB that is causing problems with many of their services in us-east-1. We have seen issues loading the dashboard and docs sites, and for a few hours we've been unable to log in to Statuspage to update this site. We're sorry about that delay. Up until a few minutes ago, our metrics suggested that core call functionality wasn't being impacted. We just saw a small number of call failures in us-east-1, though. We're continuing to monitor the situation and do what we can to minimize this outage's impact on you and your customers. We'll post more information here as we have it.
- **identified** 2025-10-20 15:10 UTC: AWS is continuing to address issues in us-east-1. We're still seeing normal activity levels across our APIs and call servers for this time of day, so we have no reason to believe that any your customers' calls are actually being affected. Part of AWS's mitigation efforts involve limiting the rate at which we can start new call servers. Out of an abundance of caution, we're temporarily removing us-east-1 from our list of available regions for new call sessions. This means your users will likely connect to a call through us-west-2 instead. This failover happens automatically and transparently, and you don't need to do anything. We've already scaled up call servers in us-west-2 to handle the increase in sessions. We'll keep you posted as we continue to monitor the situation.
- **monitoring** 2025-10-21 00:50 UTC: AWS has resolved their incident. We're continuing to run the same call servers in us-east-1 as we were before the incident started, but we're still routing the majority of US traffic through us-west-2. We plan to return things to normal tomorrow.
- **resolved** 2025-10-21 15:22 UTC: This incident has been resolved.
---
Canonical: https://rewindex.com/company/daily/incidents/l730222c713w · Markdown: https://rewindex.com/company/daily/incidents/l730222c713w.md · JSON: https://rewindex.com/api/v1/companies/daily/incidents/l730222c713w · Generated 2026-10-20T00:06:41.074Z