GitHub: Incident with Git Operations
Timeline of updates
- resolved
On May 8, 2025, between 14:40 UTC and 16:27 UTC the Git Operations service was degraded causing some pushes and merges to fail. On average, the error rate was 1.4% with a peak error rate of 2.24%. This was due to a configuration change which unexpectedly led a critical service to shut down on a subset of hosts that store repository data. We mitigated the incident by re-deploying the affected service to restore its functionality. In order to prevent similar incidents from happening again, we identified the cause that triggered this behavior and mitigated it for future deployments. Additionally, to reduce time to detection we will improve monitoring of the impacted service.
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 2025-05-08 15:20 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Incident with Git Operations
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/42gtccf6dd98
GitHub profileRecent GitHub incidentsAll outages on May 8, 2025GitHub in May 2025MarkdownJSON