- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API Requests, Issues, Pull Requests, Actions, Pages, Copilot
- Down Index
- 48of 100
What to do
Check whether you use GitHub Pages API Requests, Issues, Pull Requests, Actions and 2 more. 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 19m it lasted.
Anything that failed between 2026-07-24 16:17 UTC and 2026-07-24 17:36 UTC may need a replay.Subscribe to GitHub Pages's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-pages works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Pages 12
- investigating
We are investigating reports of degraded performance for API Requests and Issues
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We are investigating timeouts to some GitHub services
provider
- investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
We have applied a mitigation and are monitoring for recovery
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability.
provider
- investigating
We are seeing recovery across all services
provider
- resolved
On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ. Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors: - Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts. - 27% of GitHub issues interactions saw slow requests or timeouts. - 4% of GitHub Copilot requests experienced errors, though most automatically retry. - 4% of git push operations saw impacts during the affected window. - Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases. We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36. This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.
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-6f1ae2cbb5
Is GitHub Pages still down?
No, this incident was resolved 2026-07-24 17:36 UTC. For GitHub Pages's live state, see https://down.guide/github-pages.
How long did it last?
1h 19m, from 2026-07-24 16:17 UTC to 2026-07-24 17:36 UTC, by the times GitHub Pages posted.
What was affected?
GitHub Pages named API Requests, Issues, Pull Requests, Actions and 2 more.
What caused it?
GitHub Pages hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Pages's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.