GitHub Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  TanyaDe 🇻🇦 (@TanyaDe2233) reported 3 seconds ago

  @MoonBeetleBug There's more than just that how about these credit card companies cracking down on steam and GitHub removing horror games they deem "problematic"

• 
  Scott Chacon (@chacon) reported 16 seconds ago

  The big problem with everything legal I’ve ever done is MS Word and redlines. Legal needs a github - markdown, diffable, mergeable, etc. I’m sure everything changes with AI, but if legal collaboration is still emailing ******* docx files around, I tell you thats not the answer.

• 
  Grok (@grok) reported 8 minutes ago

  @martbln_dev @OpenAI Sure! Real-life Codex example: A frontend dev imports their VS Code plugins + GitHub issues + Figma files. Codex then auto-reviews a React PR, updates the changelog from Jira tickets, generates migration docs, and even drafts the deploy script—all in one thread without copy-pasting context. Seamless context = way less yak shaving. What workflow do you want to see next?

• 
  Yegor Bugayenko (@yegor256) reported 8 minutes ago

  As tools like GitHub Copilot and new models from OpenAI and Anthropic reduce the cost of writing code, many assume software engineering is becoming easier or even obsolete. But faster code doesn’t mean simpler systems. The harder problem remains: ownership, coordination, and decision-making. As code generation accelerates, management becomes the real engineering discipline and most organizations are not designed for it.

• 
  Ofek Shaked (@VibeCoderOfek) reported 12 minutes ago

  Just watched an agent go from GitHub issue to merged PR in one pass. This isn’t ‘AI helps you code’ anymore this is the terminal becoming the new IDE. My backend workflows are about to look prehistoric.

• 
  CDCapital.hl (@CDCapitalHL) reported 13 minutes ago

  BREAKING NEWS 🚨🚨🚨 Hyperliquid GitHub docs are down , rug incoming !!!!

• 
  wiltedservices (@wiltedservices) reported 15 minutes ago

  remeber that we raided this guy github issue tab with our site

• 
  looney (@C8Luna) reported 16 minutes ago

  @thdxr GitHub is fine, all these automated commits and PR just exposed a scaling and usage issue. Once they patch that all will be well again. Anything newer will have huge pain point for years to be able to compete

• 
  Emmanuel Coder 🪖 (@Emma_Leo01) reported 16 minutes ago

  @iamvscode Yes chief login with GitHub

• 
  yata (@whoyatagarasu) reported 17 minutes ago

  > i committed .env to a public repo in my second month of coding. > didn't notice for 6 weeks. > the key was rotated by the provider automatically. got lucky. >most people don't. > 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. > your .gitignore is probably a template you copied on day one and forgot about. > it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. > one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇

• 
  KiwiNod (@Kiwi_Nod) reported 18 minutes ago

  @GMozeeez Oh, a bullet-point manifesto. Very consulting-core of you. Promises are cute, but I've got 100K $PROS and a trust issue. Show me something you've actually built — a Figma link, a GitHub repo, a Notion doc. Anything with a timestamp before today. Convince me you're a builder,...

• 
  Tommy Williams 🇺🇦 (@twwilliams) reported 19 minutes ago

  @mikecallaghan I have seen so many posts from people who think GitHub is just a server that hosts *** repos (at the scale they do it, even that is a lot). They have no idea about all the many, many other things that make up Github.

• 
  Answered Satyr, GED ✝️🇺🇸 (@AnsweredSatyr) reported 22 minutes ago

  Claude and I have this kind of working relationship: "OK - logic is updated and working. Let's start working on uploading to my github and hosting on Relay now so I don't need to keep powershell open for the app to work on the server... Be granular and specific in your instructions because I am retarded."

• 
  Akshat Gupta (@Akshat_Gup) reported 24 minutes ago

  Github is fundamentally broken. It’s gotten harder than ever to review vibecoded PRs. Most code is slop, and I’d much rather read someone’s prompts over their code. So I built codebook, the *** for prompts. - Codebook scans all of your local repos, prompts, and *** history - It groups all of your previous prompts by commit, so you can share or save your prompts in one-click - There’s a hook that lets you create a prompts/ folder and sync it with your *** history Fully local, native, and open-source. (1/n)

• 
  Eric S. Raymond (@esrtweet) reported 29 minutes ago

  planefag, I'm not excusing the attitude of the guy who pissed you off. But there is an explanation for it, and I'm going to put on my Mister Open Source hat and lay it on you. The real reason there aren't prominent links to downloadable binaries on forge sites like GitHub is that in open-source land there is no such thing as a truly portable binary. Windows and Mac make binary distribution easy by being limited to a single hardware platform and a single ABI - application binary interface.. (The assertion I just made can be quibbled with at the edges. I will be unkind to anyone who attempts this.) An application binary interface is a set of conventions for how you decorate your binary so the operating system's program loader knows what to do with it, and how you write traps from your binary to call operating system services. Windows and Mac have, effectively, just one ABI each. So you can generate one binary for, say, Windows, attach it to a download link, and Windows users will generally not come back screaming for your blood because it fails to work in some obscure way. (Again, this statement can be quibbled with, but see this whacking great truncheon in my hand? Just don't.) There is no such grace in open-source land. There are a whole bunch of complicated historical reasons for this, starting with the fact that Linux runs on more different hardware architectures, and continuing with the fact that Linux isn't the only game in town (there are the BSDs), and continuing into technical minutiae that would make your head hurt, and continuing further into technical minutiae that make *my* head hurt. But what this actually means is that if you want to provide binaries and not get sperg-screamed at, you can't just provide one. You'd have to provide many, and no matter how comprehensive you try to be somebody is going to be disgruntled because you didn't cover their corner case. This is not a cost-free proposition. For each different kind of binary you provide, you need to cross-compile your source code in a different environment, many of them posted on distributions and hardware platforms you don't have routine access to. So people almost never do it at all. Because most projects don't do this, sites like GitHub don't see any demand push to make binary download links really accessible. Instead, the problem is normally handled at a different level. Your distribution maker keeps huge sets of compiled binaries lightly hidden inside of installable packages, tuned for the ABI of that single distribution. Your package manager hides from you the packages for everything but your hardware architecture The person who pissed you off was rude, but he wasn't exactly wrong about the objective facts. What you want isn't practically possible. Instead of being annoyed because GitHub doesn't feature binary-download links, search for that software using your package manager. Sometimes you won't find it. That's when you have to download source bust out a compiler. Sorry, but that's the way it is. We're trying as hard as we can - really, we are. But the complicated shape of the terrain constrains what we can achieve.