Copilot Coding Agent Degraded Job Completion
Summary
From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%. <br /><br />We identified the issue as an infrastructure change that wrongly marked the majority of API backends in a single region as unhealthy. As a result, requests routed to those backends failed before reaching the application layer. <br /><br />To prevent this from happeni
Impact
major
Timeline
[investigating] We are investigating reports of impacted performance for some GitHub services.
via statuspage[investigating] We are aware of degraded REST API availability and are investigating
via statuspage[investigating] API Requests is experiencing degraded performance. We are continuing to investigate.
via statuspage[investigating] We are continuing to investigate an issue causing approximately 35% of REST API requests to fail. Based on our current understanding, requests are not consistently reaching the application layer, resulting in failed requests returning HTML responses instead of the expected API response format. We are actively investigating the issue and will provide another update as soon as more information is available.
via statuspage[monitoring] The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
via statuspage[monitoring] As of 23:46 UTC, the REST API service is reachable and responding to requests normally.
via statuspage[resolved] This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
via statuspage[resolved] From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%. <br /><br />We identified the issue as an infrastructure change that wrongly marked the majority of API backends in a single region as unhealthy. As a result, requests routed to those backends failed before reaching the application layer. <br /><br />To prevent this from happening again, we're improving our systems to catch this kind of invalid configuration before it reaches production. We'll also audit the related systems to make them more resilient to future changes, and we're increasing our monitoring sensitivity so we're alerted to problems like this sooner.
via statuspageLessons Learned
⚠GitHub has experienced 114 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, api, routing have occurred 866 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: Network / Routing, API Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Networking in BLR1
DigitalOcean · Jul 19, 2026
Service is operating normally: [RESOLVED] Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Some users are unable to access Codex
OpenAI · Jul 18, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 18, 2026