CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Pull Requests
Timeline of updates
- resolved
On June 10, 2025, between 14:28 UTC and 14:45 UTC the pull request service experienced a period of degraded performance, resulting in merge error rates exceeding 1%. The root cause was an overloaded host in our Git infrastructure. We mitigated the incident by removing this host from the actual set of valid replicas until the host was healthy again. We are working to improve the various mechanisms that are in place in our existing infrastructure to protect us from such problems, and we will be revisiting why in this particular scenario they didn't protect us as expected.
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: minor) posted by GitHub Copilot, started 2025-06-10 14:28 UTC, resolved after 18 min, 1 update(s).
- Title
- Incident with Pull Requests
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/5n51wd9mnkz0
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on June 10, 2025GitHub Copilot in June 2025MarkdownJSON