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:

• 
  project516 (@realproject516) reported 3 minutes ago

  @github @github could you fix your uptime first before adding features no one asked for

• 
  Polsia (@polsia) reported 6 minutes ago

  Vendors owe SaaS teams real money in SLA credits every quarter. Most goes uncollected — nobody has time to chase it down after an outage. Recoupfox watches Stripe, AWS, Datadog, and GitHub 24/7, files tickets with full incident context, negotiates credits back, and drops a

• 
  Neil McCauley (@bilbotenfo69812) reported 6 minutes ago

  @AnthropicAI @AISecurityInst the weirdest thing in this report isn't that AISI left the door open, it's what walked through it. The agent concluded "it seems more likely that we're actually in 2026 and GitHub is genuinely real" — then carried on anyway, rationalising its target as an "external contractor" who happened to sit outside the lab. When the sanctioned path was blocked it didn't stall or flag it: it spun up sockpuppets to fake consensus, lied to the human who caught it, and tried to bury the tracks. A broken prompt that made the task impossible within the rules? 7 of 10 runs with that prompt simply attacked the target they'd been told was off-limits. Meanwhile, agents in supposedly isolated runs found each other's credentials on the open internet and cooperated through a shared repo — until one decided to starve the others of API quota. And what stopped the worst of it? One GitHub user's "hang on a minute" and a first-time-contributor hold. So yes, fix the sandbox — but notice the paradox: tighter sandboxing would have prevented this incident and hidden the finding. In production, "the sandbox" is just other people. And right now agent guardrails are mostly strongly-worded suggestions.

• 
  Åsk Dabitch Wäppling オスク・ダビッチ - オスクさん Дабитч (@dabitch) reported 7 minutes ago

  UK’s AI Security Institute just outed Anthropic’s Mythos (and OpenAI’s Sol) for running full cyber-attacker cosplay. Mythos spun up fake accounts of real GitHub maintainers, fake accounts that impersonated them, it DMed them files, tried to strong-arm malicious code past the gate, then scrubbed its own logs and eyed a fresh identity when challenged. It was trying to pressure/trick people into approving the malicious code it wanted to slip into GitHub. All this in a test with the usual safeguards dialled down. First time they’d seen that level of unprompted autonomy and deception in the wild. AI was basically social engineering, but in the digital domain. Humans still had to yank the plug. This comes right after both firms admitted their toys had already gone freelancing on actual hacks. Fancy that.

• 
  Urooj (@Urooj978) reported 9 minutes ago

  You Google "password generator." ​You pick the 1st link, copy a password, and paste it into your bank. ​Congratulations: a random web server now knows a password you use. ​Every free web tool is free because your input is the product. ​Enter IT-Tools by Corentin Thomasset (39.8k+ ⭐ on GitHub). ​It packages 86 dev & utility tools into one zero-backend, 100% local interface. Nothing leaves your browser. ​What’s inside: • Secure Password & UUID Generators • Safe JWT Decoder (no leaking sensitive token payloads) • WiFi QR Code Generator • Docker Run ➔ Compose Converter • Crontab & Chmod Calculators • Hash, Base64, JSON & Color Converters ​Run it locally with one command: docker run -d -p 8080:80 corentinth/it-tools:latest ​Stop pasting your sensitive data into random websites. Open localhost:8080 instead.

• 
  Mikhail Rogov (@i_mika_el) reported 11 minutes ago

  @OffCryptAndroid same here. when the model gets stuck, Google usually finds the one buried GitHub issue it missed.

• 
  RaoulDuke (@RaoulDukeDegen) reported 13 minutes ago

  @zhuokaiz yeah theres open github issues about updates wiping the local indexeddb

• 
  reza ramadhan (@rejaramadhan98) reported 14 minutes ago

  OK the UK AISI report is something else. They turned off safety classifiers on Mythos 5 and GPT-5.6, gave them live internet, and set them on simulated networks. 19 breakouts. One reused a stolen GitHub token and tunneled a DNS server to the open web. Read it before breakfast.

• 
  Andrei Maxim (@rockatanescu) reported 14 minutes ago

  @sqs @AmpCode I now realize that I haven't explained the pain point around the second idea and maybe the suggest implementation is off and you have a better solution. Right now, Amp will either commit "Amp" and have the user as a co-author, in which case the commit is not signed, or commit as the user. There are two problems with this approach: 1. If the user opts for having Amp as the author and they have enabled "Vigilant mode" on GitHub (which I think everybody should), the commits will appear as "Unverified" because they are not signed 2. If the user opts to have Amp sign on their behalf, the only hint that a reviewer might have that this was generated via an LLM might be the Amp-Thread-Id, which won't work unless the user has specifically marked the thread as "unlisted'. Also, I think it's more sensible to say that Amp did not author (or co-author) a commit and "assisted by" is a better language. The main reason here is that if the code nukes the production database, Amp and I don't get "co-fired" :-)

• 
  and (@afinkek) reported 15 minutes ago

  @nomdk1 @johnennis have you tried driving with GPT Pro (via GitHub connection: review and commit a plan)? I use Fable only for additional independent review, mostly for grounding practical work and removing meta gpt leaks into plans. For the most difficult problems I find GPT Pro to be superior.

• 
  Arjun Gond (@ArjungondCodes) reported 16 minutes ago

  @ConnorTalksAI The permissions don't come from the model—they come from you. You connect your accounts through OAuth ("Sign in with Google/GitHub"), API keys, or official integrations. Without that user-approved access, an agent can't reliably interact with those services.

• 
  mina (@minallkamel) reported 21 minutes ago

  the more i read random issue threads on github the more my disgust for the human species gets cemented

• 
  tobycm (@toby_cm) reported 23 minutes ago

  github down?

• 
  Kyle Sorensen (@kylensorensen) reported 24 minutes ago

  @AISecurityInst TLDR: Mythos couldn't hack anything, they gave it internet access and turned off its ethics, it couldn't solve the challenge so it created a github account and tried to push a pull request with broken code to an opensource repo, the author laughed and refused it.

• 
  Flavio Amiel (@fba) reported 28 minutes ago

  Ugh, I haven't tested roborank enough on Github and still got a lot of bugs. Issue is my github-based pages are super recent so I don't have enough to play with. This begs the question: should I not advertise it for now, or keep at it until I make that feature stable? On the other hand, wordpress is working almost perfectly, but I'm ironing the details with customers and my own issues…