What happened
GitHub.com experienced multiple service interruptions in recent weeks. These were separate incidents, but they shared a root cause: new challenges in scaling our database tier. Specifically, increased load on our largest database cluster contributed to degradation across several services.
We understand that reliability is critical to your projects and teams, and we apologize for the disruption.
Next steps
We have multiple data partitioning initiatives already in progress, and will be rolling out some of this work in the near future. In the coming weeks, we will publish a more detailed technical report covering these events and the work we are doing to improve the scalability and performance of our backend systems.
For real-time updates on system availability, follow our status page.
