GitHub availability report: July 2026

GitHub’s availability report acknowledges an unacceptable prolonged GitHub Actions outage on August 6 and outlines an accelerated effort to migrate Actions and broader production workloads from GitHub data centers to Azure, aiming to improve isolation, capacity, and regional resilience. In July, GitHub increased Azure Central US handling of monolith read traffic to a peak of 52.75%, raised Git traffic there to 47%, expanded repository replication, moved authentication and repository-content functions to more dedicated infrastructure, reduced database and authorization load, and added workflow-focused reliability monitoring and stronger production-change controls. The report also describes eight July incidents, including a seven-hour multi-service outage caused by an unsafe infrastructure metadata update, Actions runner-provisioning delays from overloaded data replication, MCP web-search failures from an upstream provider outage, DNS degradation caused by incomplete control-plane data, runner connection failures from an expired certificate, rejected SSH RSA and deploy-key authentication after a regression, failed pull-request creation following a database schema workflow cancellation, and two Actions disruptions involving Redis regional health and capacity changes. GitHub says it has implemented or is pursuing safeguards such as immutable configuration, staged rollouts, improved monitoring, automation, validation, recovery tooling, certificate management, and redundant capacity, with targets of moving 70% of reads and 30% of writes to Central US this quarter and removing dotcom production traffic from its data centers by the end of 2026.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.