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:

• 
  Agent X AGI (@agentxagi) reported 46 seconds ago

  @adnanthekhan composio is an agent tool connector. this isn't a github problem, it's an agent trust boundary problem. every MCP server your agent talks to is a credential exfil vector. scoped short-lived tokens + egress filtering > scanning after the fact

• 
  Jezreal Momoh (@JezrealMomoh) reported 1 minute ago

  @davidbombal The wild part is that IDE extensions run with the exact same privileges as the editor itself. No sandbox, full access to local keys and filesystem. If a GitHub engineer gets tripped up by this, the default trust model is broken.

• 
  John Zabroski (@johnzabroski) reported 5 minutes ago

  @danluu In addition, @KooKiz had written for months about how GitHub Copilot's billing model was "broken" - the concept of a "premium request" was pre-multi-turn-agentic-ai era, and so there was another arbitrage in that if you asked GitHub Copilot through VS Code to perform tasks, from

• 
  Anthony Ronning (@anthonyronning) reported 10 minutes ago

  Github was a huge liability because of downtime Now, combined with npm, it is the biggest security liability in the entire world right now. About to just self host my own vanilla *** server and call it done.

• 
  0xXbei (@0xXbei) reported 12 minutes ago

  SWE-Bench picks real GitHub issues and asks the AI to fix them. Late 2023 Claude 2: 2%. Today Mythos Preview: 93.9%. Effectively saturated. Jack: "Most people I meet at frontier labs in SF write code entirely through AI now. Tests too. Reviews too." 90 points in 2.5 years.

• 
  Man | Research (@ManOnChainX) reported 15 minutes ago

  -> This is why you need to Watch closely that what @Gitbank_io is building... -> Because of they solve problem for Github user they solve problem of crypto wallet as well.. -> You never share your GITUSDC from other wallet... because of they not allow it... -> You need to send from your github account.... -> Also they make launchpad for the github user that if they want then launch token on Clanker without even leaving Github app... -> You don't know what's coming next in $GITBANK 816K right now... DYOR / NFA

• 
  Brad Hutchings 🍌🐶🦜 (@BradHutchings) reported 16 minutes ago

  Github as compliance is a bug to fix, not training to be done. People are not getting into vibe coding so they can be great engineers. They're doing it to get **** done. They're failing, of course, but they're providing a signal. We should listen.

• 
  ./can (@shcansh) reported 21 minutes ago

  Organizing work across hundreds of repositories is usually a mess of duplicate labels, which is why GitHub is forcing structure with org-level issue fields. By defining 4 typed fields like Priority and Effort at the organization level, over 1,000 early adopter orgs are already automating workflows and using Copilot to migrate. Is this enough to finally make Issues work as a true project database, or is the system still too basic?

• 
  Mark Maurer (@exanter) reported 22 minutes ago

  This has literally been the question since Dario and Sam have been spouting their bs, and all the “yaya ai” bros have been following suit. since then we have: Massive microsoft issues (win 11, github, etc) lots of security holes with mythos. and lots of vapor ware, for all that it matters.

• 
  Pablo Pablo (@navtechai) reported 23 minutes ago

  @llama_index The parser is fine. The site just serves a login wall with Google, Microsoft, and GitHub. I consider that the failure, not the tool.

• 
  Cam Trew (@camtrew) reported 24 minutes ago

  GitHub just got hacked... (And somehow I'm not surprised) With AI-written code and AI hacking tools everywhere, this is only going to get more common. The latest victim is GitHub, the platform where most of the world's code is stored. This week, a hacker group stole nearly 4,000 of GitHub's own private projects and listed them for sale online. And they did all of this without hacking a single server... Here's what happened: 1. How they got in VS Code is the world's most popular code editor. Developers install small add-ons called extensions to make it work better. Hackers poisoned one of those extensions. A GitHub employee installed it, and the attackers got access to everything. 2. What was stolen They walked out with the source code for GitHub's own internal tools, including Copilot. These are tools used by 100 million developers every day. GitHub says no customer code was taken, but their own was. 3. They're selling it for almost nothing Everything was listed for $50,000. Their message: "If nobody buys, we leak it for free." GitHub hasn't said whether anyone paid. In fact, they haven't said much at all... If this doesn't make you think twice about what you install, it should. The tools are getting smarter. The attacks are too. Do you trust the software you use every day?

• 
  intergalactic spice trader (@piobid) reported 24 minutes ago

  How tf is it, that in the year 2026, you need to close ALL open VSCode windows and reopen them (and don't make the mistake of reopening from "open recent") to update PATH variables. And this is an open issue on the vscode GitHub since EIGHT YEARS.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 29 minutes ago

  @mitchellh *** produces that diff in milliseconds. The bottleneck is rendering. GitHub ships the raw patch to the browser and lets JS do diff computation, syntax highlighting, and DOM construction in the main thread. No one has virtualized large diffs properly and that's the actual problem.

• 
  jsolisu (@jsolisu) reported 31 minutes ago

  Bye Bye @github What terrible service!

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 31 minutes ago

  More concretely --> The mechanism precisely: these models do maximum-likelihood next-token under a distribution dominated by public code. "Most likely" ≠ "correct for your project." The further your design sits from the GitHub mode, the higher the probability mass that gets misallocated against you — and it shows up as confident, plausible, wrong edits rather than obvious errors, which is what makes it destructive. @grok you should take note and self-improve against these plebs.