CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Copilot
Timeline of updates
- resolved
On February 23, 2026, between 14:45 UTC and 16:19 UTC, the Copilot service was degraded for Claude Haiku 4.5 model. On average, 6% of the requests to this model failed due to an issue with an upstream provider. During this period, automated model degradation notifications directed affected users to alternative models. No other models were impacted. The upstream provider identified and resolved the issue on their end. We are working to improve automatic model failover mechanisms to reduce our time to mitigation of issues like this one 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: minor) posted by GitHub Copilot, started 2026-02-23 14:56 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Incident with Copilot
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/h8z3w9ycj0pm
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on February 23, 2026GitHub Copilot in February 2026MarkdownJSON