- Level
- confirmed
- Worst impact
- Degraded
- Components
- Git Operations
- Regions
- us
- Down Index
- 24of 100
What to do
Check whether you use GitHub Git Operations in us. 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 3h 8m it lasted.
Anything that failed between 2026-03-18 22:36 UTC and 2026-03-19 01:44 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 8
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.
provider
- investigating
We are continuing to investigate degraded performance for git operations from the US West Coast.
provider
- investigating
We continue to investigate degraded performance for git operations from the US West Coast.
provider
- investigating
We continue to investigate the slow performance of Git Operations affecting the US West Coast.
provider
- investigating
We are seeing recovery in git operations for customers on the West Coast of the US.
provider
- resolved
On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues. This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7
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-0691bb39ef
Is GitHub still down?
No, this incident was resolved 2026-03-19 01:44 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
3h 8m, from 2026-03-18 22:36 UTC to 2026-03-19 01:44 UTC, by the times GitHub posted.
What was affected?
GitHub named Git Operations in us.
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.