rewindex

RewindexOutage eventsAug 12, 2026

GitHub outage, Aug 12, 2026

5 linked vendors posted 4 incidents between and . 5 vendors named GitHub in 4 incidents (5 of them blamed it). GitHub posted “Incident with Pull Requests and Issues” at 16:16 UTC. 4 other vendors had incidents in the same window; nothing links them to GitHub (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when GitHub posted ().

  1. GitHub posted
Named GitHubNamed another vendor or depends on oneEach 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: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

GitHubposted 16:16 UTCWithin an hour2 vendors, 2 blamed GitHubBolt.new, CircleCILater3 vendors, 3 blamed GitHubHashiCorp, Terraform Cloud (HCP), Socket
GitHubposted 16:16 UTCWithin an hour2 vendors, 2 blamed GitHubBolt.new, CircleCILater3 vendors, 3 blamed GitHubHashiCorp, Terraform Cloud(HCP), Socket
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 16:16 UTC"]:::root
  h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>Bolt.new, CircleCI"]:::blames
  root --> h1
  later["Later<br/>3 vendors, 3 blamed GitHub<br/>HashiCorp, Terraform Cloud (HCP), Socket"]:::blames
  root --> later

Vendors that named GitHub

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

Within an hour

2 vendors

  • +5 min

    Blames GitHub

    Incident, no impact listed

    Bolt.new[Dependency Check] GitHub

    …[Dependency Check] GitHub This incident has been resolved. This incident has been resolved. Upstream Provider has reported an outage…

  • +17 min

    Blames GitHub

    Minor incident

    CircleCIGitHub service degradation may impact customers using GitHub

    …GitHub service degradation may impact customers using GitHub The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/i…

Later

2 vendors

Also happening at the same time (not linked)

4 incidents from 4 vendors started in this window without naming GitHub or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 32 incidents in these hours).

Show all 4

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