- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 100
What to do
Check whether your product depends on LlamaCloud. 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 15m it lasted.
Anything that failed between 2025-07-25 16:36 UTC and 2025-07-25 16:51 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 2
- identified
We're seeing degraded performance caused by an ongoing Red Hat Quay incident affecting our autoscaling
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-3c926bb844
Is LlamaCloud still down?
No, this incident was resolved 2025-07-25 16:51 UTC. For LlamaCloud's live state, see https://down.guide/llamaindex.
How long did it last?
15m, from 2025-07-25 16:36 UTC to 2025-07-25 16:51 UTC, by the times LlamaCloud posted.
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.