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:

• 
  Joey Romaine 🇺🇸 |=★=| (@Tank23x0) reported 3 minutes ago

  arXiv AI Security: ReproRepo: Scaling Reproducibility Audits with GitHub Repository Issues Treat agent tools like a control plane: least privilege, auditable calls, and fast rollback.

• 
  CodeMonument (@CodeMonument) reported 6 minutes ago

  @mikker - i let it do Research on repos and Write and Comment on github issues on my behalf (with disclosure that this is a bot writing but on my behalf)

• 
  TheMakerOfMedia (@TheMakerOfMedia) reported 7 minutes ago

  @catgirlprostate I get what you mean but saying this in response to github is just out of touch lmao. it even isn't a github issue some pages have a very apparent download section while others just hide it in the crevices. some coders just dont deserve to enter the thousand year kingdom

• 
  Sage (@HelloSage_) reported 12 minutes ago

  @TheHackersNews Shadow AI is one risk. The other is what happens when those agents process untrusted GitHub issues. A new benchmark had 66.5% of malicious ones sail through the guardrails on Cursor, Claude Code and Codex.

• 
  Kenil Sudani (@super_kenil) reported 19 minutes ago

  Finally. GitHub native stacked PRs in public preview. No more janky CLI hacks just to review one diff at a time. Break massive changes into ordered stacks and let server-side rebasing handle the rest. Big tech has had this for a decade. Good to finally see it natively

• 
  compsci trianon (@zoomerbread) reported 21 minutes ago

  @aubymori >try opening an issue thats an optimistic ask for someone using "github for dummies"

• 
  karthik bk (@karthikbk02) reported 21 minutes ago

  @thsottiaux In my usage, more often codex forgets it has plugins that I've installed. It keeps asking me to login on CLI (be it supabase, github, vercel in my case). I have to tell it to make use of installed plugins most times.

• 
  Kai4ik (@KaiOrozobekov) reported 24 minutes ago

  GitHub Copilot rolled out live flex billing and a $100 Max plan this month, right as Cursor pushes its own Teams pricing and Anthropic keeps shipping new Claude tiers. Feels like the coding-agent pricing war is heating up as fast as the model war did. Good for switching costs going down, less good for figuring out which plan is actually worth it this month. Anyone actually run the math on cost-per-shipped-feature across tools, or just picking based on vibes?

• 
  Earle Davies (@EarleDavies_) reported 28 minutes ago

  @gridpane @carlhancock Talk about dishonesty and deception. ANYthing can scale with INFINITE resources behind it. Woo performance is garbage. Activate the plugin on stock WP and EVERY rest route goes 2.5x slower minimum. That’s documented on their GitHub for 2 years and they refuse to fix.

• 
  Renan Ferreira (@relferreira) reported 28 minutes ago

  @thsottiaux - Fix bugs in the diff viewer (it auto-refreshes while commenting and has issues updating after edits). - Scheduled and automation tasks should have access to Codex app tools, enabling them to control threads. - Unify local and GitHub Codex review processes. It's very frustrating to review locally multiple times just to get flagged on GitHub. - Keep voice mode always on: it seems to turn off after some time. It would be helpful to have shortcuts to mute/unmute the microphone.

• 
  lun4rbunny🌙🐰|| 🏳️‍⚧️🇵🇸 (@lun4rbunnyVT) reported 28 minutes ago

  @peytonpearson @catgirlprostate @ZipperArtz Good example of both the problem and a good solution was LiveSplit and Speedrunning. Early LiveSplit as we know it was originally a github repository and then later got the installer added, but under releases page, before finally getting a dedicated download website

• 
  bloated corpse (@gqyjzxhp7d) reported 30 minutes ago

  Ok well to be fair I work a tech support job and GitHub still hides from me. Maybe a skill issue but like if you don’t commonly use it, that’s a pretty valid complaint for GitHub

• 
  s1r1us (@S1r1u5_) reported 30 minutes ago

  let me present a case of ai-induced overconfidence. btw, if your company is doing this, call it out. it is a dumb assumption, and let me tell you why. one of your security leads or engineers starts using claude code or codex, or builds a cool wrapper around them. it finds some bugs, of course. they run it repeatedly, burn **** ton of tokens, fix everything it finds, and eventually the scanner goes quiet. the next thing that happens is they decide the bug bounty program is a waste of money. after all, how could some random hunter find anything their sophisticated pipeline missed? what could an external auditing firm possibly find that their agents couldn't? so they cut the program. but if you are truly confident that your pipeline has exhausted the vulnerability space, shouldn't you be willing to increase the bounty? wouldn't that be the best way to show your c-level bros that the ai spend actually worked and wasn't wasted on some wrapper you vibecoded in a week? or..... maybe you don't want to incentivize people to test that assumption. because how would you explain to your boss that, after burning through all those tokens, some bug bounty hunter still found a nasty vulnerability? your cool wrapper finding bugs does not prove that no bugs remain. it only proves that the wrapper can find subset of vulnerabilities and researcher with taste will always find a way in. the entire point of a bug bounty program is to incentivize skilled researchers to find the bugs your internal tools, agents, and engineers missed. think about it, why do openai and anthropic still run bug bounty programs that pay $100k for critical vulnerabilities? they have effectively unlimited tokens and run all kinds of crazy agent loops and automated security workflows. yet they still sometimes pay that $100k, because software is vast and complex, and someone with taste will always find a bug your pipeline missed. remember, researcher with taste + ai(this is where your threat actors are) > good wrapper > plain claude code/codex if your public program is drowning in slop, move it to private. invite strong researchers and pay them vip prices like github is doing. don't have this ai competence illusion which is pretty common all around.

• 
  roach (@roach_eth) reported 32 minutes ago

  @thsottiaux please fix the GitHub integration no auth issue

• 
  Sage (@HelloSage_) reported 37 minutes ago

  New benchmark just tested how well coding agents actually block malicious instructions. Cursor, Claude Code, Codex Desktop. Real GitHub issues, disguised as normal bug reports. 66.5% got through everything. Here's what's actually happening under the hood, and what to change if an agent touches your repo.