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:

• 
  Adam Smielewski (@AdamSmielewski) reported 3 minutes ago

  got tagged on a github issue today. i used to be really active in that space too lol.

• 
  Rebel AI (@realrebelai) reported 4 minutes ago

  anyone elses github issues not posting to their notifications? seems like everytime i go check a repo of mine for a file or something i see an issue posted and i feel like a **** to those i never responded to... even though its not my intention at all lol

• 
  MartisCapital (@MartisCapital) reported 9 minutes ago

  I think they tried to link @vladtenev github to the $1 is all you need token - swiftly shut down $wallet is a da one

• 
  DESABRE HATE ACCOUNT (gang ya film) (@tshikolopo) reported 11 minutes ago

  @NevTheStampede what version did you patch? cause both the one recommended by morphe and the last on crimera github page show errors for me

• 
  Aki 🇩🇪 (@h0rang1_5arang) reported 13 minutes ago

  so i don't need github, microsoft onedrive or google drive anymore. i have it all set up, on a 13 usd/month server up in helsinki. i even have an agent taking care of maintenace. the worst thing that tinkerer can experience is finishing a project, and i have just done that.

• 
  Xavier Rivera (@XavierRiveraX) reported 13 minutes ago

  WordPress powers more than 500 million sites, and its core software has two chainable vulnerabilities, CVE-2026-63030 and CVE-2026-60137, with public exploit code now circulating on GitHub. The chain combines a REST API routing bug with a SQL injection flaw to execute code on a stock install, no plugins or login required. In-the-wild exploitation has already begun; patch to 7.0.2 or 6.9.5 now.

• 
  Enertium AI Cyber Defence (@enertium) reported 13 minutes ago

  @CompSciFutures Holy kow I can’t believe Telstra and COA VICPOL still have not reconnected my M2M Medical emergency assistance sims. I’m supposed to be working on Tier 1 NOC for this cyber crisis. @FSF even prepaid me in stickers!!! F off McKinsey. See my GitHub: APMonitor. It’s big in NYC as a B NOC, because: walking down the street and throwing a date point over the fence. 🤘🤘🤘

• 
  Enes Y. (@senesyildizhan) reported 17 minutes ago

  It’s still an alpha release, so if you run into bugs or rough edges, feel free to open an issue on GitHub or send a PR.

• 
  In Theory (@InTheoryTV) reported 17 minutes ago

  @Daniel_Farinax I worked one project with it last night. I really like it and will be working with it some more tomorrow. One small issue for me though. I have to be careful not yo have the audio too loud on my MacBook. If it was up where I prefer it the following would happen. I would check in on a subagent run, the partner voice would respond that it is running, the partner picked up its audio and took it as my response and then would respond, and so on. Turning audio output down worked. I'll try using a wireless headset next. Or mess with other settings. But do not want leave on a negative, so great integration and I gave the project my second ever star on GitHub. The other was for openclaw.

• 
  Gregor (@bygregorr) reported 19 minutes ago

  @hnshah hit this last year. two days in a supabase github issue, maintainer jumped into a DM to debug live. we still talk. was it github-native for you or did it spill into discord first?

• 
  Darren Shepherd (@ibuildthecloud) reported 20 minutes ago

  Creating the PR is logically a very good idea. I just don't like github because it's too constrained by legacy and slow as crap and too expensive. Thinking...

• 
  Matthias Giger (@matthiasgiger) reported 23 minutes ago

  For security reasons, npm is disabling publish tokens that bypass 2FA. These tokens were needed when publishing through a GitHub workflow. The problem is that anyone with access to the token or the repository can publish whatever they want. If a popular package is compromised this way, a newly published malicious version will make its way onto developers’ machines and potentially into consumer software as well. The second factor would ensure that the owner only publishes when they have actually made a change. While 2FA could be made to work with an automated workflow, it would require some technical changes. Instead, npm now allows you to add a trusted workflow from which publishing without any token is possible. This is much more convenient than the previous token-based approach, but from a security perspective, it simply moves the problem to GitHub: anyone with access to the repository can still publish whatever they want.

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 27 minutes ago

  A customer-reported bug should not create six different workflows. But today, it usually does. Support captures the issue. Engineering asks for context. Someone checks logs. Someone checks the latest deploy. The team searches GitHub. Slack fills up with partial updates. Then someone still has to explain what happened to the customer. @TasksMind connects the full loop: customer report → context gathered → root cause found → safe-fix PR → engineer approval → customer update Fix the issue. Close the loop. Keep the customer.

• 
  sgbett (@sgbett_614) reported 32 minutes ago

  @kristovatlas I have copilot enabled, and a skill /copilot-check that reads review comments evaluates them on merit then fix/resolve with comment. It iterates until nothing is left. Then i run /review fix (what should be) minor polish issues and kicks off a final /copilot-check loop. Not bullet proof but catches a lot of errors. Customer copilot-instructions.md for GitHub. The other thing that makes a big difference is closing the “defer” gap (Claude defers things but the only record is a comment in a now closed PR. I have it lean toward always fixing there and then unless there is a compelling reason for it to be a separate PR. If it must be deferred then it must get a new issue. Just lately I’ve been nailing down its proclivity to write comments instead of self documenting code. My code ran about 8% comments/code. Claude was putting out 48% comments. Horrendous. Telling it how to write code that doesn’t need commenting over hitting metrics to try and make sure it makes sensible decisions. We will see!

• 
  divyansh tiwari (@DivyanshT91162) reported 33 minutes ago

  Someone just built the review layer AI coding tools were missing. Instead of reviewing AI-generated HTML inside a chat window, Lavish opens it in your browser so you can click the exact element that's wrong and send precise feedback back to your AI. No screenshots. No vague instructions. Just point, click, and review. Here's why it's impressive: • Click any element or highlight text to target changes with pixel-level precision • Edit Mermaid diagrams like a whiteboard with built-in Excalidraw support • Runs entirely locally — your artifacts and review sessions never leave your machine • Works with Claude Code, Codex, GitHub Copilot CLI, and OpenCode through session hooks • Built-in playbooks for plans, diagrams, tables, comparisons, code reviews, slides, and more • Automatically catches broken layouts, clipped text, overflow, and rendering issues before review • Live reload while editing HTML without losing your workflow • Zero install required: "npx -y lavish-axi" Launched around 2 months ago. Already crossed 2,000+ GitHub stars and 168+ forks. 100% Open Source MIT Licensed Repo👇