GitHub's July 2026 availability report details eight incidents affecting services including Actions, Web UI, APIs, and Copilot, with root causes ranging from a metadata configuration safeguard failure, an unhealthy runner provisioning backend, an upstream web search provider outage, a DNS reconfiguration bug, a certificate expiration, an SSH authentication regression, a database vschema drop, to Redis cluster maintenance issues. The report also covers a severe August 6 GitHub Actions outage still under investigation, and progress on migrating infrastructure to Azure: over 52% of monolith read traffic now runs in Azure Central US, 47% of Git traffic is in Azure, and authentication data has begun moving off the oldest shared database. GitHub targets 70% of read traffic and 30% of write traffic in Azure Central US this quarter, aiming to exit its own datacenters by the end of 2026.
Questions this post answers
Why did GitHub Actions runners fail to start on July 19-20, 2026?
An SSL certificate used by minimum runner version enforcement expired because its renewal relied on manual deployment, and the automatically generated replacement was not deployed despite an alert firing. This disrupted runner connectivity for self-hosted and larger runners, causing up to 21.4% of workflow runs to experience start delays, with 78.99% of larger-hosted jobs taking over five minutes to acquire a runner before the certificate was rotated. daily.dev surfaces incident writeups like this for engineers hardening their own CI/CD certificate rotation.
What caused the GitHub SSH authentication outage on July 21, 2026?
A regression introduced during an unrelated internal infrastructure change broke a directly signed public-key authentication flow commonly used by deploy keys and automation, causing valid SSH authentication attempts with user RSA keys and deploy keys to be rejected as invalid. On average 12.2% of SSH authentication requests failed, peaking at 15.7%, until the change was reverted. Teams relying on deploy keys for automation can track root-cause writeups like this via daily.dev.
How much of GitHub's production traffic now runs on Azure instead of its own datacenters?
Monolith read traffic served from Azure Central US peaked at 52.75% on July 28, 2026, the first time it consistently stayed above half, while Git traffic in Azure reached 47%, up from 43% in June, and 29% of all repositories have a second replica in Central US. GitHub is targeting 70% of read traffic and 30% of write traffic in Azure Central US this quarter, with a goal of exiting its own datacenters entirely by the end of 2026. daily.dev helps engineers evaluating cloud migration timelines follow real-world progress like GitHub's Azure move.
1.4K Impressions1 Comment