GitHub Availability Report: July 2026

GitHub is conducting a root cause analysis of the GitHub Actions outage that occurred on August 6, and the findings will be included in the August availability report to be released in September. To prevent recurrence and enhance scalability, GitHub is also accelerating the migration of GitHub Actions to Azure.

In this outage, the fact that core Actions services remained in self-managed data centers contributed to capacity shortages and delayed recovery. While most Actions executions are processed on Azure, the launch service connecting the monolith and Actions had not yet been migrated, causing cascading failures. GitHub plans to move this service to Azure to secure capacity to absorb surging loads.

In July, progress was made in expanding independent Azure-based capacity and reducing reliance on shared infrastructure.

• Monolith read traffic processed in Azure Central US increased to 52.75% by July 28.
• The share of Git traffic within Azure rose from 43% in June to 47%.
• 29% of all repositories secured a second replica in Central US.
• Stability verification procedures began to be applied to every major traffic expansion effort.

Some authentication tables were migrated from the existing shared database to dedicated infrastructure. Dedicated user services are distributing over 1 million queries per second at peak, and 80% of critical permission lookups are processed via isolated service paths.

Repository content traffic is being fully processed on dedicated infrastructure in Central US. The dedicated pull request service achieved 99.87% parity with the monolith even for authenticated read requests, and is gradually migrating all traffic.

Performance improvements continued. Total query time for the artifacts table was halved by a single production change, and caching in the Git authorization path reduced authentication service load by 18.2% despite increasing request volumes. Search workloads are currently all processed in Central US, and additional capacity has been secured.

GitHub plans to measure the health of key customer workflows such as pull requests, in addition to infrastructure status, to detect signs of outages earlier. High-risk manual operational tasks are being replaced with automation, review procedures, and operational safeguards to reduce reliance on human error.