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
Changes to GitHub Copilot Individual plans
We’re making these changes to ensure a reliable and predictable experience for existing customers.
Bringing more transparency to GitHub’s status page
Changes to the status page will provide more specific data, so you’ll have better insight into the overall health of the platform.
Developer policy update: Intermediary liability, copyright, and transparency
We’re sharing recent policy updates that developers should know about, updating our Transparency Center with the full year of 2025 data, and looking to what’s ahead.