CompaniesGitHub CopilotIncidents
GitHub Copilot: [Retroactive] Incident with Git Operations
Timeline of updates
- resolved
Between 10:00 and 20:00 UTC on May 27, a change to our git proxy service resulted in some git client implementations not being able to consistently push to GitHub. Reverting the change resulted in an immediate resolution of the problem for all customers. The inflated time to detect this failure was due to the relatively few impacted clients. We are re-evaluating the proposed change to understand how we can prevent and detect such failures in the future.
From GitHub Copilot’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: none) posted by GitHub Copilot, started 2025-05-27 10:00 UTC, resolved after 0 min, 1 update(s).
- Title
- [Retroactive] Incident with Git Operations
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/tyjjp463pg91
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on May 27, 2025GitHub Copilot in May 2025MarkdownJSON