# LlamaIndex: AWS outage - some llamacloud services may be degraded

- Impact (vendor’s label): major
- Status: resolved
- Started: 2025-10-20 09:31 UTC · Resolved: 2025-10-20 12:20 UTC · Duration: 2.8 h
- Updates: 3 · Affected components: LlamaCloud - LlamaCloud Public API, LlamaParse API, LlamaCloud - LlamaParse
- [Vendor status page: https://stspg.io/t4j0tzvwtk5f](https://stspg.io/t4j0tzvwtk5f)
- [Company: LlamaIndex](https://rewindex.com/company/llamaindex.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 +2 h 21 min vs AWS’s own post)
- Evidence: “…AWS outage - some llamacloud services may be degraded This incident has been resolved. AWS is still not 100% up, but LlamaCloud seems to be running smoothly now. We're still waiting on AWS to confirm…”

```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["LlamaIndex (this incident)<br/>posted +2 h 21 min"]:::me
  h4 --- 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 09:31 UTC: We are currently investigating this issue.
- **monitoring** 2025-10-20 10:36 UTC: AWS is still not 100% up, but LlamaCloud seems to be running smoothly now. We're still waiting on AWS to confirm everything is solved on their side.
- **resolved** 2025-10-20 12:20 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2025-10-20 09:31 UTC: [Major incident: AWS outage - some llamacloud services may be degraded](https://rewindex.com/change/i820910065e053b.md)


---
Canonical: https://rewindex.com/company/llamaindex/incidents/lknwrcl4pv9r · Markdown: https://rewindex.com/company/llamaindex/incidents/lknwrcl4pv9r.md · JSON: https://rewindex.com/api/v1/companies/llamaindex/incidents/lknwrcl4pv9r · Generated 2026-10-20T01:32:30.325Z