- Level
- confirmed
- Worst impact
- Major outage
- Components
- LlamaParse API, LlamaParse API
- Regions
- eu, us
What to do
Check whether you use LlamaCloud LlamaParse API, LlamaParse API in eu, us. 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 53m it lasted.
Anything that failed between 2026-03-01 13:31 UTC and 2026-03-01 16:24 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 6
- investigating
We are currently investigating the issue
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
We have identified the issue, EU is now back online, US will be soon up.
provider
- monitoring
We have identify the issue and deploy a fix. Service are going back to normal progressively
provider
- monitoring
We are continuing to monitor for any further issues.
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-293d07b189
Is LlamaCloud still down?
No, this incident was resolved 2026-03-01 16:24 UTC. For LlamaCloud's live state, see https://down.guide/llamaindex.
How long did it last?
2h 53m, from 2026-03-01 13:31 UTC to 2026-03-01 16:24 UTC, by the times LlamaCloud posted.
What was affected?
LlamaCloud named LlamaParse API, LlamaParse API in eu, us.
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.