GitHub: Incident With Copilot
Timeline of updates
- resolved
On June 6, 2025, an update to mitigate a previous incident led to automated scaling of database infrastructure used by Copilot Coding Agent. The clients of the service were not implemented to automatically handle an extra partition. Hence it was unable to retrieve data across partitions, resulting in unexpected 404 errors. As a result, approximately 17% of coding sessions displayed an incorrect final state - such as sessions appearing in-progress when they were actually completed. Additionally, some Copilot-authored pull requests were missing timeline events indicating task completion. Importantly, this did not affect Copilot Coding Agent’s ability to finish code tasks and submit pull requests. To prevent similar issues in the future we are taking steps to improve our systems and monitoring.
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: none) posted by GitHub, started 2025-06-06 23:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Incident With Copilot
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/5g8smlrj5ynp
GitHub profileRecent GitHub incidentsAll outages on June 6, 2025GitHub in June 2025MarkdownJSON