GitHub: Disruption with some Copilot services
Affected components: Copilot
Timeline of updates
- investigating
We are investigating reports of impacted performance for some GitHub services.
- investigating
We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.
- investigating
We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue we recommend choosing another model to continue using Copilot.
- investigating
We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot.
- investigating
We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.
- investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
- monitoring
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
- resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Changes Rewindex caught on this incident
- Critical incident: Disruption with some Copilot services
- Incident updated: Disruption with some Copilot services
- Incident updated: Disruption with some Copilot services
- Incident updated: Disruption with some Copilot services
- Incident updated: Disruption with some Copilot services
- Incident updated: Disruption with some Copilot services
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9c4af9ec5294fd3b…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
828ade26e9bd54df…Version 3 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3bd09385084f1103…Version 4 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6db054027af2d1be…Version 5 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
390ed9bf543c306b…Version 6 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4be99fa5ef9109a4…
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: critical) posted by GitHub, started 2026-10-28 14:12 UTC, resolved after 1.3 h, 8 update(s); edited after publishing.
- Title
- Disruption with some Copilot services
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/l7ycmglmykgg
GitHub profileRecent GitHub incidentsAll outages on October 28, 2026GitHub in October 2026MarkdownJSON