Menu

📰
0

GitHub availability report: February 2026

The GitHub Blog·@JakubOleksy·2 months ago
#KRGwck
Reading 0:00
15s threshold

In February, we experienced six incidents that resulted in degraded performance across GitHub services. We recognize the impact these outages have had on teams, workflows, and overall confidence in our platform. Earlier today, we released a blog post outlining the root causes of recent incidents and the steps GitHub is taking to make our systems more resilient moving forward. Thank you for your patience as we work through near-term and long-term investments we’re making. Below, we go over the six major incidents specific to February. **February 02 17:41 UTC (lasting 1 hour and 5 minutes)** From January 31, 2026, 00:30 UTC, to February 2, 2026, 18:00 UTC, Dependabot service was degraded and failed to create 10% of automated pull requests. This was due to a cluster failover that connected to a read-only database. We mitigated the incident by pausing Dependabot queues until traffic was properly routed to healthy clusters. All failed jobs were identified and restarted.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More