- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API Requests
- Down Index
- 30of 100
What to do
Check whether you use GitHub API Requests. 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 1h 23m it lasted.
Anything that failed between 2026-07-16 22:51 UTC and 2026-07-17 00:14 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 7
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
We are aware of degraded REST API availability and are investigating
provider
- investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
provider
- 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.
provider
- monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
As of 23:46 UTC, the REST API service is reachable and responding to requests normally.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7fedec6c32
Is GitHub still down?
No, this incident was resolved 2026-07-17 00:14 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 23m, from 2026-07-16 22:51 UTC to 2026-07-17 00:14 UTC, by the times GitHub posted.
What was affected?
GitHub named API Requests.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.