Rewindex

CompaniesLlamaIndexIncidents

LlamaIndex: Vercel is Down :(

CriticalStatus: resolvedStarted Resolved (6 min)1 updatellamaindex.statuspage.io (opens in new tab)
Part of an outage event

Vercel outage, Aug 7, 2024 · 10 vendors, 11 incidents

LlamaIndex’s incident blames Vercel as the cause. (hop 1, posted +7 min vs Vercel’s own post)

“…Vercel is Down :( This incident has been resolved.…”

Swipe sideways to see the whole diagram.

Vercelposted 19:13 UTCWithin an hour2 vendors, 2 blamed VercelLlamaIndex, DailyLlamaIndex (this incident)posted +7 min
Vercelposted 19:13 UTCWithin an hour2 vendors, 2 blamed VercelLlamaIndex, DailyLlamaIndex (this incident)posted +7 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["Vercel<br/>posted 19:13 UTC"]:::root
  h1["Within an hour<br/>2 vendors, 2 blamed Vercel<br/>LlamaIndex, Daily"]:::blames
  root --> h1
  me["LlamaIndex (this incident)<br/>posted +7 min"]:::me
  h1 --- 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.

Timeline of updates

  1. resolved

    This incident has been resolved.

From LlamaIndex’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

LlamaIndex profileRecent LlamaIndex incidentsMarkdownJSON