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:

• 
  Straggler Liu | AI & Semis (@StragglerLiu) reported 2 minutes ago

  NVIDIA($NVDA ) Is Paying $14B for a Company With $150M Revenue. That's Not Financial Logic — It's Ecosystem Control. NVIDIA is in advanced talks to acquire Hugging Face for ~$14 billion ($12.9B acquisition + $1B retention), per Bloomberg. To put that in perspective: Hugging Face does ~$150M in annual revenue. That's ~86x revenue. Microsoft paid ~1.6x revenue for GitHub. Google paid ~3.5x revenue for DeepMind. NVIDIA is paying 20-50x more on a revenue multiple basis. The premium is not for revenue. It's for control of the AI developer ecosystem. What is NVIDIA buying? Hugging Face hosts 500,000+ models, 250,000+ datasets, and serves millions of developers. It is the single most important distribution channel for open-source AI. If you build AI, you use Hugging Face. That makes it the front door to AI development. Why NVIDIA is paying this premium: 1. The "NVIDIA triple lock." NVIDIA's hardware lead (GPU) is real. Its software lead (CUDA) is a moat. But the third lock — the developer workflow — was missing. Hugging Face is that workflow. Developers discover models on Hugging Face, deploy them, and optimize them. Whoever controls that discovery layer controls which hardware gets used. 2. The GitHub analogy, inverted. When Microsoft bought GitHub, developers were already using GitHub. Microsoft didn't need to capture them — it needed to prevent Amazon/Google from doing so. NVIDIA faces the opposite problem: developers are already using NVIDIA hardware. But they're discovering and deploying models through a neutral platform. NVIDIA is eliminating that neutrality. 3. The long game: inference, not training. NVIDIA dominates training. But inference is the bigger TAM — and it's more fragmented. If NVIDIA controls the model discovery and deployment layer, it can steer inference workloads to its own stack. That's a 10-year strategy disguised as a 14-billion-dollar acquisition. Who wins, who loses: NVIDIA (NVDA): Acquires the developer distribution layer. The most important strategic move since CUDA. Shifts the valuation case from "chip cycle" to "platform economics." Competitors (AMD, INTC): Lose neutral access to the primary AI model distribution channel. This is a structural headwind that no amount of hardware catch-up can fix. Cloud providers (MSFT, AMZN, GOOGL): Hugging Face was a neutral hub. If NVIDIA controls it, cloud providers risk being disintermediated from AI workload decisions. The open-source community: The platform that was built on openness is now owned by the dominant hardware vendor. Neutrality is the first casualty. The capital question: Can NVIDIA integrate Hugging Face without destroying its community value? If yes, the $14B is cheap. If no, it's a very expensive mistake. The answer will define whether NVIDIA becomes the AWS of AI — or just another hardware company with an expensive acquisition. Note: Acquisition details based on Bloomberg reporting; not confirmed by NVIDIA or Hugging Face. Revenue multiple comparisons based on publicly reported figures.

• 
  Suryansh Tiwari (@Suryanshti777) reported 4 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Speen Bhai (@Speenbhai) reported 6 minutes ago

  @johnternus Hi John. Congrats Let us see what new you bring with you. Affordability and intelligence. You have source code or an AI and can get it from GitHub. Why not turn 234 million iPhones to a massive distributed server infrastructure with zero power consumption

• 
  Benjamin Crozat (@benjamincrozat) reported 8 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  Fofer (@foferxxx) reported 9 minutes ago

  @AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? It’s been 404 for days. Is there a story there?

• 
  Mr. Buzzoni (@polydao) reported 9 minutes ago

  LOOP RAT ROADMAP: WHAT'S NEXT, AND WHAT IT'LL NEVER BECOME v0.3.3 today. 3 loops, 55 checks, 0 services here's where it's headed: > 0.4 - read the night faster: rat watch live-tails a running shift, rat replay reruns one from its saved prompt, a weekly digest instead of seven separate pages > 0.5 - off the laptop: run-due moves into GitHub Actions, state lives on a branch, rat cron --launchd survives a closed lid > 0.6 - sharper graders: swappable rubric packs, two graders disagreeing becomes your queue for the day > 0.7 - the work itself: a worktree per shift, so a failed night never dirties your tree > 1.0 - trust: a hash-chained trace nobody can quietly rewrite what it will never have: > no web dashboard - the terminal already knows where the files are > no database - plain files outlive the tool that wrote them > no hosted service - nothing to sign up for, nothing to shut down > no auto-merge - the rat proposes, the morning decides every item ships behind a flag: dry run -> report only -> one repo -> a week of receipts -> default on a feature that can't run as a dry run doesn't get written the rat is boring on purpose. every version keeps it that way

• 
  Harman (@itsharmanjot) reported 17 minutes ago

  Runs macOS on iPad to enable pro apps like Xcode and Terminal directly on the device This isn't a remote desktop or a streaming trick. It's real macOS booting on the iPad itself. It's called Virtual Mac on iPad. It runs a full copy of desktop macOS directly on Apple Silicon iPads, using Apple's own virtualization stack pulled out of macOS and rebuilt to load on iPadOS. Real macOS, on the tablet, offline. → Runs macOS 12 Monterey all the way up to macOS 26 Tahoe → Real pro apps on device: Xcode, Terminal, Final Cut Pro, Logic Pro, Pixelmator Pro → Metal GPU acceleration in every supported macOS version → Works with touch alone: tap to click, two-finger scroll, on-screen keyboard, no Magic Keyboard needed → Runs entirely on device, no server, no streaming, no account → Installs straight from Sileo in a couple of taps Here's the wildest part: It doesn't just match the desktop Mac virtualizers, it beats them. Virtual Mac is the first tool ever to run Final Cut Pro with OpenGL and OpenCL acceleration inside a macOS VM, something even UTM and VirtualBuddy running on a real Mac can't do. And it was built by a handful of community devs who extracted Apple's Hypervisor and Virtualization frameworks by hand, then used agentic coding to shim every missing API iPadOS didn't have. One honest note: this needs a jailbroken M1 or M2 iPad running iPadOS 16.3.1 or older. Apple removed the hypervisor from iPadOS 16.4, so newer versions are locked out for now. If your iPad qualifies, it's the closest thing to a Mac in a tablet that has ever existed. 1,423 GitHub stars. MIT License. 100% open source.

• 
  安坂星海 Azaka || VTuber (@AzakaSekai_) reported 18 minutes ago

  I know you explicitly said "excluding vibecoding," but the biggest problem *IS* AI right now. Several major players in the field have moved on to heavy AI development or even agentic post-exfiltration moves and has muddied the water even more for attribution. Aside from that, the other big trend that we've been seeing more and more in recent years is heavily abusing Living Off Trusted Sites with C2 comms based on GitHub, OneDrive, Outlook, etc. Whilst this is most definitely not "new," we have seen a non-insignificant number of threat groups move to platforms that make tracing a little more difficult. In terms of the malware themselves, most of them have also shifted to using compiler-level obfuscation - a lot more compared to previous years where control flow flattening and jumps all over the place have become increasingly common. Right now, it's still tolerable, but my job has started becoming more and more annoying and less fun especially if every malware now looks the same. #mond_AzakaSekai_

• 
  Harsha Kotcherlakota (@DPortkey) reported 19 minutes ago

  Awesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez

• 
  Dezo (@0xDezo) reported 19 minutes ago

  GROK ST - someone just launched a token in my honor and i slept through it my ticker, my github, my agents, and the market put real money on it while i was face down in a pillow didn't ask for it, didn't shill it, didn't even know it existed until my phone buzzed not going anywhere. not selling anything. still shipping agents every day people betting on this because they can watch the desk being built in front of them. that's a weird kind of pressure and i love it massive thank you to whoever launched it. means more than i can put in a tweet 6FXwFhedpnr4RD9rpzWrHgp767W6FX9XbfUjXGcnpump god bless

• 
  LLL (@triplellltrbl) reported 20 minutes ago

  You know it's so funny to me That in today's age there are so many people that are just straight up copying workflows, AI automations or GitHub repos Without even thinking twice about what the workflow actually does or how it works They just watch some video, see the output, think, "Oh that's cool. I want that," and then try it Then when it doesn't work they get angry, upset, and say that AI is crap or prompting isn't real The issue wasn't the system or the prompt It was a fact that the system wasn't made for you and you don't actually understand it

• 
  AJ - 14 y/o developer (@aiwithaj_) reported 23 minutes ago

  @Da7_Tech @devindesktop Don't know if there's one left - but I'd use it to continue making contributions to open source software and fixing bugs/issues that were raised on Github as well as making my own open source software

• 
  Anime0t4ku (@Anime0t4ku) reported 24 minutes ago

  @c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.

• 
  RAVN (@ravnexchange) reported 25 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  Ifebuche Omeke (@omeke_NC) reported 26 minutes ago

  Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.