Skip to main content
LlamaCloud

Service Degradation and High Latency

Partial outage Lasted 54m · started · LlamaCloud's page

Level
confirmed
Worst impact
Partial outage
Components
LlamaParse API, LlamaParse API, LlamaParse UI, LlamaParse UI
Down Index
43of 100

What to do

  • Check whether you use LlamaCloud LlamaParse API, LlamaParse API, LlamaParse UI, LlamaParse UI. 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 54m it lasted.

    Anything that failed between 2026-05-31 03:23 UTC and 2026-05-31 04:17 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. 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-48b2f06d3b

Is LlamaCloud still down?

No, this incident was resolved 2026-05-31 04:17 UTC. For LlamaCloud's live state, see https://down.guide/llamaindex.

How long did it last?

54m, from 2026-05-31 03:23 UTC to 2026-05-31 04:17 UTC, by the times LlamaCloud posted.

What was affected?

LlamaCloud named LlamaParse API, LlamaParse API, LlamaParse UI, LlamaParse UI.

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.