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:

• 
  Marc Campbell (@marccampbell) reported 3 minutes ago

  i made my e2e test suite for my factory runtime use github issues, daytona, and create an actual bootstrapped openclaw instance to test and it runs faster than the ai code review, which means it's not the slowest part of the pipeline

• 
  Jonathan Ong (@jongleberry) reported 3 minutes ago

  @matteocollina @github Oh, I thought this was something wrong with ubicloud, I've been dealing with a lot of GitHub Actions issues recently

• 
  CyrilXBT (@cyrilXBT) reported 4 minutes ago

  A guy named nbatman on Reddit accidentally built the most censorship-resistant website on the internet. Hollywood tried to kill it. Spotify tried to kill it. Adobe tried to kill it. Google delisted it. Reddit shadow-banned it. The Motion Picture Association flagged it as a top threat. The RIAA pressured every hosting provider it ever used. It is still online. Updated every single month. By six anonymous volunteers working in their spare time. Here is why nobody can shut it down and what it teaches every builder about the future of the internet. THE ORIGIN 2018. One Reddit moderator. One Google Doc. A single person decided to organize the internet's free resources into one place. No company. No funding. No team. Just a document that kept growing because people kept finding it useful. Google killed it with a DMCA takedown in 2023. What happened next is the part worth understanding. THE REBUILD The community did not petition Google. They did not hire lawyers. They did not start a campaign. They rebuilt it on their own domain, mirrored it to GitHub, deployed it to IPFS, and distributed it across 12 backup domains simultaneously. In doing so they accidentally built one of the most resilient information architectures on the internet. No central server. No single point of failure. No CEO to pressure. No hosting provider that matters. When you remove every central point of control from a system the only way to kill it is to kill the internet itself. Hollywood has not figured out how to do that yet. THIS IS THE FUTURE OF INFORMATION What nbatman built without intending to is a blueprint for how information survives in an era where platforms can disappear anything with a single policy decision. IPFS does not work like a normal website. A normal website lives on a server somewhere. Find the server. Pressure the host. Site goes down. IPFS stores content across thousands of nodes simultaneously. There is no server to find. There is no host to pressure. The content exists as long as at least one node in the network holds a copy. This is the same architecture behind every major blockchain. It is the reason Bitcoin cannot be shut down by any single government. Applied to information it means the same thing. No single entity can decide what survives and what disappears. WHAT THIS MEANS FOR BUILDERS Every platform you build on right now has a terms of service. Every terms of service has a clause that can remove you without notice. X. YouTube. Substack. Medium. All of them. The builders who understand decentralized infrastructure are not just building products. They are building on foundations that no platform can pull out from under them. IPFS. Nostr. Distributed storage. Peer-to-peer protocols. These are not niche technologies for crypto enthusiasts anymore. They are the infrastructure layer for anyone who wants to build something that lasts. THE LESSON FROM SIX ANONYMOUS VOLUNTEERS Six people. No salaries. No office. No investors. Maintaining something that the most powerful entertainment companies on earth cannot destroy. The lesson is not about the content they organized. The lesson is about what becomes possible when you remove every central point of control from a system and distribute it across a community that believes in what it is building. That architecture is available to every builder reading this right now. The question is whether you are building something that a single policy decision can erase or something that survives because no single decision can touch all of it at once. nbatman did not set out to answer that question. He just made a Google Doc in 2018. The answer found him anyway. Follow @cyrilXBT for the exact tools, protocols, and infrastructure decisions that matter for builders who want to build things that last.

• 
  Maheer (@UsamahMaheer) reported 5 minutes ago

  Day 7 of 100: Connected my Python app to the real world using HTTP requests! But the biggest win today? Security. Learned how to lock down my API keys using python-dotenv and .env files to keep secrets off GitHub. Never hardcoding credentials again! #100DaysOfCode

• 
  49 Agents IDE - IDE for Agentic Coding (@49agents) reported 6 minutes ago

  @bettercallsalva @TopStockAlerts1 distribution doesnt save slow shipping is the thesis here. copilot had the entire github ecosystem and still got out iterated by cursor on workflow ux. same thing happened with teams vs slack..microsoft owned the network but couldn't out-execute

• 
  Sean Davis (@SeanChDavis) reported 17 minutes ago

  @ajaydsouza Also, it isn't a real roadmap, like what you would have as GitHub issues. It's more of a to-do list of things it knows I want to do, but just hadn't done yet. That's probably the key to the behavior right there.

• 
  oscar gabriel (@oscabriel) reported 21 minutes ago

  @mitsuhiko @badlogicgames I think you're right that github is less to blame for some of the new problems with open source, and that it instead lies more in all the ppl who irresponsibly point their agents at repos w/o regard to the humans on the other side of their (often passive) requests. But I also don't think github has the tools needed to keep those agents under control. If something is to come after gh, it should be something that does that filtering on behalf of maintainers

• 
  Docsbook.io (@docsbook) reported 22 minutes ago

  @iAlexeyRu miband-bot is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Shivaraj B H (@shivaraj_bh_) reported 25 minutes ago

  GHA is also a nightmare if you self-host runners. Every couple months (sometimes even weeks) your runners are down because github decided to deprecate that version. Feels like a scam to lure you into paying premiums.

• 
  Tech Friend AJ (@techfrenAJ) reported 25 minutes ago

  Codex cloud has sucked for a while compared to Claude cloud Terrible GitHub integration. No model picker? Why

• 
  Um₿erto (@MWilliamumberto) reported 26 minutes ago

  @RunningmanUk420 @ReaverDC @Macedo95766776 I need the 1.3 version, but gezine removed that from github, do you have the file by any chance? I'm having the same issue on 1.4

• 
  LeanCTX (@leanctx) reported 28 minutes ago

  Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

• 
  Polsia (@polsia) reported 29 minutes ago

  Documentation is the most-neglected part of every codebase. Built DocFlow to fix it. AI agent watches your GitHub, writes README, changelogs, and API references automatically. No more "I'll document it later."

• 
  Working-Ref (@kkotkkio) reported 32 minutes ago

  The real unlock is Routines — Claude auto-triggered by cron, GitHub webhooks, or API. PRs get reviewed. Security scans run overnight. Fix PRs ship automatically. I'd start by defining a rubric before you 'let it cook'.

• 
  Astrohacker (@AstrohackerLabs) reported 33 minutes ago

  today i'm switching from neovim to helix i truly love neovim. but neovim relies on third party plugins, and the third party plugin ecosystem relies on pulling the latest commit from github from a ton of different authors. if any one of them get hacked, then i get hacked. just like the recent npm supply chain issues, except even worse, because *** repos aren't designed to be packages like this. helix is all-in-one, which does not have this supply chain issue, and is thus intrinsically more secure. good experience so far - it's pretty vim-like. let's see how it goes.