# LlamaIndex: Increased Parse Latency
- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-05-08 00:11 UTC · Resolved: 2026-05-08 01:07 UTC · Duration: 56 min
- Updates: 3 · Affected components: LlamaParse API, LlamaParse (Global) - LlamaParse API, LlamaParse API, LlamaParse (EU) - LlamaParse API
- [Vendor status page: https://stspg.io/8g294gzpn9z2](https://stspg.io/8g294gzpn9z2)
- [Company: LlamaIndex](https://rewindex.com/company/llamaindex.md)
## Part of an outage event
- [AWS us-east-1 outage, May 8, 2026: 38 vendors, 43 incidents](https://rewindex.com/events/2026-05-08-aws-us-east-1)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −13 min vs AWS’s own post)
```mermaid
flowchart LR
root["AWS us-east-1
posted 00:25 UTC"]:::root
before["Posted before AWS did
3 vendors, 2 blamed AWS
Neon, Datadog, Convex"]:::blames
root --> before
h1["Within an hour
11 vendors, 11 blamed AWS
Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
root --> h1
h4["1 to 4 hours later
10 vendors, 9 blamed AWS
Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
root --> h4
later["Later
2 vendors, 2 blamed AWS
Wiz, SingleStore"]:::blames
root --> later
me["LlamaIndex (this incident)
posted −13 min"]:::me
root -.->|"same window"| 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** 2026-05-08 00:11 UTC: We are currently investigating this issue.
- **investigating** 2026-05-08 00:12 UTC: We are continuing to investigate this issue.
- **resolved** 2026-05-08 01:07 UTC: This incident has been resolved.
---
Canonical: https://rewindex.com/company/llamaindex/incidents/3xglrdt4p7jm · Markdown: https://rewindex.com/company/llamaindex/incidents/3xglrdt4p7jm.md · JSON: https://rewindex.com/api/v1/companies/llamaindex/incidents/3xglrdt4p7jm · Generated 2026-10-19T23:15:54.767Z