GitHub Copilot incident

Disruption with Copilot next edit suggestions

Minor Resolved Upstream link ↗

Started

June 17, 2026 at 05:57 PM UTC

Duration

1h 30m

Resolved

June 17, 2026 at 07:28 PM UTC

Updates timeline

  1. Investigating

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

  2. Investigating

    We have identified a likely cause and are applying a mitigation

  3. Investigating

    We have applied mitigation and are seeing recovery

  4. Monitoring

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

  5. Resolved

    On June 17, 2026, between 16:57 UTC and 19:14 UTC, Copilot code completions were degraded and users were unable to receive Next Edit Suggestions. Standard ghost text code completions were not affected. This was due to a configuration change that caused the service's routing layer to incorrectly discard all Next Edit Suggestion model endpoints as invalid.<br /><br />We mitigated the incident by deploying a corrected configuration change at 18:55 UTC, with full recovery observed at 19:14 UTC.<br /><br />We are working to improve the resilience of our routing layer to limit impact due to a subset of invalid configurations, and to improve our alerting to detect sudden traffic changes that are not captured by standard error rate monitors.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader