GitHub: Disruption with some GitHub services
Timeline of updates
- resolved
Between 01:36 and 08:11 UTC on Thursday March 12, GitHub.com experienced elevated error rates across Git operations, web requests, and related services. During a planned infrastructure upgrade, a configuration issue caused newly provisioned Kubernetes nodes to run an incompatible version of etcd, which disrupted cluster consensus across several production clusters. This led to intermittent 5XX errors on git push, git clone, and page loads. Deployments were paused for the duration of the incident. Once the incompatible nodes were identified, they were removed and cluster consensus was restored. A validation deploy confirmed all systems were healthy before normal operations resumed. To prevent recurrence, we are adding programmatic enforcement of version compatibility during node replacements, implementing monitoring to detect split-brain conditions earlier, and updating our recovery tooling to reduce restoration time.
From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2026-03-12 01:54 UTC, resolved after 51 min, 1 update(s).
- Title
- Disruption with some GitHub services
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/lw6j95nyw3py
GitHub profileRecent GitHub incidentsAll outages on March 12, 2026GitHub in March 2026MarkdownJSON