LlamaIndex: Website Login Issues
AWS outage, Jul 16, 2026 · 27 vendors, 29 incidents
LlamaIndex’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 1 min vs AWS’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>posted 08:44 UTC"]:::root
before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
root --> before
h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
root --> h1
p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
root -.-> p0
k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
p0 -->|"blamed Anthropic"| k0
me["LlamaIndex (this incident)<br/>posted +1 h 1 min"]:::me
root -.->|"same window"| 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: LlamaParse (Global) - LlamaParse UILlamaParse UILlamaParse (EU) - LlamaParse UILlamaParse UI
Timeline of updates
- investigating
We are investigating an issue with our authentication provider impacting our login flow. API is unaffected.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
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
13648674388d9618…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).