- Level
- confirmed
- Worst impact
- Partial outage
- Components
- LlamaParse API
- Down Index
- 34of 100
What to do
Check whether you use LlamaCloud LlamaParse API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 49m it lasted.
Anything that failed between 2025-10-20 09:31 UTC and 2025-10-20 12:20 UTC may need a replay.Subscribe to LlamaCloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=llamaindex works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from LlamaCloud 3
- investigating
We are currently investigating this issue.
provider
- monitoring
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.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-55762b6a88
Is LlamaCloud still down?
No, this incident was resolved 2025-10-20 12:20 UTC. For LlamaCloud's live state, see https://down.guide/llamaindex.
How long did it last?
2h 49m, from 2025-10-20 09:31 UTC to 2025-10-20 12:20 UTC, by the times LlamaCloud posted.
What was affected?
LlamaCloud named LlamaParse API.
What caused it?
LlamaCloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
LlamaCloud's official status page, https://llamaindex.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.