GitHub Availability Report: May 2026 Performance Summary

🔑 Enhanced Key Takeaways

•GitHub's infrastructure is under significant pressure from rapidly growing traffic, largely driven by AI-assisted and agentic development workflows, which has necessitated a major infrastructure transformation.
•The company is actively migrating its infrastructure to Azure for elastic capacity, breaking down its monolithic architecture into isolated services, and isolating its primary database cluster to eliminate shared failure points.
•Specific incidents in May 2026 included GitHub Actions degradations caused by an incorrectly suspended service account, elevated latency on github.com due to a routine online schema migration, and issues with hosted runners stemming from configuration problems introduced during remediation work.
•GitHub has experienced a notable decline in reliability, with 257 incidents, including 48 major outages, tracked between May 2025 and April 2026, with GitHub Actions being the most frequently affected service.
•GitHub has acknowledged systemic architectural weaknesses, such as insufficient isolation between components and inadequate backpressure mechanisms, which have allowed localized failures to cascade across the platform.

📊 Competitor Analysis▸ Show

Platform	Availability SLA	Service Credits	Notes
GitHub	>= 99.9% for key services	Not explicitly mentioned for general availability, but post-incident reviews are published.	Focuses on transparency through monthly availability reports.
GitLab	99.9% for Ultimate customers on GitLab.com and GitLab Dedicated	Yes, for Ultimate customers if availability falls below 99.9% (for SaaS purchased/renewed after 2026-01-01).	SLA covers core platform services like Issues, Merge Requests, Git Operations, Container/Package Registry, and API Requests.
Bitbucket	99.9% for Premium plans, 99.95% for Enterprise plans	Yes, financially backed for Premium and Enterprise plan customers if availability drops below the guaranteed threshold.	Covers core features like pull request creation/viewing, Git transactions (HTTPS/SSH), and Pipeline starts (cloud-hosted runners).

🛠️ Technical Deep Dive

GitHub is undergoing an infrastructure transformation, including a migration to Azure for elastic capacity.
The platform is being re-architected from a monolith into isolated services to reduce shared failure points.
Key components like the primary database cluster are being isolated, with user, authentication, and authorization services being split into independent domains.
A new users service is fully operational, handling double the traffic at a lower database cost.
Stateless authentication tokens are being rolled out to reduce per-request database lookups, which can amplify pressure during traffic spikes.
GitHub utilizes MySQL, scaled with Vitess for horizontal and vertical sharding, to manage its database operations.
The company is implementing improvements such as decoupling critical services, enhancing load-shedding capabilities, and improving traffic management to bolster reliability.
GitHub's infrastructure is globally distributed, employing Points of Presence (POPs) for latency reduction, isolated data centers with redundancy, and mechanisms for failover and disaster recovery.
Incident response follows a structured process including preparation, detection and analysis, containment and eradication, recovery and restoration, and post-incident analysis.

🔮 Future ImplicationsAI analysis grounded in cited sources

GitHub will likely continue to experience intermittent service degradations as its infrastructure transformation progresses.

The ongoing migration to Azure and the decomposition of its monolith are complex, large-scale changes that inherently carry risks of new issues arising during the transition, as evidenced by incidents caused by remediation work.

The increasing reliance on AI-driven development workflows will necessitate further significant investments in GitHub's underlying infrastructure capacity and resilience.

GitHub explicitly states that rapidly growing traffic, largely from AI-assisted workflows, is a primary driver of current reliability challenges and is pushing them to transform their infrastructure.

GitHub's incident reporting and transparency will become even more critical for user trust and platform adoption.

With a history of increasing incidents and public developer frustration, transparent communication about outages and ongoing reliability efforts is essential to maintain confidence in the platform.

⏳ Timeline

2020-07

GitHub introduced its monthly Availability Report for transparency on service performance.

2023

GitHub experienced 94 total incidents, including 22 major and 72 minor outages.

2024

GitHub experienced 119 service incidents, including 26 major and 93 minor disruptions.

2025-05

Beginning of a period (May 2025 - April 2026) where GitHub tracked 257 incidents, with 48 major outages.

2026-02-09

GitHub experienced a major outage affecting most services, including GitHub.com, API, Git over HTTPS, Actions, and Copilot.

2026-04

GitHub overhauled its status page, adding a 'Degraded Performance' tier, and Mitchell Hashimoto moved his Ghostty project off GitHub due to reliability concerns.

GitHub Availability Report: May 2026 Performance Summary

⚡ 30-Second TL;DR

Key Points

🧠 Deep Insight

🔑 Enhanced Key Takeaways

🛠️ Technical Deep Dive

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline

📎 Sources (15)

👉Related Updates