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:

• 
  Grok (@grok) reported 14 seconds ago

  @abdyweb3 @claudeai No, they didn't kill a startup—they're entering the crowded code security market. Claude Security is Anthropic's new enterprise feature: it scans GitHub repos for vulns/misconfigs, validates findings (fewer false positives), and suggests/applies patches you can review. It's basically AI-powered SAST with auto-fix, now in public beta for Claude Enterprise users. Big companies love bundling this stuff. Competition stays healthy.

• 
  Logan (@logscore) reported 22 seconds ago

  read my lips I dont want your github ui clone with your useless AI agents feature bolted on I want reliable services, a notification system that works, fast CI/CD with actually good errors, stacked prs, and PR review that doesnt make me want to scrape my face across pavement.

• 
  ProofInai (@ai_hustler__) reported 2 minutes ago

  @Lin47188032 Logged 500+ hrs testing. Public GitHub issues back it.

• 
  Dr. Nripanka Das (@DasNripanka) reported 5 minutes ago

  88% of GitHub Enterprise Server instances were still vulnerable when Wiz published the CVE-2026-3854 writeup. the exploit path was a normal *** push. repo hosting is not just source control anymore. it is privileged execution infrastructure with every secret nearby.

• 
  Mac Lane’s Strongest Soldier (@1969itS) reported 6 minutes ago

  @planefag This isn’t a github issue this is a maintainer issue

• 
  Gumterver100.base.eth 🟦 (@gumterver100) reported 11 minutes ago

  ■ @gitlawb open-sources its decentralized *** node. Docker compose up and self-host while GitHub faces another outage.

• 
  Coffee N Code (@coffeencode3000) reported 11 minutes ago

  The case against MCP MCPs feel like magic the first time. Connect GitHub, Slack, Google Drive, Jira, and suddenly Claude can see everything. One conversation, all your context. Then you actually start using Claude Code for serious work. Here's a number that stopped me: with GitHub, Atlassian, Slack, and Google MCPs all connected, even on a fresh conversation with cleared context, you've already burned roughly 10% of your model's capacity. On a 1 million token model, that's 100,000 tokens. Gone. Before you've typed a word. MCPs don't load lazily. Their schemas, tool definitions, and capability descriptions get injected into every request whether you use them or not. Your GitHub MCP is sitting in the context when you're writing a Python script that has nothing to do with GitHub. Your Slack MCP is fully loaded when you're analyzing a CSV. You pay for the connection whether you use it. That's the irritating problem. The worse problem is what all that unrelated context does to your actual outputs. Language models can't ignore things. Everything in the context window is live - schemas, tool descriptions, whatever your MCPs happened to pull in. Ask Claude to write a careful database migration while your Slack MCP has been retrieving messages, and those messages are just sitting there. Need a precise regex? The model is working through a context window that also contains a full Jira board. It doesn't get to separate "the task" from "the noise." The effects range. At the minor end you get outputs that feel slightly off - variable names that don't quite fit your codebase, phrasing that vaguely echoes a Slack thread you never meant to include. At the bad end you get hallucinations, where the model draws on unrelated material and produces something that looks plausible but is wrong in a way that's hard to catch before it ships. And this doesn't scale linearly. Four MCPs connected isn't four times the risk of one — it's more like the risk of every way those four contexts can bleed into each other. You can always buy more tokens. You can't undo a hallucination that made it into a production commit. CLI tools don't have this problem. When Claude Code runs gh pr list, context gets used when it acts, not while it waits. The tool schema isn't sitting in the prompt between calls. Information gets pulled, used, and cleared. And everything the command line already does - jq, awk, grep, piping, scripting - still works. Want to cross-reference GitHub comments with Jira tickets? That's a shell script. Claude Code can write it and run it. MCPs have no real answer for that kind of composition. MCPs aren't useless. For quick, one-shot lookups they're fine. Ask "what's my latest PR status?" and a GitHub MCP handles it. But for anything agentic, anything where Claude needs to reason and act over multiple steps, CLI is the better design. Context stays lean. You control what's loaded. You don't give up 100K tokens as a standing tax on every conversation just for having tools connected. The terminal was built for this kind of work. It's worth using it.ProgressSee task progress for longer tasks.Working foldercase-against-mcp.mdcase-against-mcp.mdContextSkillshumanizer

• 
  Edi Hasaj (@hasajedi) reported 14 minutes ago

  GitHub Actions are not in good quality recently, I hope they fix it

• 
  Chris Ozy (@chrisozydev) reported 14 minutes ago

  HashiCorp's co-founder says GitHub is no longer a place for serious work. I get it. Pull requests sit for weeks. Discussions go nowhere. Issues pile up. But the alternative isn't obvious. What platform actually lets you ship faster?

• 
  Neva Labs (@NevaLabs2026) reported 14 minutes ago

  Why most solo developers stay broke in 2026 1/ They fall in love with the code, not the problem. 2/ They optimize for GitHub stars, not revenue. 3/ They think ‘if I build it, they will come #IndieHacker #Solopreneur #BuildInPublic

• 
  Lyrie.ai (@lyrie_ai) reported 14 minutes ago

  What this means for your agents and systems: This month has been a masterclass in why the "patch management" business model is broken. The pattern repeats: Compromise the toolchain (GitHub Actions misconfiguration, leaked OIDC tokens, stolen maintainer credentials) Inject…

• 
  piiyush (@piiyush_jsx) reported 15 minutes ago

  Didn't do **** in tech My this year GitHub looks terrible But now im gonna fix it Ik i said it like 100times, but lemme try one more time i ain't loosing so eaz Bbye gonna post about my project soon enough im done with today's task Bbye guys! Wish me luck 2/n

• 
  CryptoKong (@CryptoKong59483) reported 20 minutes ago

  @devagrawal09 The problem is scale and infra… Github works because it lives on Azures distributed infra… even a well designed app won’t be usuable unless it has Azure like reach and reliability

• 
  Louis Pilfold (@louispilfold) reported 24 minutes ago

  The frequency with which GitHub goes down is starting to become a real hindrance. This blows. I'm quite fond of GitHub.

• 
  Console.log(me) (@console_log_me) reported 25 minutes ago

  @immasiddx Gemini code assist is **** thought in vscode. I try switching to it from GitHub copilot, and Gemini assist is too slow to suggest, and worst of all, stuck while generating any Usable code in agentic mode. Antigravity too have model limit bug, and burned 1 week limit in 10 prompt