We are seeing elevated errors with Next Edit Suggestions and Completions

lowGitHubJun 23, 2026 23:04Duration: 25m
authenticationconfiguration
Configuration ErrorAuthentication Issue

Summary

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

Impact

minor

Timeline

Jun 23, 2026 23:04

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

via statuspage
+22m
Jun 23, 2026 23:26

[investigating] We have applied a rollback and are seeing recovery.

via statuspage
+1m
Jun 23, 2026 23:27

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

via statuspage
+2m
Jun 23, 2026 23:29

[resolved] 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.

via statuspage

Lessons Learned

GitHub has experienced 114 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to authentication, configuration have occurred 158 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: Configuration Error, Authentication Issue. Consider implementing preventive measures specific to this failure category.