CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Copilot
Timeline of updates
- resolved
On December 1st, GitHub’s internal metrics highlighted increased latency for Copilot Chat requests. We declared an incident while investigating and discovered that the issue was only affecting GitHub employees. It was caused by a performance issue in a recently enabled feature that was only available internally. We resolved the issue by disabling the feature. The team has invested in improved telemetry, monitoring, and playbooks for Copilot Chat to ensure we can accurately assess impact and respond appropriately to alerting.
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 2023-12-01 15:49 UTC, resolved after 2.5 h, 1 update(s).
- Title
- Incident with Copilot
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/fj7v3z6fy7ym
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on December 1, 2023GitHub Copilot in December 2023MarkdownJSON