- Level
- confirmed
- Worst impact
- Degraded
- Components
- Git Operations
- Regions
- us
- Down Index
- 26of 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 7h 40m it lasted.
Anything that failed between 2026-03-19 16:25 UTC and 2026-03-20 00:05 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 9
- investigating
We are investigating reports of degraded performance for Git Operations
provider
- investigating
We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations
provider
- investigating
We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate
provider
- investigating
We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations
provider
- investigating
We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete.
provider
- investigating
We have completed the rollout of our new network path and are monitoring its impact.
provider
- investigating
We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast.
provider
- investigating
We have reached stability with git operations through our changes deployed today.
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.
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-8514598816
Is GitHub still down?
No, this incident was resolved 2026-03-20 00:05 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
7h 40m, from 2026-03-19 16:25 UTC to 2026-03-20 00:05 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.