Skip to main content
LlamaCloud

AWS outage - some service may be degradated

Degraded Lasted 30m · started · LlamaCloud's page

Level
confirmed
Worst impact
Degraded
Down Index
16of 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 30m it lasted.

    Anything that failed between 2025-10-20 07:22 UTC and 2025-10-20 07:52 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

  1. investigating

    We are currently monitoring this issue

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. resolved

    The incident is resolved, we will continue monitoring our service in case of regression.

    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-b697e1b83e

Is LlamaCloud still down?

No, this incident was resolved 2025-10-20 07:52 UTC. For LlamaCloud's live state, see https://down.guide/llamaindex.

How long did it last?

30m, from 2025-10-20 07:22 UTC to 2025-10-20 07:52 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.