rewindex

RewindexOutage eventsAug 17, 2026

GitHub outage, Aug 17, 2026

11 linked vendors posted 10 incidents between and . 11 vendors named GitHub in 10 incidents (11 of them blamed it). GitHub posted “Incident with GitHub.com” at 13:40 UTC. 12 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 ().

    13. 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 13:40 UTCWithin an hour6 vendors, 6 blamed GitHubBolt.new, Mintlify, CircleCI, Pulumi +21 to 4 hours later4 vendors, 4 blamed GitHubSnyk, dbt Labs, Docker, ClickHouse CloudLater1 vendor, 1 blamed GitHubRetool
GitHubposted 13:40 UTCWithin an hour6 vendors, 6 blamed GitHubBolt.new, Mintlify, CircleCI,Pulumi +21 to 4 hours later4 vendors, 4 blamed GitHubSnyk, dbt Labs, Docker,ClickHouse CloudLater1 vendor, 1 blamed GitHubRetool
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 13:40 UTC"]:::root
  h1["Within an hour<br/>6 vendors, 6 blamed GitHub<br/>Bolt.new, Mintlify, CircleCI, Pulumi +2"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed GitHub<br/>Snyk, dbt Labs, Docker, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed GitHub<br/>Retool"]:::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

5 vendors

  • +6 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…

  • +8 min

    Blames GitHub

    Minor incident

    MintlifyGitHub outage impacting Mintlify dashboard

    …GitHub outage impacting Mintlify dashboard The github incident has been resolved Automatic updates and previews are delayed due to API request failures from a github outage https://www.githubstatus.co…

  • +24 min

    Blames GitHub

    Major incident

    CircleCIGitHub Incidents impacting CircleCI functionality

    …GitHub Incidents impacting CircleCI functionality GitHub's APIs appear to be operating normally. GitHub API error rates and latencies appear to have recovered. We will continue to monitor. GitHub has…

  • +25 min

    Blames GitHub

    Incident, no impact listed

    PulumiGitHub services failing

    …GitHub services failing This incident has been resolved. GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable. https://www.githubsta…

  • +54 min

    Blames GitHub

    Major incident

    Cursorand xAIGitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase

    …GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service…

1 to 4 hours later

4 vendors

  • +1 h 22 min

    Blames GitHub

    Minor incident

    SnykGitHub Integration Degradation

    …GitHub Integration Degradation Snyk engineers have confirmed service recovery. The incident is now resolved. Snyk engineers have confirmed service recovery. The incident is now resolved. Snyk is curre…

  • +1 h 23 min

    Blames GitHub

    Major incident

    dbt LabsGit Failures in dbt Platform

    …ioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.…

  • +1 h 41 min

    Blames GitHub

    Major incident

    DockerIssues building DHI customizations

    …Issues building DHI customizations GitHub outage is over and the customizations are going through. Due to a 3rd party vendor's outage, we're having issues building DHI customizations. We'll keep monit…

  • +1 h 44 min

    Blames GitHub

    Minor incident

    ClickHouse CloudProvisioning of new CDC pipes for Postgres might be delayed or failing

    …We identified an issue where new CDC ClickPipes can't be provisioned due to dependency on GitHub availability (https://www.githubstatus.com/incidents/zkxwbgr0cnmx). Team is monitoring the issue and tr…

Later

1 vendor

  • +4 h 53 min

    Blames GitHub

    Minor incident

    RetoolSource Control Degradation due to Github Outage

    …Source Control Degradation due to Github Outage Github has resolved their incident. An upstream incident with Github (https://www.githubstatus.com/incidents/zkxwbgr0cnmx) is causing issues with source…

Also happening at the same time (not linked)

12 incidents from 12 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 31 incidents in these hours).

Show all 10

Detected automatically from 9 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.