GitHub Status · History · Incident #4736

RESOLVED

Disruption with Copilot next edit suggestions

Minor · Started Jun 17, 2026 · 5:57 PM

  • Duration

    1h 30m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

Disruption with Copilot next edit suggestions

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.


  • Started

    Jun 17, 2026 · 5:57 PM

  • Resolved

    Jun 17, 2026 · 7:28 PM

  • Duration

    1h 30m

  • Severity

    Minor

Event timeline

How this incident unfolded

  • Investigating

    Jun 17 · 5:57 PM GitHub

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

  • Investigating

    Jun 17 · 6:40 PM GitHub

    We have identified a likely cause and are applying a mitigation

  • Investigating

    Jun 17 · 7:09 PM GitHub

    We have applied mitigation and are seeing recovery

  • Monitoring

    Jun 17 · 7:14 PM GitHub

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

  • Resolved

    Jun 17 · 7:28 PM GitHub

    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.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free