Rewindex

CompaniesLlamaIndexIncidents

LlamaIndex: Increased Parse Latency

MinorStatus: resolvedStarted Resolved (56 min)3 updatesstspg.io (opens in new tab)
Part of an outage event

AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents

LlamaIndex’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −13 min vs AWS’s own post)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack, Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign, Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreLlamaIndex (this incident)posted −13 min
same windowAWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack,Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign,Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreLlamaIndex (this incident)posted −13 min
LlamaIndex is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>posted 00:25 UTC"]:::root
  before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
  root --> before
  h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::blames
  root --> later
  me["LlamaIndex (this incident)<br/>posted −13 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: LlamaParse APILlamaParse (Global) - LlamaParse APILlamaParse APILlamaParse (EU) - LlamaParse API

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are continuing to investigate this issue.

  3. resolved

    This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

LlamaIndex profileRecent LlamaIndex incidentsMarkdownJSON