Is LlamaCloud down? › Outage history
LlamaCloud outage history
LlamaCloud published 35 incidents on its official status page since Oct 16, 2025, 6 of them rated at the highest impact level. 4 were major or long incidents with their own pages; the biggest are listed first. Below them is every smaller incident, then our own 90 day check history.
Biggest LlamaCloud outages
Ranked by the official impact level, then by how long they lasted. Each has its own page with the cause, the fix time and every official update.
- Oct 20, 2025: Major service degradation due to AWS outage 13 hours 29 min · rated "Critical"
- Mar 1, 2026: Currently down in EU and NA 2 hours 53 min · rated "Critical"
- Dec 9, 2025: [LlamaCloud EU] Partial outage on Index 10 hours 6 min · rated "Major"
- Mar 2, 2026: EU LlamaParse partial outage - degraded accuracy 3 hours 31 min · rated "Major"
Every smaller LlamaCloud incident
Minor and short incidents from the LlamaIndex status page, newest first, each with a line from the official updates. Times are UTC.
September 2026
Sep 29, 2026, 14:19 UTC · 400 errors for some extract schemas
1 hour 44 min · rated "Minor"
"The issue has been identified and a fix is being implemented."
Sep 17, 2026, 18:48 UTC · High error rate for agentic parse in EU
1 hour 41 min · rated "Major"
"The issue has been identified and a fix is being implemented."
July 2026
Jul 30, 2026, 23:11 UTC · High latency for Parse API
12 minutes · rated "Minor"
"This incident has been resolved."
Jul 16, 2026, 09:44 UTC · Website Login Issues
38 minutes · rated "Critical"
"We are investigating an issue with our authentication provider impacting our login flow. API is unaffected."
Jul 14, 2026, 17:36 UTC · Elevated latency for parse & extract APIs
11 minutes · rated "Minor"
"This incident has been resolved."
Jul 2, 2026, 02:40 UTC · Degraded parsing latency
1 hour 59 min · rated "Minor"
"This incident has been resolved."
June 2026
Jun 24, 2026, 01:59 UTC · Elevated API Errors
2 hours 6 min · rated "Major"
"We're experiencing an elevated level of API errors and are currently looking into the issue."
Jun 16, 2026, 17:21 UTC · Degraded Parsing Throughput
9 minutes · rated "Major"
"We are investigating decreased parsing throughput and higher latency"
Jun 4, 2026, 21:01 UTC · Parse cost effective degraded
1 hour 47 min · marked as no impact
"Degraded performance and increased latency on cost effective mode due to an upstream model provider outage"
Jun 3, 2026, 13:43 UTC · Increased parse latency
24 minutes · rated "Critical"
"We are continuing to investigate this issue."
May 2026
May 31, 2026, 03:23 UTC · Service Degradation and High Latency
54 minutes · rated "Major"
"This incident has been resolved."
May 8, 2026, 00:11 UTC · Increased Parse Latency
56 minutes · rated "Minor"
"We are continuing to investigate this issue."
May 6, 2026, 23:35 UTC · Increased Parse Latency
1 hour 6 min · rated "Minor"
"A fix has been implemented and we are monitoring the results."
May 6, 2026, 14:12 UTC · Data Processing Delays - Parse v2
duration not stated · marked as no impact
"Parse jobs delayed up to 30m, lasting between 11:30-13:00 UTC"
May 5, 2026, 20:55 UTC · System Degraded - Login and Job Resolution Issues
4 minutes · marked as no impact
"This incident has been resolved."
April 2026
Apr 28, 2026, 20:01 UTC · API connectivity issues
22 minutes · marked as no impact
"The issue has been identified and a fix is being implemented."
Apr 21, 2026, 07:00 UTC · Increased latency on cost_effective
duration not stated · rated "Minor"
"Increase latency from upstream provider causing slower than usual parsing on cost_effective mode in EU zone"
March 2026
Mar 16, 2026, 22:39 UTC · Jobs not running
43 minutes · marked as no impact
"The issue has been identified and a fix is being implemented."
Mar 11, 2026, 20:43 UTC · Increase parse v2 and extract latency
1 hour 39 min · rated "Major"
"We are continuing to investigate this issue."
Mar 10, 2026, 00:32 UTC · Elevated Latency
1 hour 44 min · rated "Major"
"The issue has been identified and a fix is being implemented."
Mar 6, 2026, 23:46 UTC · Elevated Latency
2 hours 2 min · rated "Major"
"We are investigating elevated latency in Parse V2 and Extraction APIs"
Mar 3, 2026, 21:58 UTC · High Job Latency
1 hour 15 min · rated "Major"
"This incident has been resolved."
Mar 2, 2026, 17:52 UTC · System Outage
2 hours 34 min · rated "Major"
"A fix has been implemented and we are monitoring the results."
December 2025
Dec 8, 2025, 16:42 UTC · LlamaCloud Index Retrieval Elevated Error Rates
3 hours 11 min · rated "Minor"
"We are investigating elevated error rates in Index retrieval"
Dec 2, 2025, 22:29 UTC · Elevated Error Rates for Extract Requests
22 minutes · rated "Minor"
"This incident has been resolved."
Dec 1, 2025, 21:42 UTC · Elevated Latency for LlamaExtract
44 minutes · rated "Minor"
"This incident has been resolved."
November 2025
Nov 6, 2025, 20:52 UTC · Elevated Job Error Rates
50 minutes · rated "Critical"
"This incident has been resolved."
October 2025
Oct 27, 2025, 13:40 UTC · EU degraded performance and errors
1 hour 39 min · rated "Minor"
"A fix has been implemented and we are monitoring the results."
Oct 20, 2025, 09:31 UTC · AWS outage - some llamacloud services may be degraded
2 hours 49 min · rated "Major"
"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."
Oct 20, 2025, 07:22 UTC · AWS outage - some service may be degradated
30 minutes · rated "Minor"
"The incident is resolved, we will continue monitoring our service in case of regression."
Oct 16, 2025, 22:36 UTC · Service Outage
11 minutes · rated "Critical"
"This incident has been resolved."
LlamaCloud uptime, last 90 days
Tracked since Oct 7, 2026. Updated Oct 22, 2026, 12:35 UTC.
Every LlamaCloud problem in the last 90 days
No outages, degraded periods or maintenance recorded since Oct 7, 2026.
Day by day
| Day (UTC) | Uptime | Avg response | Worst |
|---|---|---|---|
| Oct 22, 2026 | 100% | 242 ms | Up |
| Oct 21, 2026 | 100% | 471 ms | Up |
| Oct 20, 2026 | 100% | 451 ms | Up |
| Oct 19, 2026 | 100% | 426 ms | Up |
| Oct 18, 2026 | 100% | 439 ms | Up |
| Oct 17, 2026 | 100% | 447 ms | Up |
| Oct 16, 2026 | 100% | 727 ms | |
| Oct 15, 2026 | 100% | 793 ms | |
| Oct 14, 2026 | 100% | 811 ms | Up |
| Oct 13, 2026 | 100% | 827 ms | Up |
| Oct 12, 2026 | 100% | 899 ms | Up |
| Oct 11, 2026 | 100% | 598 ms | Up |
| Oct 10, 2026 | 100% | 243 ms | Up |
| Oct 9, 2026 | 100% | 268 ms | |
| Oct 8, 2026 | 100% | 323 ms | Up |
| Oct 7, 2026 | 100% | 335 ms | Up |
LlamaCloud outage questions
Was LlamaCloud down today?
No. We recorded no LlamaCloud outage, degraded period or maintenance today (Oct 22, 2026, UTC).
Was LlamaCloud down yesterday?
No. We recorded no LlamaCloud outage, degraded period or maintenance yesterday (Oct 21, 2026, UTC).
When was LlamaCloud last down?
The latest incident on the LlamaIndex status page started Sep 29, 2026, 14:19 UTC: 400 errors for some extract schemas (1 hour 44 min).
What was the biggest LlamaCloud outage?
Of the incidents on record since Oct 16, 2025, the biggest was on Oct 20, 2025: Major service degradation due to AWS outage. The LlamaIndex status page rated it "Critical" and it lasted 13 hours 29 min.
How often does LlamaCloud go down?
LlamaCloud's status page posted 35 incidents since Oct 16, 2025, 1 of them in the last 30 days. Most incidents affect part of the service, not all of it. Uptime from our own checks over the last 90 days: 100%.
Times are UTC. Official incidents are the company's own posts, quoted from the LlamaIndex status page. Problem periods start when the official status page or our checks first show a problem and end when the service is next found working, so durations are accurate to within a few minutes. Recent outages across all services.