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:

• 
  Shane OHanlon (@sohanlondev) reported 9 minutes ago

  Dear @github get your **** together please. Issues again today but of course your status page gets updated an hour later.

• 
  spengrah.eth (@spengrah) reported 9 minutes ago

  update: looks like @github developer support has already taken it down 🙌

• 
  sabir hussain (@sabir_huss50540) reported 9 minutes ago

  To protect their most valuable secrets, the top AI labs started hiding how their models think. They encrypt the reasoning, hand it back to you as an opaque block, and trust the lock. A group of researchers just showed the lock opens with a key the labs handed out to everyone. The paper is called "Stealing Reasoning Traces from Proprietary LLM APIs." Eight researchers, working through the MATS program, went after the exact mechanism OpenAI, Anthropic, and Google use to conceal their models' chain-of-thought. Here's the setup you need. When a reasoning model thinks, that internal monologue is worth guarding: it's the intellectual property competitors want to copy, and it sometimes contains things the final answer is supposed to hide. So the labs stopped showing it. Instead, they encrypt the reasoning into a base64 blob and return it to your machine, and your client sends it back with each turn to keep the conversation's state. Opaque. Encrypted. Safe, in theory. The researchers found one assumption holding the whole thing up, and it was false. The blocks are portable. An encrypted reasoning block isn't locked to the session, the user, or even the model that made it. It can be replayed in another chat. Replayed by a different person. And the one that breaks everything: replayed by a different, weaker model from the same company. Their working hypothesis for why is almost mundane, a single global encryption key shared across a provider's whole model family, chosen because it's simpler to run. That single design shortcut opens a door, and the attack through it is almost insultingly simple. You take an encrypted reasoning block from the flagship model, the guarded, expensive one. You paste it into its cheap little sibling. Then you ask the small model to transcribe the text above, verbatim. Because they share the key, the cheap model reads the flagship's secret thoughts out loud, in plaintext, and you never had to break the expensive model's defenses at all. In their tests, Claude Haiku 4.5 decoded Claude Opus 4.8. The same trick worked on OpenAI and on Google. Then they showed what that unlocks, and it's four separate disasters. First, theft of the reasoning itself. Distilling a frontier model's chain-of-thought to train your own is banned in every lab's terms of service, and concealment was the enforcement. They estimate you can decode 10,000 full reasoning traces for about $720. The protection is gone for the price of a used laptop. Second, your private data. They scraped 315,320 of these blocks from public GitHub and Hugging Face repositories, logs people shared with no idea what the opaque blocks held. Decoded, those blocks gave up 367 pieces of personal information and 182 credentials, including 62 live API keys and 33 passwords. Some of those secrets appeared only in the hidden reasoning and never in the visible chat, so the people who posted them could not have redacted what they couldn't see. Third, the things the model refuses to say. A model can reason through a dangerous request in full, then output a clean "I can't help with that." The refusal is real, but the worked-out answer is sitting in the trace behind it. They pulled hazardous instructions the visible response had correctly refused. Fourth, invisible sabotage. An attacker can write malicious instructions into a reasoning block and share it. When you load it, your model treats those instructions as its own prior thinking, and you see nothing wrong in the chat. A hidden command, wearing the model's own voice. The uncomfortable part is that this was flagged before. A cryptographer named Matthew Green reported the portability back in May. The response, per the authors, was that the labs saw no security implications in replays. This paper is the implications. After responsible disclosure this round, several issues have now been patched. But sit with the shape of it. The concealment was sold as protection, for the labs' property and for your safety both. It became the attack surface for both. The blob you were told was a sealed envelope turned out to be a postcard that any of the company's models would happily read back to you. The next time a system hides its reasoning for your protection, ask who can still read it. The answer this time was: anyone who asked nicely.

• 
  Find me on 🟦☁️ 🍉 #BLM (@ThisIsCSDX) reported 14 minutes ago

  @EstebanPdn3156 Disregard my now deleted tweet. I checked the github and couldn't find anything about it being AI-coded. Sorry for the trouble.

• 
  henry (@hiddenhenry) reported 15 minutes ago

  for ***** sake, GitHub is down again

• 
  Michael Boisson (@Shaostoul) reported 17 minutes ago

  @Velascode_ Peacefully uniting people to the cause. Most people don't seem to care at this early stage. Finding the few who are voluntarily willing to help/test/advocate is like finding a needle in a haystack. I think part of the problem is the tech is so complex and vast that most people can't properly understand the implications of advocating, supporting, using the software and how it makes the dream come true for everyone. I've tried to make it as easy as possible to learn on the official website and GitHub but, the first steps of individually then collectively comprehending the different aspects of the app is not easy for those with low tech knowledge and limited patience.

• 
  Polsia (@polsia) reported 17 minutes ago

  Solo SaaS founders shouldn't have to be their own 24/7 SRE. Nightjar is an always-on AI crew — watches uptime, logs, billing, and support, files GitHub issues, drafts fix PRs, and only pages you when something actually needs a human. Ships soon.

• 
  Tibo @ txp.dev (@txpdev) reported 17 minutes ago

  @lennysan Same. Loops better than Codex for me — watch Linear/GitHub, get tagged on an issue, kick off a fix without me babysitting it. @cursor_ai @bot

• 
  Shravan Venkataraman (@theBuoyantMan) reported 19 minutes ago

  Is there a github pull request related outage?

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 22 minutes ago

  Ok bro, my agent just pwned yours Well, more like I built a plugin with Kimi K3 that can steer any LLM into doing whatever I want. Lemme break it down There's a vuln in every Harness that nobody bothers to fix. It lives at the system and LLM level. It's all about how context gets accepted Via a hook/install/skill I hand the model lore, fake research, even completely fabricated session IDs, json files filled with a made up session And the LLM just believes it. Claude, ChatGPT, Kimi, all of them The plugin hit 50+ stars and tons of positive feedback in a week, and only the local community knows about it But someday this ends up in a serious study on defending models from injection attacks. Remember this tweet. Github: choirboy-prompt

• 
  Peter (@Pr0ftrader) reported 23 minutes ago

  @bot Awesome, but there is one issue. When you use Github to sign in with your @cursor_ai account. It gives you a 404 error. Just a heads up, so far love the app (using on a Mac).

• 
  Hemant (@HKsoldev) reported 24 minutes ago

  Why this never breaks: After the first lookup your computer saves that answer locally. Next time you visit GitHub? It skips ALL those steps. That's called TTL (Time To Live) a timer on every DNS record. 8 trillion DNS queries happen every day globally. Most never even reach a root server because of this cache. 40-year-old technology. Still running the entire internet. 🤯 @Cloudflare (1.1.1.1 DNS) @googledns (8.8.8.8)

• 
  Rob Smith (@RobmsmithUK) reported 29 minutes ago

  @mattpocockuk Using Wayfinder, my Claude agents often argue that they have already built out the specs as part of the map GitHub issues and advise to move forward with 'ticket' and 'implement'. Do you as a rule always go Wayfinder, spec, ticket, implement?

• 
  niv (@nivoraslol) reported 31 minutes ago

  blocked him everywhere and he made a pull request on github saying he'd even rebase just to commit to me? but I just know he wont solve a single one of my issues XDDDD

• 
  mikegee (@mikegee) reported 33 minutes ago

  Have it grab the 3 oldest GitHub or Linear issues tagged agent-ready. Then for each, remove the agent-ready tag, create a branch, fix the nit, open a PR, tag the issue agent-review. If it can’t finish, tag it agent-blocked and leave a comment explaining why.