LlamaIndex Outage History

LlamaIndex is up right now

Pingoru has recorded 37 incidents for LlamaIndex: 32 in the last 12 months and 4 in the last 90 days.

Source: llamaindex.statuspage.io

37incidents recorded
32last 12 months
4last 90 days
2 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking LlamaIndex in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202620 of 720 (0%)
May 202653 of 744 (0%)
June 202644 of 720 (1%)
July 202643 of 744 (0%)
August 202600 of 744 (0%)
September 2026329 of 720 (4%)
October 202600 of 508 (0%)

Incidents, newest first

Major September 29, 2026 Classify and Split API Degraded 1d 1h LlamaParse API

Started Sep 29, 2026, 03:57 PM UTC· resolved Sep 30, 2026, 05:12 PM UTC

  1. identified Sep 29, 2026, 03:57 PM UTC

    We are investigating an outage affecting the Split/Classify API caused by reduced availability of an upstream model provider. Requests may fail while the issue continues. We are working to restore service and will post another update as soon as we have more information.

Read the full incident report →

Minor September 29, 2026 400 errors for some extract schemas 1h 44m LlamaParse API, LlamaParse API

Started Sep 29, 2026, 02:19 PM UTC· resolved Sep 29, 2026, 04:04 PM UTC

  1. identified Sep 29, 2026, 02:19 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Sep 29, 2026, 03:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 29, 2026, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 17, 2026 High error rate for agentic parse in EU 1h 41m LlamaParse API

Started Sep 17, 2026, 06:48 PM UTC· resolved Sep 17, 2026, 08:30 PM UTC

  1. identified Sep 17, 2026, 06:48 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Sep 17, 2026, 07:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 17, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2026 High latency for Parse API 12m LlamaParse API

Started Jul 30, 2026, 11:11 PM UTC· resolved Jul 30, 2026, 11:23 PM UTC

  1. investigating Jul 30, 2026, 11:11 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 30, 2026, 11:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 16, 2026 Website Login Issues 38m LlamaParse UI, LlamaParse UI

Started Jul 16, 2026, 09:44 AM UTC· resolved Jul 16, 2026, 10:22 AM UTC

  1. investigating Jul 16, 2026, 09:44 AM UTC

    We are investigating an issue with our authentication provider impacting our login flow. API is unaffected.

  2. resolved Jul 16, 2026, 10:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 14, 2026 Elevated latency for parse & extract APIs 10m LlamaParse API

Started Jul 14, 2026, 05:36 PM UTC· resolved Jul 14, 2026, 05:47 PM UTC

  1. investigating Jul 14, 2026, 05:36 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 14, 2026, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 2, 2026 Degraded parsing latency 1h 59m LlamaParse API, LlamaParse API

Started Jul 02, 2026, 02:40 AM UTC· resolved Jul 02, 2026, 04:39 AM UTC

  1. investigating Jul 02, 2026, 02:40 AM UTC

    We are currently investigating this issue.

  2. resolved Jul 02, 2026, 04:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 24, 2026 Elevated API Errors 2h 6m LlamaParse API

Started Jun 24, 2026, 01:59 AM UTC· resolved Jun 24, 2026, 04:05 AM UTC

  1. investigating Jun 24, 2026, 01:59 AM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. monitoring Jun 24, 2026, 02:36 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 24, 2026, 04:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 16, 2026 Degraded Parsing Throughput 8m LlamaParse API, LlamaParse API

Started Jun 16, 2026, 05:21 PM UTC· resolved Jun 16, 2026, 05:30 PM UTC

  1. investigating Jun 16, 2026, 05:21 PM UTC

    We are investigating decreased parsing throughput and higher latency

  2. resolved Jun 16, 2026, 05:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 4, 2026 Parse cost effective degraded 1h 46m LlamaParse API

Started Jun 04, 2026, 09:01 PM UTC· resolved Jun 04, 2026, 10:48 PM UTC

  1. identified Jun 04, 2026, 09:01 PM UTC

    Degraded performance and increased latency on cost effective mode due to an upstream model provider outage

  2. resolved Jun 04, 2026, 10:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 3, 2026 Increased parse latency 24m LlamaParse API, LlamaParse API

Started Jun 03, 2026, 01:43 PM UTC· resolved Jun 03, 2026, 02:08 PM UTC

  1. investigating Jun 03, 2026, 01:43 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 03, 2026, 01:52 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 03, 2026, 01:57 PM UTC

    An upstream compute provider had an outage. Services are recovering

  4. resolved Jun 03, 2026, 02:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 31, 2026 Service Degradation and High Latency 53m LlamaParse API, LlamaParse API, LlamaParse UI, LlamaParse UI

Started May 31, 2026, 03:23 AM UTC· resolved May 31, 2026, 04:17 AM UTC

  1. investigating May 31, 2026, 03:23 AM UTC

    We are currently investigating this issue.

  2. resolved May 31, 2026, 04:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026 Increased Parse Latency 55m LlamaParse API, LlamaParse API

Started May 08, 2026, 12:11 AM UTC· resolved May 08, 2026, 01:07 AM UTC

  1. investigating May 08, 2026, 12:11 AM UTC

    We are currently investigating this issue.

  2. investigating May 08, 2026, 12:12 AM UTC

    We are continuing to investigate this issue.

  3. resolved May 08, 2026, 01:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 6, 2026 Data Processing Delays - Parse v2 –

Started May 06, 2026, 11:30 AM UTC· resolved May 06, 2026, 11:30 AM UTC

  1. resolved May 06, 2026, 02:12 PM UTC

    Parse jobs delayed up to 30m, lasting between 11:30-13:00 UTC

Read the full incident report →

Notice May 5, 2026 System Degraded - Login and Job Resolution Issues 4m LlamaParse API, LlamaParse API, LlamaParse UI, LlamaParse UI

Started May 05, 2026, 08:55 PM UTC· resolved May 05, 2026, 08:59 PM UTC

  1. investigating May 05, 2026, 08:55 PM UTC

    We are currently investigating this issue.

  2. resolved May 05, 2026, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 28, 2026 API connectivity issues 22m LlamaParse API, LlamaParse UI

Started Apr 28, 2026, 08:01 PM UTC· resolved Apr 28, 2026, 08:24 PM UTC

  1. investigating Apr 28, 2026, 08:01 PM UTC

    We are currently investigating this issue.

  2. identified Apr 28, 2026, 08:16 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 28, 2026, 08:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 28, 2026, 08:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026 Increased latency on cost_effective –

Started Apr 21, 2026, 07:00 AM UTC· resolved Apr 21, 2026, 07:00 AM UTC

  1. resolved Apr 21, 2026, 08:23 PM UTC

    Increase latency from upstream provider causing slower than usual parsing on cost_effective mode in EU zone

Read the full incident report →

Notice March 16, 2026 Jobs not running 42m LlamaParse API, LlamaParse API

Started Mar 16, 2026, 10:39 PM UTC· resolved Mar 16, 2026, 11:22 PM UTC

  1. investigating Mar 16, 2026, 10:39 PM UTC

    We are currently investigating this issue.

  2. identified Mar 16, 2026, 11:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 16, 2026, 11:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 16, 2026, 11:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 11, 2026 Increase parse v2 and extract latency 1h 39m LlamaParse API

Started Mar 11, 2026, 08:43 PM UTC· resolved Mar 11, 2026, 10:22 PM UTC

  1. investigating Mar 11, 2026, 08:43 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 11, 2026, 09:41 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 11, 2026, 09:41 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Mar 11, 2026, 10:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 11, 2026, 10:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2026 Elevated Latency 1h 44m LlamaParse API, LlamaParse UI

Started Mar 10, 2026, 12:32 AM UTC· resolved Mar 10, 2026, 02:17 AM UTC

  1. investigating Mar 10, 2026, 12:32 AM UTC

    We are investigating elevated latency in Index API

  2. identified Mar 10, 2026, 01:07 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 10, 2026, 01:44 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Mar 10, 2026, 01:44 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 10, 2026, 02:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 3, 2026 High Job Latency 1h 14m LlamaParse API, LlamaParse UI

Started Mar 03, 2026, 09:58 PM UTC· resolved Mar 03, 2026, 11:13 PM UTC

  1. investigating Mar 03, 2026, 09:58 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 03, 2026, 11:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026 System Outage 2h 33m LlamaParse API, LlamaParse UI

Started Mar 02, 2026, 05:52 PM UTC· resolved Mar 02, 2026, 08:26 PM UTC

  1. investigating Mar 02, 2026, 05:52 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 02, 2026, 07:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 02, 2026, 08:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026 EU LlamaParse partial outage - degraded accuracy 3h 31m LlamaParse API

Started Mar 02, 2026, 11:26 AM UTC· resolved Mar 02, 2026, 02:58 PM UTC

  1. investigating Mar 02, 2026, 11:26 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 02, 2026, 11:26 AM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 02, 2026, 02:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 1, 2026 Currently down in EU and NA 2h 52m LlamaParse API, LlamaParse API

Started Mar 01, 2026, 01:31 PM UTC· resolved Mar 01, 2026, 04:24 PM UTC

  1. investigating Mar 01, 2026, 01:31 PM UTC

    We are currently investigating the issue

  2. investigating Mar 01, 2026, 01:52 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 01, 2026, 01:53 PM UTC

    We have identified the issue, EU is now back online, US will be soon up.

  4. monitoring Mar 01, 2026, 02:23 PM UTC

    We have identify the issue and deploy a fix. Service are going back to normal progressively

  5. monitoring Mar 01, 2026, 02:28 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Mar 01, 2026, 04:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 9, 2025 [LlamaCloud EU] Partial outage on Index 10h 6m LlamaParse API, LlamaParse UI

Started Dec 09, 2025, 11:18 AM UTC· resolved Dec 09, 2025, 09:24 PM UTC

  1. investigating Dec 09, 2025, 11:18 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 09, 2025, 12:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 09, 2025, 09:24 PM UTC

    This incident has been resolved.

Read the full incident report →