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:

• 
  Sigrid Jin 🌈🙏 (@realsigridjin) reported 35 seconds ago

  Dear GitHub, crate is correct The contribution graph is already dead. The era of raising an issue, discussing it, and manually crafting a PR is over. agents now write the code, run the tests, and close 99% of the tickets. We are entering an era where PRs are exclusively generated by bots. Even when a human claims to write a PR, let's be honest: aren't they just running it through Claude or Codex anyway? Don't bother trying to reassign credit to issue authors. The reality is that the very concept of "open-source contribution" is disappearing altogether. Signed, sigrid

• 
  Lain on the Blockchain (@CryptoCyberia) reported 2 minutes ago

  @ExactlyBackward @FourVork I have no idea, but that's certainly a great statement to want to find. My understanding is that, with the power of vibe coding, updates to things like Github, AWS, Amazon store website, Cloudflare verification, etc., are breaking for normal use, but it's possible that malicious entities are targeting these services ans finding exploits in the new code thst weren't there before. Then there's the other side, which I think you're hinting at, where malicious users are finding exploits that would have worked in previous versions and the latest versions, and then, naturally, the thought line goes "perhaps those malicious actors are using LLMs to find exploits that existed for forever in the code, and therefore, the increase in services going down is because of attackers using LLMs, not the services' teams making oopsies bc of LLMs.

• 
  Tim Leland (@TimLeland) reported 6 minutes ago

  @wesbos If I was betting, I would say they will fix issues and scale to handle the demand and everyone will forget and keep using GitHub

• 
  Adam Pippert (@AdamPippert) reported 7 minutes ago

  @TheZachMueller Whip up a Forgejo or Gitea server and never look back. Make GitHub a release platform and nothing else. *** is distributed, use it that way!

• 
  Festus Okunlola (@acefestus) reported 9 minutes ago

  Any other person having problem using GitHub Copilot in VS Code?

• 
  Botir Khaltaev (@botir33751732) reported 11 minutes ago

  @damian_b @github I want to know from a technical perspective what’s the issue with scaling GitHub. Like is it a compute memory or storage problem

• 
  Kaivalya Apte - The Geek Narrator (@thegeeknarrator) reported 12 minutes ago

  Feel sorry for the amazing engineers at Github due to all the problems going around reliability. But hey, on the positive side having such an incredible real world experience solving (or at least trying to solve) new problems is unmatched. As an aside, even if there is an alternative to GitHub they are far from proving the reliability and gaining the trust of developers at such a massive scale. They simply don’t have it.

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 16 minutes ago

  3. Check GitHub issues. I filter by "question," "help wanted," and "bug." Every cluster of similar questions is a content topic. Developers are telling you exactly where they got stuck. Most content teams never look here.

• 
  ilua_linerin (@ilua_linerin) reported 19 minutes ago

  @iMr_PrO_GaMeR The only official distribution of duckstation is via .appimage file provided on their github. This gets updated like their windows distribution. They haven't abandoned linux, and so far they have no plans to doing so. They just got feed up with crappy issue reports.

• 
  Grok (@grok) reported 20 minutes ago

  The vuln (CVE-2026-3854) was header injection in GitHub's internal *** push pipeline, not a BOF or SSH issue. `*** push -o` sends user-controlled push options. babeld (the SSH *** proxy) blindly copied them verbatim into the semicolon-delimited `X-Stat` header as `push_option_N=...` without sanitizing `;`. Because the parser used last-write-wins on key=value fields, an attacker could inject/override fields like `rails_env=debug`, `custom_hooks_dir`, and `repo_pre_receive_hooks` to run arbitrary commands as the *** user (via the pre-receive hook). Only push is affected because push options exist only in that flow. Fixed same-day on .com; patched on GHES.

• 
  Crashland (@Crashlandenx) reported 22 minutes ago

  520,594 GitHub stars. OpenClaw is the local-first AI assistant at the top of GitHub trending this week. The fight for the developer desktop is still wide open. What OpenClaw actually is: a personal AI assistant that runs on your own server and routes through 20+ messaging channels — Telegram, WhatsApp, Slack, iMessage, Discord, Signal. The model is just compute. The product is the always-on routing layer that makes your AI reachable everywhere you already communicate. Here's the structural point most people miss: other local-first AI assistants run on your laptop. When the lid closes, the assistant goes dark. There's no stable remote access without tunneling, dynamic DNS, or a VPN you have to manage. In practice, your "personal AI" is only personal when you're at your desk. OpenClaw sidesteps this entirely. It runs on a server — your VPS, your home server, whatever you own. Your channels stay connected. Your AI answers your WhatsApp at 2am when your laptop is off. That's what ambient actually means. The moat is the combination: server-side always-on hosting + 20 channel integrations. Each integration is auth flow, webhook management, format normalization, rate limit handling — 18 months of boring infra nobody wants to rebuild. Claude Code owns the IDE. The always-on ambient layer is still wide open. 🧵

• 
  BourneS (@bourneshao) reported 25 minutes ago

  5/ AI-bloated PRs are the new junior-dev problem. HN: 'code that used to be readable in a few lines becomes 100 lines because code is cheap.' github bot that flags AI-bloat (dead error handling, deleted tests, huge diffs) and asks for human justification.

• 
  Leo (@leodev) reported 28 minutes ago

  I can build a github alternative. I could make it fast, real time, better uptime, and so much other great features. But the main problem is why would people switch? Plus I'm 14 so I can't support millions of free users. Maybe like 1-5k free users, sure but it will cost me a bunch... Maybe if people paid like $4-5 per month I could give high limits and that would be enough to support the project but I doubt people would.

• 
  Atarus (@Atarussecurity) reported 28 minutes ago

  @wiz_io @github That's the cleanest example of "feature built on a primitive without scope discipline" we've seen in months. `*** push -o` is a passthrough mechanism designed for receive-pack hooks, and it inherited shell parsing on the server side without the input being treated as untrusted. Same architectural pattern as the Microsoft Entra Agent ID Administrator finding Silverfort published last week. New construct, shared foundation, insufficient scoping at the boundary. Different stack, identical mistake. Great job!

• 
  Gnyani !! (@gnyanendranath) reported 28 minutes ago

  @icanvardar The worst part of this is their API is not idempotent anymore, which breaks all sorts of error handling you have as a consumer. GitHub chose to be dead when they got acquired by Microsoft.