Vercel: Increased 400s across Middleware and Edge Function invocations
Vercel outage, Aug 7, 2024 · 4 vendors, 5 incidents
Vercel’s incident is the root of the event (the provider’s own post). (root, posted +0 min vs Vercel’s own post)
Swipe sideways to see the whole diagram.
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
class root meFull 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
- resolved
This incident has been resolved. We have published a report in our blog: https://vercel.com/blog/update-regarding-vercel-service-disruption-on-august-7-2024 (opens in new tab)
From Vercel’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 www.vercel-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Vercel, started 2024-08-07 19:13 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Increased 400s across Middleware and Edge Function invocations
- Vendor
- Vercel
- Date
- URL
- https://rewindex.com/company/vercel/incidents/f6b2blrl5f5f
Vercel profileRecent Vercel incidentsAll outages on August 7, 2024Vercel in August 2024MarkdownJSON