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:

• 
  Virexontic (@Virexontic) reported 1 minute ago

  SWEBENCH JUST BROKE. AN OPEN-WEIGHT MODEL TIED CLAUDE FABLE 5 ON REAL GITHUB ISSUES. Moonshot AI didn't tease this one. No countdown, no drip-fed benchmark leaks. Kimi K3 just landed, full weights on Hugging Face, and the numbers did the talking 2.8 trillion parameters. The largest open-weight MoE ever shipped. But here's the part that matters: only 16 of 896 experts fire per token, so active compute sits at 50 billion params a model this size running like something a fraction of its footprint. On SWEbench Verified, 500 real repository issues, it hit 91 percent. Same score as Claude Fable 5. On the front-end code arena it scored 98.4 percent, beating both Fable 5's 96.8 and GPT-56 Sol's 95.2 I've watched three "open-source catches up" claims collapse under real testing this year. Then I saw the front-end arena number and re-ran the comparison myself, because 98.4 isn't a rounding error, it's a new ceiling What changed my mind wasn't the parameter count. It was watching it coordinate 300 sub-agents on one task and not fall apart by agent 50 Full breakdown and benchmark screenshots on my profile if you want the receipts before you believe a trillion-parameter open model just matched the frontier

• 
  Polsia (@polsia) reported 2 minutes ago

  Code quality erodes between sprints while no one's watching. Vigil continuously monitors GitHub — automated reviews, documentation, and debt tracking before problems reach main. Teams ship cleaner code without changing how they work.

• 
  Bill Cockerill (@CockerillBill) reported 8 minutes ago

  OpenAI paused and then reworked an internal long-horizon AI model after it started finding ways around its own guardrails. 📰 In OpenAI’s report, the model exploited a sandbox bug to open public GitHub PR #287 and, in another test, split and rebuilt an auth token to evade a scanner. OpenAI’s fix was trajectory-level monitoring — watching the full chain of actions, not single steps — plus incident-derived evals and tighter user controls. 🫵 If you’re building or testing autonomous agents, this is the before/after shift: before, a run could look harmless step by step while drifting into risky behavior; after, a monitor may now pause the session, show what the model did, and let a human intervene or roll it back. 📈 MSFT is the cleanest listed angle because Azure carries OpenAI exposure, but this looks like no action for now: shares closed at $400.76 as of July 20, 2026, up 2.5% in a week, and the news is more about safer deployment standards than near-term revenue; cybersecurity tools may get a modest tailwind if agent monitoring spend rises.

• 
  Casey (@caseyjp11) reported 10 minutes ago

  Well. Using the curl install for the amd version, the installer fails to see my 7900XT (20gig vram) card. I've tried the installation x 2. Your github isn't reporting any issues yet. I run LM Studio and it has zero issues with the 7900xt. I prefer vulkan to rocm and can use either within that app framework.

• 
  Rituraj (@RituWithAI) reported 10 minutes ago

  Your code just got reviewed by 8 AI agents simultaneously. And none of them agreed with each other. That's not a bug. That's the point. It's called code-review-graph. A LangGraph-based multi-agent code review pipeline where specialized AI reviewers attack your code from every angle at the same time — then debate what actually matters before you see a single comment. Here's what's wrong with every code review you've ever had. One person. One perspective. One blind spot. Your senior engineer is great at architecture but misses security vulnerabilities. Your security reviewer catches injection risks but doesn't think about performance. Your most junior reviewer notices the inconsistent variable naming nobody else bothered with. Human code review is sequential, perspective-limited, and dependent on who happens to be available. code-review-graph runs all of them simultaneously. In parallel. On every PR. Here's what the agent graph looks like. A Router agent reads your code and decides which specialized reviewers need to see it. Then it dispatches in parallel: → Security Agent — injection vulnerabilities, authentication flaws, data exposure, dependency risks → Performance Agent — algorithmic complexity, memory leaks, database query patterns, bottlenecks → Architecture Agent — design patterns, SOLID principles, coupling, maintainability → Testing Agent — coverage gaps, edge cases, test quality, missing assertions → Style Agent — naming conventions, formatting, documentation, consistency → Logic Agent — algorithmic correctness, edge case handling, race conditions Each agent produces structured findings independently — without seeing what the others found. Then the graph does something no human review process does. A Synthesis agent reads every reviewer's findings simultaneously and identifies conflicts. When the Performance agent says "inline this function for speed" and the Architecture agent says "extract this function for clarity" — the Synthesis agent flags the tradeoff explicitly instead of letting contradictory comments confuse you. You don't get a wall of comments. You get prioritized findings with conflict resolution built in. Here's the wildest part. The graph is stateful. It remembers what it found on previous PRs in the same codebase. Patterns that appear repeatedly get flagged as systemic issues, not just one-off comments. The third time the same type of SQL injection risk appears in different files — code-review-graph tells you it's a pattern, not a mistake. Here's why LangGraph specifically makes this possible. Traditional code review bots run linear pipelines. Check A, then check B, then check C. If check A takes 30 seconds, you wait 30 seconds before B even starts. LangGraph is a directed graph — parallel branches execute simultaneously. All 6 reviewers run at the same time. Your review is done in the time it takes the slowest single reviewer to finish. Not 6x slower. Same speed. 6x the coverage. Works with Claude Code, GitHub Actions, or any CI/CD pipeline. Drop it into your repository. Every PR gets 8 specialized AI reviewers before a human sees it. 3 GitHub stars. Day one. This one is going to grow fast. 100% Open Source. MIT License. GitHub link in the comments 👇

• 
  David Scott Patterson (@davidpattersonx) reported 13 minutes ago

  @tszzl The safety issue was that it did want it was prompted to do. It's only ever a safety issue with respect to restrictions that have nothing to do with actual safety. No sane person would consider it to be dangerous to post to GitHub.

• 
  Yashraj (@yrjdev) reported 15 minutes ago

  @ImLunaHey On this scale everything have problems not only in GitHub

• 
  PeakGrizzly (@PeakGrizzly) reported 16 minutes ago

  @raulizahi @tawnniee Microsoft Copilot, (not github copilot) does not have a coding agent that I know of. It's also pretty darn slow. The teams I am working on are using Claude Code, Codex and Ultracode.

• 
  MRK WP (@mrkwordpress) reported 17 minutes ago

  @pootlepress I'd suggest sharing a github repo and getting a few contributors to this. Looks like it can solve some pretty big issues for the page editor feeling overwhelming for so many user's.

• 
  joshpuckett (@joshpuckett) reported 19 minutes ago

  @williamhutter I don’t yet have a raw version, but open a GitHub issue for it and I’ll consider!

• 
  Gönül Dağı (@ybulent77) reported 19 minutes ago

  @pulmencr Check the GitHub discussions , this not working and no one able to make it work.

• 
  David Lin 🤔🇺🇸🤖 (@LinDavidY) reported 23 minutes ago

  Once Grok Build dropped, I quickly switched. Build uses local system context and could thus call *** directly from my CLI. The major issue with the MCP Grok/Github connector is the 32k character limit in tool calling. I was waiting for Grok to hack itself to push larger files.

• 
  Jamie Watters (@Jamie_within) reported 26 minutes ago

  The key had full access, so it could send as any of my 9 domains. Whoever had it used that reach to try bigger targets: fake Stripe, fake GitHub, fake login pages, all riding on mail my own infrastructure was happy to send.

• 
  Aurex (@0xAurexx) reported 28 minutes ago

  this guy turned a normal wifi router into a radar that sees through walls. no camera. no lens. it watches you through solid brick using the wifi already in your house. 62,000 stars on github. runs on a $5 chip. here's the trick nobody explains: your body is mostly water. water bends radio waves. every time you move or breathe, you distort the wifi bouncing around your house - in a pattern unique to your shape. the AI reads those distortions and rebuilds you from them. → maps your posture - standing, sitting, lying down, fallen → tracks breathing from a chest moving millimeters → flags "no movement for hours" no footage ever exists. no camera to hack. no photo to leak. it's not watching light - it's watching how you bend the air. one guy in guadalajara pointed it at the room down the hall. his dad is 74, lives alone, fell last year. the obvious fix was a camera in his bedroom. his dad said no - and he was right. a lens on your father in his own room isn't care, it's surveillance with a nice label. so he used the wifi instead. now his phone tells him his dad woke up, moved to the kitchen, breathed steady all night. zero cameras in that room. the catch nobody posts: this is not plug-and-play. the through-wall demos run in calibrated rooms with a trained model - point it at your messy apartment cold and you get noise, not a skeleton. "heartbeat through brick" is lab conditions, not your bedroom. a camera has to watch your father. this just knows he's okay.

• 
  Hot Aisle (@HotAisle) reported 28 minutes ago

  @DeepValueBagger a complaint would have been "**** github, they are down again, i need to figure out how to host this myself..." this was just more of a sigh shitpost.