--- title: GitHub keeps falling over, but nobody's actually leaving description: Recurring GitHub outages have reignited debate over whether developers should migrate to alternatives like GitLab, Codeberg, Gitea, or sourcehut. Gergely Orosz... canonical: https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GitHub keeps falling over, but nobody's actually leaving | daily.dev og:description: Recurring GitHub outages have reignited debate over whether developers should migrate to alternatives like GitLab, Codeberg, Gitea, or sourcehut. Gergely Orosz... og:url: https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe og:image: https://api.daily.dev/og/posts/OpTsgAFwe.png og:image:alt: GitHub keeps falling over, but nobody's actually leaving 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 keeps falling over, but nobody's actually leaving **[Trends](https://daily.dev/sources/trends)** · 1 min read · 1 upvotes · 0 comments ## Summary Recurring GitHub outages have reignited debate over whether developers should migrate to alternatives like GitLab, Codeberg, Gitea, or sourcehut. Gergely Orosz argues GitHub's reliability problems stem from years-old architectural decisions with no quick fix. Most developers admit annoyance but say switching is impractical: corporate teams are locked in by Actions and tooling investment, while individuals stay due to network effects and discoverability. Some run mirrored repos on alternative hosts while keeping GitHub as the public face. One take frames the outages as exposing a deeper shift: GitHub's real value was always its social layer, not git hosting itself, and that layer is eroding as AI-generated pull requests replace human interaction, with no decentralized replacement yet being built. ## Content GitHub went down again on August 17, nearly eight hours this time, and the discourse split into two camps almost immediately: people demanding answers, and people saying the answer was obvious months ago. The official story: a critical infrastructure component in a Central US data center couldn't scale under a new traffic peak. CTO Vlad Fedorov's postmortem points to a genuinely wild number, monthly commits jumped from 1.4 billion in April to 2.9 billion now, alongside 130 million merged PRs and 24 million new repos a month. GitHub's response has been to throw hardware at it: 3 million new CPU cores, 120 petabytes of storage, and shifting 58% of platform load to Azure, up from just 12% in May. Their own data centers are reportedly maxed out on power.

Nobody's buying ## Questions this post answers ### Why did GitHub go down on August 17 for almost eight hours? A critical infrastructure component in a Central US data center failed to scale under a new traffic peak. CTO Vlad Fedorov's postmortem attributes this to explosive growth: monthly commits rose from 1.4 billion in April to 2.9 billion, alongside 130 million merged pull requests and 24 million new repositories created per month, overwhelming existing capacity. _Teams tracking platform reliability risks like GitHub's outages can follow the fallout on daily.dev._ ### How much of GitHub's infrastructure now runs on Azure instead of its own data centers? 58% of platform load now runs on Azure, up sharply from just 12% in May. This shift comes as GitHub's own data centers are reportedly maxed out on power capacity, alongside additions of 3 million new CPU cores and 120 petabytes of storage to handle surging commit and repository growth. _Engineers weighing infrastructure dependencies can follow how GitHub's Azure migration unfolds on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 0 discussions (as of 2026-09-13). **TL;DR:** No discussion data was provided, so this reflects only the post's own framing of repeated GitHub outages and reliability concerns. **Sentiment:** 0% positive · 0% mixed · 100% skeptical --- Tags: [#github](https://daily.dev/tags/github), [#git](https://daily.dev/tags/git), [#gitlab](https://daily.dev/tags/gitlab) [View this post on daily.dev](https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe) ```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 keeps falling over, but nobody's actually leaving","url":"https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe"},"datePublished":"2026-08-17T18:28:42.141Z","dateModified":"2026-09-13T19:26:33.630Z","description":"Recurring GitHub outages have reignited debate over whether developers should migrate to alternatives like GitLab, Codeberg, Gitea, or sourcehut. Gergely Orosz...","isAccessibleForFree":true,"articleSection":"Trends","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":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,git,gitlab","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"GitHub keeps falling over, but nobody's actually leaving"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/github-keeps-falling-over-but-nobody-s-actually-leaving-optsgafwe#faq","mainEntity":[{"@type":"Question","name":"Why did GitHub go down on August 17 for almost eight hours?","acceptedAnswer":{"@type":"Answer","text":"A critical infrastructure component in a Central US data center failed to scale under a new traffic peak. CTO Vlad Fedorov's postmortem attributes this to explosive growth: monthly commits rose from 1.4 billion in April to 2.9 billion, alongside 130 million merged pull requests and 24 million new repositories created per month, overwhelming existing capacity. Teams tracking platform reliability risks like GitHub's outages can follow the fallout on daily.dev."}},{"@type":"Question","name":"How much of GitHub's infrastructure now runs on Azure instead of its own data centers?","acceptedAnswer":{"@type":"Answer","text":"58% of platform load now runs on Azure, up sharply from just 12% in May. This shift comes as GitHub's own data centers are reportedly maxed out on power capacity, alongside additions of 3 million new CPU cores and 120 petabytes of storage to handle surging commit and repository growth. Engineers weighing infrastructure dependencies can follow how GitHub's Azure migration unfolds on daily.dev."}}]} ```