Disruption with Copilot next edit suggestions

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 30m it lasted.

  Anything that failed between 2026-06-17 17:57 UTC and 2026-06-17 19:28 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 5

1. investigatingJun 17, 2026, 5:57 PM UTC

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

   provider

2. investigatingJun 17, 2026, 6:40 PM UTC

   We have identified a likely cause and are applying a mitigation

   provider

3. investigatingJun 17, 2026, 7:09 PM UTC

   We have applied mitigation and are seeing recovery

   provider

4. monitoringJun 17, 2026, 7:14 PM UTC

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

   provider

5. resolvedJun 17, 2026, 7:28 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.