GitHub Availability Dips in May 2026

GitHub details nine service disruptions in May 2026, highlighting ongoing infrastructure upgrades and lessons learned from major incidents.

Abstract digital representation of GitHub platform status and data flow
An overview of GitHub's platform performance and infrastructure updates for May 2026.· Github Blog
Visual TL;DR
New Users ServiceEffect
From the article 5 mentionsA new users service is handling double previous traffic at a lower cost, and stateless authentication tokens are rolling out to reduce database load during peak times.
Stateless TokensContext
From the articleA new users service is handling double previous traffic at a lower cost, and stateless authentication tokens are rolling out to reduce database load during peak times.
Schema Migration IncidentDriver
From the article 2 mentionsA critical incident on May 4th, lasting over an hour, was triggered by a routine online schema migration on a high-traffic database table.
May 2026 DisruptionsDriver
From the articleGitHub reported nine service disruptions in May 2026, leading to degraded performance across its platform.
Infrastructure UpgradesDriver
ongoing investments aimed at enhancing reliability and preventing failures
From the articleThese incidents occurred as the company continues significant infrastructure investments aimed at enhancing reliability.
Azure MigrationCore
migrating services to Azure, 40% monolith & 30% Git traffic now on Azure
From the article 5 mentionsThe company is actively migrating services to Azure and breaking down its monolithic architecture into isolated components.
Monolith DecompositionContext
breaking down monolithic architecture into isolated components
From the articleAs of May, 40% of monolith traffic and 30% of Git traffic now run on Azure, with repository replication at 99%.
Service IsolationContext
separating user, auth, and authz domains prevents cascading failures
From the article 4 mentionsA new users service is handling double previous traffic at a lower cost, and stateless authentication tokens are rolling out to reduce database load during peak times.
Improved ReliabilityEffect
aiming to prevent single points of failure and enhance stability
From the article 3 mentionsGitHub is committed to improving reliability, prioritizing availability over new features.

GitHub reported nine service disruptions in May 2026, leading to degraded performance across its platform. These incidents occurred as the company continues significant infrastructure investments aimed at enhancing reliability.

The company is actively migrating services to Azure and breaking down its monolithic architecture into isolated components. This strategy aims to prevent single points of failure. As of May, 40% of monolith traffic and 30% of Git traffic now run on Azure, with repository replication at 99%.

Significant progress has been made in isolating the primary database cluster. Separating user, authentication, and authorization domains prevents cascading failures. A new users service is handling double previous traffic at a lower cost, and stateless authentication tokens are rolling out to reduce database load during peak times.

A critical incident on May 4th, lasting over an hour, was triggered by a routine online schema migration on a high-traffic database table. The combined load saturated database connections, causing query contention and widespread timeouts affecting pull requests, issues, actions, and Git operations. Dependent services like Codespaces, Packages, and Copilot also experienced degraded performance.

The incident was detected quickly, and the migration was paused, leading to recovery. Mitigation took approximately 33 minutes, with full resolution following 30 minutes later. As a result, GitHub is implementing stricter controls for database migrations, including dynamic throttling and automated circuit breakers.

GitHub Actions faced degradation on May 5th and 6th due to issues with hosted runners in the East US region. The May 5th incident, impacting 13.5% of standard runner jobs, was caused by a scale-up operation hitting an internal rate limit. Remediation efforts for this incident inadvertently introduced a configuration error that led to the May 6th degradation, affecting 17.1% of standard runner jobs.

GitHub is committed to improving reliability, prioritizing availability over new features. The company acknowledges ongoing work is needed but emphasizes its dedication to ensuring GitHub is consistently available.

Gartner Recognition

This focus on reliability comes as GitHub was recognized as a Leader in the Gartner Magic Quadrant for AI Code Assistants for the second consecutive year.

© 2026 StartupHub.ai. All rights reserved. You may not republish this article in full without a license. Search engines and AI research tools may crawl and summarize for reference. Bulk reproduction or model training requires a license. See our terms.
Daniel Singer

Written by

Daniel Singer

Editor, StartupHub.ai

Daniel Singer is the editor of StartupHub.ai, a technology expert and thought leader on AI and its applications across sectors, from fintech and healthcare to developer tooling and consumer software. He writes and tests the tools covered here thoroughly and regularly, and built StartupHub.ai to give founders, operators and buyers a clearer read on what they are actually being sold.