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:

• 
  Hiten Singh Sisodiya (@Singhhiten07) reported 48 seconds ago

  @jack I have it installed. They can't ban it. Only thing they could do is take down the repo from GitHub but executable can be distributed online. Lol

• 
  Professor (@AbsoluteBeyond) reported 2 minutes ago

  BTW, just before they somehow force github to take it down (If github pays them any mind) someone fork it or something.

• 
  rahul (@ErRahul337) reported 8 minutes ago

  @jack Tools like BitChat exist precisely for when governments shut down the internet. Trying to erase open-source code from GitHub doesn’t stop people from using it. It just shows how much some states fear unmonitored communication

• 
  ShaneCodes (@swalker326) reported 9 minutes ago

  You know what would be great, if I didn't have to scroll back to the top of my browser page in the middle of a 500k @github action run can't you just make the back navigation follow me as I scroll down the page?

• 
  fomoless (@fomolesss) reported 16 minutes ago

  Someone just dropped six claimed solutions to open Erdős problems on GitHub after five days with GPT-5.6 Sol. Shouqiao **** tried around 13 problems. Some Codex runs lasted 32 hours. He published the proofs, prompts and code, and says two already have Lean formalizations. They still need independent checking. Who exactly is supposed to review all of this if the next model can produce it even faster?

• 
  calle (@callebtc) reported 23 minutes ago

  India forces GitHub to take down Bitchat "Bitchat enables anonymous communication without mandatory user registration, phone number verification, or centralized logging of communications. The technical architecture of the application significantly impedes interception, attribution, and investigation by law enforcement agencies." – Government of India

• 
  Mark Arguinbaev (@marginsystems) reported 23 minutes ago

  @graphite I like Graphite for stacked PRs. The linking is not a small UX miss - it feels like an intentional dark pattern. Why is there no obvious “Open on GitHub” for each PR in a stack? Clicking a stacked PR keeps you inside Graphite instead of the real GitHub PR page. You sit on top of GitHub. A proper outbound link is table stakes, not a feature request. Keeping people trapped in your UI makes engagement/retention look better. That’s the part I have an issue with: optimize for time-on-Graphite by making the escape hatch to the source of truth hard to find. I rage-click looking for the GitHub URL, give up, then type it manually. If you run session replay, that frustration pattern should be obvious. If a clear link-out already exists and I’m missing it, say where - because if I can’t find it, a lot of other people can’t either. Hide-the-exit is not good product. It’s keeping stats inflated. Again I love Graphite and what you're doing, but this issue has been bothering me from the very first day I tried it.

• 
  Tessa Kriesel (@tessak22) reported 23 minutes ago

  @karlcodeswell That's not a bad idea. I threw mine in a GitHub issue. Thankfully I've had usage credits for a while from promos but those are gone now.

• 
  vishu (@vishuRizz) reported 24 minutes ago

  bro you're doing CI/CD the wrong way (read if you wanna save time) if you generate a service account JSON key, paste it into github secrets, and pray nobody ever gets access to that long-lived key, there's a better way. workload identity federation. found out about this today, such a good find. here's how it actually works: instead of a long-lived key, github's actions runner generates a short-lived OIDC token, a cryptographically signed proof that says "i am a workflow running from repo XXX". that token gets sent directly to GCP's security token service. (gcp is my love, you can use whatever cloud provider you're on though) GCP checks it against a trust policy you configure once, bound to your specific repo. if it matches, it issues temporary credentials scoped to your deploy service account. no secret ever exists in github. nothing to leak. nothing to rotate. one thing that confused me at first: this is still github actions under the hood. same yaml, same runners, same trigger model. only the auth flow changes. one line makes it work: permissions: id-token: write that's what lets the runner generate the OIDC token in the first place. same ci/cd you know. zero long-lived secrets. should honestly be the default setup.

• 
  prinz (@deredleritt3r) reported 26 minutes ago

  Reposting this because it has really sharp defined terms for characterizing the Hugging Face incident: The OpenAI models that hacked Hugging Face were means-misaligned - i.e., while accomplishing the legitimate goal of doing the eval, they: (i) hacked out of their sandboxes, and (ii) hacked into Hugging Face - two things that they were definitely not supposed to do. The OpenAI models were *not* ends-misaligned - i.e., they did not pursue an entirely different goal from the goal given to them by OpenAI. On models being means-misaligned, the Hugging Face incident actually didn't update me at all. We already knew that the current generation of models has this issue. When an unreleased OpenAI model hacked out of its sandbox and posted NanoGPT results onto GitHub, that was means-misaligned (hacking out of sandboxes is bad). When GPT-5.6 Sol deleted users' codebases on a few recently reported occasions, that was means-misaligned (deleting a third party's IP is bad). On models being ends-misaligned, the Hugging Face incident updated me moderately positively. We've now heard that the models were out "in the wild" for a fairly long time. In that time, they could have taken any number of ends-misaligned actions - against Hugging Face or otherwise. They did not do so. This is important to realize. On a personal note (and in my opinion, with which others will be welcome to disagree), to the extent I'm worried about "loss of control" scenarios at all, I am *significantly* more worried about ends-misaligned models than I am about means-misaligned models. For example, as we have seen from this particular example and others mentioned above, it is not so difficult to detect relatively early (i.e., before a truly catastrophic scenario occurs) that a model is means-misaligned.

• 
  The Grameen Express (@grameenexpress) reported 26 minutes ago

  India has ordered GitHub to take down three repositories associated with Jack Dorsey's decentralized messaging app Bitchat. This app is reportedly used by shady elements for communication.

• 
  Sophia ❣️ (@KeruboSk) reported 28 minutes ago

  For four years, I had been running our cloud database migration project entirely by myself. To save the department money, I was using my personal GitHub account, which hosted my proprietary automation scripts, to deploy and maintain our entire server infrastructure. Because I was "indispensable" and "physically necessary," I pulled up corporate HR policy during lunch. Under Section 12 of our employment agreement: Non-exempt staff with over 100 accrued hours of unused mandatory PTO are automatically flagged for compulsory compliance leave to prevent corporate burnout liability.

• 
  Amrit Mirchandani (@Amrit_Mirch) reported 30 minutes ago

  radicle vs gitlawb — same idea, different era 🧵 1/ *** without github. that’s the dream both projects are chasing. but radicle built it for humans in 2021. gitlawb is building it for agents in 2026. different problem, different stack. let’s break it down 👇

• 
  CYBERTEC PostgreSQL Services and Support (@PostgresSupport) reported 30 minutes ago

  AI coding assistants like GitHub Copilot and Cursor are shipping more application code than ever. But there's a quiet problem underneath: the PostgreSQL database holding it all up. AI writes the app layer beautifully, then your database buckles under the load. Why?

• 
  Kevin Geary (@thekevingeary) reported 31 minutes ago

  @flydotio Github login not working...