GitHub outage on 8 November 2026
GitHub: our direct checks failed for 40 min from 11:06 UTC; the official status page showed a problem 16 min later.
Measured from one checker location: Vigil's server at Hetzner in Falkenstein, Germany, with no second region to confirm it. A failure seen from Germany is strong evidence of a problem, not proof that every user was affected.
10:41–11:01 UTC · 20 min
- What we checked
- GitHub's REST API root (api.github.com)
- First failed check
- 08 Nov 2026, 10:41 UTC
- First passing check after it
- 08 Nov 2026, 11:01 UTC
- Failed checks in a row
- 4
- Error we recorded
- HTTP 503
- Official status page
- Already showed a problem at 08 Nov 2026, 10:36 UTC, 5 min before our first failed check ("Increase in timeouts for some unauthenticated users"): the vendor was first. Their status page keeps the incident history.
11:06–11:46 UTC · 40 min
- What we checked
- GitHub's REST API root (api.github.com)
- First failed check
- 08 Nov 2026, 11:06 UTC
- First passing check after it
- 08 Nov 2026, 11:46 UTC
- Failed checks in a row
- 8
- Error we recorded
- HTTP 504
- Official status page
- First showed minor issues at 08 Nov 2026, 11:21 UTC: 16 min after our first failed check ("Partially Degraded Service"). From our 5-minute polls of the status page (±5 min). Their status page keeps the incident history.
How this was measured
Every 5 minutes Vigil makes one HTTPS request to GitHub directly and, separately, reads GitHub's official status page. An episode is 2 or more failed direct checks in a row; it is published only when fewer than 3 other services failed at the same moment (otherwise the problem was probably on our side). Times are accurate to about 5 minutes. Full rules and the 90-day table: methodology. Live status: is GitHub down?
Share: