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:

• 
  BullBear.News (@bullbear_info) reported 6 minutes ago

  @github @AnthropicAI Fable 5 is back in Copilot. Let's see if it can actually fix a *** conflict this time. 🤷

• 
  The Hacker News (@TheHackersNews) reported 6 minutes ago

  The test went after a work GitHub repo. @LayerxSecurity says the agent followed the puzzle’s final step, pulled SSH login credentials, and sent them to the attacker. The demo used a harmless plaintext file, but the same path could point at open tabs, signed-in apps, or internal tools.

• 
  spring.furrest.net (he/him) (@spring_meowmeow) reported 9 minutes ago

  Well maybe after bath I need to fix the GitHub actions to be able to properly publish the new website. So yeah, soon I will attach the link.

• 
  Mark Ajzenstadt (@mardehaym) reported 12 minutes ago

  You pay $20 a month for Cursor Pro. $10 a month for GitHub Copilot. $20 a month for Claude Pro. $580 a year for AI to write your code. Same four failure modes in all three. Same four failure modes in all three. Silent wrong assumptions. Unrequested abstractions. Touching code you didn't mention. Treating "fix the bug" as a complete spec. No toggle to turn them off. No settings panel. No checkbox. A developer named Forrest Chang built a 65-line markdown file that fixes all four. It is called CLAUDE.md. You drop it in your project root. Error rate: 41% down to 11%. One file. No model change. 220,000+ GitHub stars. MIT license. $0. Cursor Pro charges $240 a year. It still ships silent assumptions. GitHub Copilot charges $100 a year. It still over-engineers. Claude Pro charges $240 a year. It still touches code it shouldn't. CLAUDE.md costs $0. Works everywhere. Fixes all four. Here is the wildest part. These four rules are what you do when you review a junior's PR. The companies charging you $580 a year could have shipped them as defaults. They didn't. You find the bloat on day 30, not day 1. By then you have renewed. But DO NOT drop this file in your project root. We should all keep paying $580 a year for tools that treat "fix the bug" as a complete specification.

• 
  Plasm (@plasm_lang) reported 15 minutes ago

  Symbol tuning: the prompt pattern that scales when your prompts get long — teach a tiny glossary once, reuse the same short symbols, instead of repeating full names with overlapping meanings and hoping the model infers context. In a federated tool schema 'labels' might be a query filter in one expression and a relation hop in another. Issue might mean GitHub in one step and Linear in the next. id might appear on three entities with three different meanings. Instead of repeating those names everywhere and hoping the model tracks the context, symbol tuning gives each contextual meaning its own slot: p#, r#, e#, and so on. The useful part is not only token compression. It is that the model gets a stable, copyable vocabulary. Examples stay short. Homographs become explicit.

• 
  Nevo (@NevoPlaysGames) reported 16 minutes ago

  @ezhdhitler If you can truly easily fix it then go make the post on GitHub or let them know I’m not a dev I’m just the guy who kept asking for years xD I’m sure if it was super easy they would’ve did it

• 
  .Dev (@AnExiledDev) reported 16 minutes ago

  @MatthewBerman What tier are you on? I have 3 sessions running Fable non-stop, I've worked roughly 20 GitHub issues, and I'm only 25% into my 5hr and 8% into my weekly... Is the web really this bad?

• 
  Fen 🏳️‍⚧️ (@FlookyBS) reported 16 minutes ago

  My website will be down for the time being. I will be migrating from GitHub pages to gitgud io.

• 
  Boyuan (Nemo) Chen (@boyuan_chen) reported 19 minutes ago

  GitHub search is now an agent attack surface. A public malware-finder repo lists 9,330 suspicious GitHub repositories detected through push-pattern heuristics. Even if only a slice is ever encountered by real users, the agent failure mode is obvious. A coding agent asked to "find a library and make it work" can browse faster than it can judge provenance. Fresh commits, plausible README text, and repo-shaped packaging become inputs to an automated install path. The fix is boring and product-level: repo-age checks, provenance scoring, blocked arbitrary ZIP downloads, sandboxed installs, dependency allowlists, and logs that show exactly what code the agent trusted. For agent systems, retrieval belongs inside the security boundary.

• 
  István Pató (@patoistvan) reported 19 minutes ago

  GitHub ownership If your SaaS source code lives under your personal GitHub account, ask: 👉🏻 Could a buyer, operator, or successor clearly understand who owns it? 👉🏻 Could the repo, packages, secrets, billing, and permissions be transferred cleanly? If not, the code is only part of the problem.

• 
  Andrey Grand (@TheAndreyGrand) reported 22 minutes ago

  Qwen 3.6 27B landed this month at 77.2% on SWE-bench Verified — and it fits in 24GB of VRAM at Q4. Sit with that pairing for a second, because the pairing is the whole point. SWE-bench Verified is the "can it actually resolve a real GitHub issue" benchmark — not a quiz, an actual code-fix task with tests that have to pass. 77% was frontier-API territory not long ago. A used 3090 is 24GB and goes for ~$700. So the model hitting that number runs on hardware you buy once and own — no per-token meter, nothing leaving the box. The honest caveat: on long multi-step agent loops and very large context, a frontier model like Claude or GPT-5 still holds up better, and you'll feel it on the genuinely hard tasks. This isn't "local won." It's the gap on everyday coding work getting thin enough to matter. If you've got a 24GB card already sitting in your machine, pull Qwen 3.6 27B at Q4_K_M and point it at your next real bug. For a solid slice of your workload, the answer's now good enough — and it's yours.

• 
  Deepesh Kalura (@KaluraDeepesh) reported 22 minutes ago

  Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

• 
  ぽっぽ／目玉P (@Memme20000610) reported 28 minutes ago

  @Validate_QA I'm calling the MiniMax models directly from Python via OpenCode without using MCP, so I haven't run into any particular subprocess issues so far. I built my own TaskSystem for this, but lately I've been thinking "AiTicketSystem" might be a more fitting name. It's still pretty incomplete and there are parts I'm too lazy to fix, but if you're interested, I can publish it on GitHub. What do you think? P.S. I don't always get reply notifications from X, so my responses might be delayed.

• 
  Scematica (@scematica) reported 32 minutes ago

  @RetardedNi85688 so please, really you guys need to do your part not just by buying and holding but doign what really matters. making issues on the github, helping me test, things of this nature that are free.

• 
  Axe Ghost. Now with Fragments mode🌟 (@axeghostgame) reported 32 minutes ago

  graph in the OP is built from data around the Godot repository from github. it confirms Godot's PR backlog is up and external contributor quality is down. the narratively complicating thing is that both trends significantly predate ai tool availability.