GitHub Copilot incident

We are seeing elevated errors with Next Edit Suggestions and Completions

Minor Resolved Upstream link ↗

Started

June 23, 2026 at 11:04 PM UTC

Duration

24 min

Resolved

June 23, 2026 at 11:29 PM UTC

Updates timeline

  1. Investigating

    We are investigating reports of impacted performance for some GitHub services.

  2. Investigating

    We have applied a rollback and are seeing recovery.

  3. Monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. Resolved

    On June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions. During this window, affected users may have seen failed or missing code completions and Next Edit Suggestions. On average about 25% of Completions and Next Edit Suggestions requests failed during the impact window, peaking at roughly 27%. The cause was a configuration change that prevented the Copilot service from obtaining the authentication tokens it needs to reach its model backends; this both failed requests directly and caused the service to temporarily remove backends from rotation. GitHub engineers detected the elevated error rate within minutes, declared an incident, and mitigated the issue at 23:22 UTC by redeploying the service with a known-good configuration, which restored normal operation. As a follow-up, the team disabled the affected authentication path to prevent a future deployment from re-introducing the problem, and is making the change rollout safer. We apologize for the disruption and are taking steps to reduce the likelihood of similar incidents.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader