Degraded REST API Availability

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%. 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. 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.

Update

As of 23:46 UTC, the REST API service is reachable and responding to requests normally.

Update

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

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.

Investigating

API Requests is experiencing degraded performance. We are continuing to investigate.

Investigating

We are aware of degraded REST API availability and are investigating

Investigating

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