About This Week’s Availability
It hasn’t exactly been a good week for GitHub’s nines. Just under an hour of total downtime over the past week comes to 99.46% uptime – far below our standards.…
It hasn’t exactly been a good week for GitHub’s nines. Just under an hour of total downtime over the past week comes to 99.46% uptime – far below our standards.
As you can imagine, it’s been a frustrating week for us too. We’ve been fighting a Distributed Denial of Service (DDoS) Attack since Saturday. The quality of the GitHub experience has been impacted by this DDoS and I wanted to take a second to apologize for that and tell you what we’re doing to fix it.
This attack is global, and has been very intense at times. Yesterday morning, for example, github.com suddenly received requests from 10,000 times the number of clients it had handled the minute before.
Our Ops team is working around the clock together with our hosting and network providers to deflect the impact of this attack while keeping GitHub fast and available for you, our awesome GitHub users. For the times we’ve been unable to stop the attack from taking us down, we sincerely do apologize.
We’re better protected against DDoS attacks now than we’ve ever been before and plan to make next week a better week.
Written by
Related posts
What’s coming to our GitHub Actions 2026 security roadmap
A look at GitHub Actions’ 2026 roadmap, outlining how secure defaults, policy controls, and CI/CD observability harden the software supply chain end to end.
Updates to GitHub Copilot interaction data usage policy
From April 24 onward, interaction data—specifically inputs, outputs, code snippets, and associated context—from Copilot Free, Pro, and Pro+ users will be used to train and improve our AI models unless they opt out.
GitHub availability report: February 2026
In February, we experienced six incidents that resulted in degraded performance across GitHub services.