← Back to GitHub History
major✓ Resolved
Degraded REST API Availability
Status
resolved
Duration
1h 23m
Updates
7
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
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.
monitoring
As of 23:46 UTC, the REST API service is reachable and responding to requests normally.
monitoring
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.
📊 TECHNICAL DETAILS
Internal ID
598cff42-8f1f-4ba3-a6dc-dbe5a1d66d51
External ID
gxycch3076xk
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
1h 23m
Total Duration
7
Status Updates
Affected Components
API Requests
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed