Rewindex

RewindexOutage eventsAug 7, 2024

Vercel outage, Aug 7, 2024

8 vendors posted 9 incidents between 19:00 and 20:00 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 2 vendors named Vercel in 3 incidents (2 of them blamed it). Vercel posted “Increased 400s across Middleware and Edge Function invocations” at 19:13 UTC.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when Vercel posted (19:13).

    3. Vercel posted 19:13
Named VercelNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Vercel, grouped by when they posted, and vendors that blamed one of the vendors Vercel took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Vercelposted 19:13 UTCWithin an hour2 vendors, 2 blamed VercelLlamaIndex, Daily
Vercelposted 19:13 UTCWithin an hour2 vendors, 2 blamed VercelLlamaIndex, Daily
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
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

Vendors that named Vercel

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

3 vendors

  • +7 min

    Blames Vercel

    Critical incident

    LlamaIndexVercel is Down :(

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

  • +15 min

    Blames Vercel

    Incident, no impact listed

    LlamaIndexJust kidding, Vercel is still down :(

    …Just kidding, Vercel is still down :( This incident has been resolved.…

  • +29 min

    Blames Vercel

    Minor incident

    Dailydashboard.daily.co availability

    …BAD_REQUEST messages when trying to load dashboard.daily.co. This is likely related to a Vercel incident: https://www.vercel-status.com/incidents/f6b2blrl5f5f The upstream issue has been resolved, an…

Same window, did not name anyone

6 incidents started during the event without naming Vercel or another vendor. Some are part of it, some are a normal day’s background (about 3 in these hours).

Show all 6

Detected automatically from 10 status pages opening incidents in the peak hour (normally at most 6). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.