# Aptible: Operation failures to to AWS API incident

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-10-20 07:47 UTC · Resolved: 2025-10-20 09:46 UTC · Duration: 2.0 h
- Updates: 4 · Affected components: Aptible Deploy, AWS EC2 - AWS EC2 (us-east-1 — Virginia), AWS EC2 (us-east-1 — Virginia)
- [Vendor status page: https://stspg.io/rm2t1b3th5m9](https://stspg.io/rm2t1b3th5m9)
- [Company: Aptible](https://rewindex.com/company/aptible.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 +36 min vs AWS’s own post)
- Evidence: “…Operation failures to to AWS API incident This incident has been resolved. AWS has indicated a fix has been applied, and we are re-enabling operations. We will continue to monitor for additional impac…”

```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["Aptible (this incident)<br/>posted +36 min"]:::me
  h1 --- 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 07:47 UTC: AWS is experiencing an issue with their APIs in us-east-1, and many services are impacted at this time. This may lead to failed operations, but there appears to be no impact to availability for apps and databases running on Aptible at this time.
- **monitoring** 2025-10-20 08:31 UTC: Since the AWS issues seem serious, and to avoid any operation failures causing resources to get stuck in a transitional state, we are taking action to block all new operations on the platform at this time. We have identified no impact to acceibilty or preformance of running apps and database containers at this time.
- **monitoring** 2025-10-20 09:30 UTC: AWS has indicated a fix has been applied, and we are re-enabling operations. We will continue to monitor for additional impact, as both Dockerhub and Quay.io were offline due to the AWS issue.
- **resolved** 2025-10-20 09:46 UTC: This incident has been resolved.


---
Canonical: https://rewindex.com/company/aptible/incidents/2qpxgjdll669 · Markdown: https://rewindex.com/company/aptible/incidents/2qpxgjdll669.md · JSON: https://rewindex.com/api/v1/companies/aptible/incidents/2qpxgjdll669 · Generated 2026-10-20T01:31:41.961Z