--- title: GitHub availability report: July 2026 | daily.dev description: GitHub's July 2026 availability report details eight incidents affecting services including Actions, Web UI, APIs, and Copilot, with root causes ranging from a... canonical: https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GitHub availability report: July 2026 | daily.dev og:description: GitHub's July 2026 availability report details eight incidents affecting services including Actions, Web UI, APIs, and Copilot, with root causes ranging from a... og:url: https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3 og:image: https://api.daily.dev/og/posts/jlSbK76S3.png og:image:alt: GitHub availability report: July 2026 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # GitHub availability report: July 2026 **[GitHub Blog](https://daily.dev/sources/ghblog)** · 15 min read · 0 upvotes · 1 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did GitHub Actions have a major outage in July 2026 related to runner acquisition? An unhealthy backend data service responsible for provisioning GitHub-hosted runners caused delayed and failed job starts for 9 hours 18 minutes on July 9, 2026. The highest-volume runner shard became overloaded and could not synchronize reliably across regions, leaving about 8% of workflow runs delayed over 5 minutes and 2% failing to start before backend replication health was restored. _Teams debugging flaky CI runner starts can follow GitHub Actions incident patterns like this on daily.dev._ ### What caused the SSH authentication failures on github.com in July 2026? A regression introduced during an unrelated internal infrastructure change broke a less common public-key authentication flow, the directly signed method commonly used by deploy keys and automation, causing valid RSA and deploy key authentications to be rejected as invalid. The issue lasted from 07:41 to 11:57 UTC on July 21, 2026, with SSH failure rates averaging 12.2% and peaking at 15.7%, and was fixed by reverting the change. _Engineers relying on SSH deploy keys for automation can track root causes of auth regressions like this via daily.dev._ ### How much of GitHub's production traffic has moved from its own datacenters to Azure as of July 2026? Monolith read traffic served from Azure Central US peaked at 52.75% on July 28, 2026, marking the first time it consistently stayed above half. Git traffic in Azure reached 47%, up from 43% in June, and 29% of all repositories had a second replica in Central US. GitHub targeted 70% of read traffic and 30% of write traffic in Central US for the following quarter, aiming to exit its own datacenters entirely by the end of CY2026. _Teams planning cloud migrations can benchmark timelines against GitHub's Azure transition progress on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 0 upvotes > The mix of root causes is a good reminder that availability work is rarely one big fix. The Azure migration numbers are encouraging, but moving auth and write traffic will be the real test. Publishing incident detail at this level makes the tradeoffs much easier to trust. ## Similar posts on daily.dev - [GitHub availability report: June 2026](https://daily.dev/posts/github-availability-report-june-2026-yjcjq42au) · GitHub Blog · 0 upvotes · 0 comments - [GitHub availability report: March 2026](https://daily.dev/posts/github-availability-report-march-2026-c2dt15scg) · GitHub Blog · 0 upvotes · 0 comments - [GitHub appears to be struggling with one nine availability](https://daily.dev/posts/github-appears-to-be-struggling-with-one-nine-availability-d4tedw2tw) · The Register · 0 upvotes · 0 comments - [What’s gone wrong at GitHub?](https://daily.dev/posts/what-s-gone-wrong-at-github--5f7pmzqel) · LeadDev · 210 upvotes · 19 comments --- Tags: [#github](https://daily.dev/tags/github), [#azure](https://daily.dev/tags/azure), [#github-actions](https://daily.dev/tags/github-actions) [View this post on daily.dev](https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"GitHub availability report: July 2026","url":"https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3"},"datePublished":"2026-08-12T22:22:27.131Z","dateModified":"2026-09-13T18:55:26.733Z","description":"GitHub's July 2026 availability report details eight incidents affecting services including Actions, Web UI, APIs, and Copilot, with root causes ranging from a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ac176b293f6d2d89e4c0c7c28c95693b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ac176b293f6d2d89e4c0c7c28c95693b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/106cf162b88840808484d4b5429b59b1","url":"https://daily.dev/sources/ghblog"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"github,azure,github-actions","timeRequired":"PT15M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Blog","item":"https://daily.dev/sources/ghblog"},{"@type":"ListItem","position":3,"name":"GitHub availability report: July 2026"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3","comment":[{"@type":"Comment","text":"The mix of root causes is a good reminder that availability work is rarely one big fix. The Azure migration numbers are encouraging, but moving auth and write traffic will be the real test. Publishing incident detail at this level makes the tradeoffs much easier to trust.","datePublished":"2026-08-13T02:36:41.629Z","url":"https://daily.dev/posts/jlSbK76S3#c-IoPa4C1La","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3#faq","mainEntity":[{"@type":"Question","name":"Why did GitHub Actions have a major outage in July 2026 related to runner acquisition?","acceptedAnswer":{"@type":"Answer","text":"An unhealthy backend data service responsible for provisioning GitHub-hosted runners caused delayed and failed job starts for 9 hours 18 minutes on July 9, 2026. The highest-volume runner shard became overloaded and could not synchronize reliably across regions, leaving about 8% of workflow runs delayed over 5 minutes and 2% failing to start before backend replication health was restored. Teams debugging flaky CI runner starts can follow GitHub Actions incident patterns like this on daily.dev."}},{"@type":"Question","name":"What caused the SSH authentication failures on github.com in July 2026?","acceptedAnswer":{"@type":"Answer","text":"A regression introduced during an unrelated internal infrastructure change broke a less common public-key authentication flow, the directly signed method commonly used by deploy keys and automation, causing valid RSA and deploy key authentications to be rejected as invalid. The issue lasted from 07:41 to 11:57 UTC on July 21, 2026, with SSH failure rates averaging 12.2% and peaking at 15.7%, and was fixed by reverting the change. Engineers relying on SSH deploy keys for automation can track root causes of auth regressions like this via daily.dev."}},{"@type":"Question","name":"How much of GitHub's production traffic has moved from its own datacenters to Azure as of July 2026?","acceptedAnswer":{"@type":"Answer","text":"Monolith read traffic served from Azure Central US peaked at 52.75% on July 28, 2026, marking the first time it consistently stayed above half. Git traffic in Azure reached 47%, up from 43% in June, and 29% of all repositories had a second replica in Central US. GitHub targeted 70% of read traffic and 30% of write traffic in Central US for the following quarter, aiming to exit its own datacenters entirely by the end of CY2026. Teams planning cloud migrations can benchmark timelines against GitHub's Azure transition progress on daily.dev."}}]} ```