Rewindex

RewindexOutage eventsMay 9, 2023

GitHub outage, May 9, 2023

5 vendors posted 4 incidents between 11:00 and 23:00 UTC, against about 30 incidents from 20 vendors in the same hours on an ordinary week. 2 vendors named GitHub in 1 incidents (2 of them blamed it). GitHub posted “Incident with Pull Requests” at 08:07 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 GitHub posted (08:07).

    25. GitHub posted 08:07
Named GitHubNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

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

Swipe sideways to see the whole diagram.

GitHubposted 08:07 UTC1 to 4 hours later2 vendors, 2 blamed GitHubv0, Vercel
GitHubposted 08:07 UTC1 to 4 hours later2 vendors, 2 blamed GitHubv0, Vercel
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["GitHub<br/>posted 08:07 UTC"]:::root
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed GitHub<br/>v0, Vercel"]:::blames
  root --> h4

Vendors that named GitHub

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

1 to 4 hours later

1 vendor

Same window, did not name anyone

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

Show all 3

Detected automatically from 6 status pages opening incidents in the peak hour (normally at most 5). 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.