We are seeing elevated errors with Next Edit Suggestions and Completions

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 25m it lasted.

  Anything that failed between 2026-06-23 23:04 UTC and 2026-06-23 23:29 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 4

1. investigatingJun 23, 2026, 11:04 PM UTC

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

   provider

2. investigatingJun 23, 2026, 11:26 PM UTC

   We have applied a rollback and are seeing recovery.

   provider

3. monitoringJun 23, 2026, 11:27 PM UTC

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

   provider

4. resolvedJun 23, 2026, 11:29 PM UTC

   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.

   provider

Corrections

None so far.

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