Minor impactResolvedDevOps

GitHub incident: Disruption with Copilot next edit suggestions

GitHub reported this minor-impact incident on its official status page on Jun 17, 2026, 17:57 UTC. It was resolved after 1h 31m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jun 17, 2026, 17:57 UTC
started
Jun 17, 2026, 19:28 UTC
resolved
1h 31m
duration
Minor
impact
  1. resolvedJun 17, 2026, 19:28 UTC

    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.We mitigated the incident by deploying a corrected configuration change at 18:55 UTC, with full recovery observed at 19:14 UTC.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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on Jun 17, 2026: Disruption with Copilot next edit suggestions · APIStatus.watch