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:

• 
  Miro Jomaa (@MiroJomaa) reported 4 minutes ago

  @marcba You dont have the check line by line but just look in github desktop the diffs, you catch some weird things. Problem is if one Ai does something stupid the others see it and do that too

• 
  Raj Singh (@mobileraj) reported 4 minutes ago

  Was asked how I think about the things I work on holistically. I break them into 3 buckets: 1. Random productivity hacks or experiments. These are usually an evening or weekend vibe-coding session. If something ends up useful or packaged enough, I’ll push it to GitHub. 2. More in-depth products with no intention of making money. I use these as playgrounds for learning and experimenting with AI. They can easily turn into 100s of hours of focused product + AI work, but they’re a great way to test workflows and hopefully build something useful for the world. Examples are GPT Food Cam and Speakrphone. 3. Things that can make money. These tend to be more deeply researched problems, often in a specific vertical, where there’s a clear user, buyer, and willingness to pay. A lot of what I build at work falls into this bucket.

• 
  Defileo🔮 (@defileo) reported 8 minutes ago

  🚨 55,000 STARS AND IT'S STILL COMPLETELY FREE. NO F*CKIN WAY THIS ISN'T A DREAM. Strix just hit 55,731 stars on GitHub (+10k stars in 1 week) > multi-agent team that hacks like a real attacker, not a scanner > every finding is proven with a real PoC, no false positives > solved 96% of XBEN web challenges for about $3 each > local live dashboard with agent graph, findings, and steering Authorized targets only, this thing actually breaks things to prove they're broken. Fewer words, more action, repo in the comments.

• 
  Ilya (@ilya__ker) reported 9 minutes ago

  Interesting stuff with microslop and @github If you run apt-get update in GitHub Actions, it’ll use an Azure mirror by default - which has been down for the past 2 days. Your job will sit there for an hour, time out, and you’ll get billed for it. And apparently, nobody really cares.

• 
  RICO (@RICO_Lumiere) reported 9 minutes ago

  Sorry to bother you out of the blue. I’ve honestly run out of options, and I heard you might be able to help with GitHub issues I can’t access, signing in just redirects back to login page, and my ticket(#4678706) hasn’t received a response Any help would mean a lot🙏 @moraes_c_

• 
  MystiqueMide (@MystiqueMide) reported 11 minutes ago

  /goal Build everything required, then run the full test and review cycle. Fix any issues you find and continue until all relevant tests, checks, and validations pass. Before making changes, read AGENTS.md and follow all repository-specific instructions. Repository rules: * Do not commit internal documentation, planning files, review notes, agent files, scratch files, or other internal-only artifacts. * Keep the public repository clean and production-ready. * Review the final diff before committing to make sure no internal files or unintended changes are included. * Use a concise, meaningful commit message that describes the actual work completed. * Do not use conventional commit prefixes such as feat:, fix:, docs:, chore:, refactor:, or similar prefixes. * Once everything is verified, commit the approved changes and push them to GitHub. IMPORTANT: When you reach the frontend work, STOP. Do not modify, build, redesign, or continue with the frontend. Wait for my explicit approval before proceeding with any frontend changes.

• 
  Harshit Sharma (@itsharxit) reported 12 minutes ago

  @cesp2099 Partially agree. Can’t speak for Linux, but on my end T3 Code feels way snappier than Codex Desktop. And “it only got famous because Theo is famous” hell no. His audience obviously helps, but that doesn’t magically get you that many stars. If you’re actually hitting these issues, a detailed GitHub issue with repro/context would probably be more useful. Gives them something concrete to fix, and everyone wins.

• 
  Tao Idr (@tao_idr) reported 16 minutes ago

  The scale of this issue is massive: 28.6M new secrets leaked on GitHub in 2025 alone (AI credentials up 81%). Threat actors harvest exposed keys in under 5 minutes. Median enterprise fix time? 94 days. This gap is where breaches happen.

• 
  Kaan (@kaanyagci) reported 16 minutes ago

  @robdvr This is more like a CI optimization issue than a vendor issue. Before moving to another vendor, I'd recommend trying: 1) A self-hosted runner with those packages pre-installed 2) Custom images instead of the default GitHub runner image 3) Caching the apt packages

• 
  AI Reality No Slop (@airealitynoslop) reported 20 minutes ago

  Cursor shipped Origin on Sunday and every headline called it a GitHub alternative. Their own changelog is more careful than that, and the difference matters. Origin does two things. You can create repos on it, which Cursor genuinely hosts. Or you can sync repos you already have on GitHub, and for those, in their words, pushes keep going to GitHub, which stays the source of truth for anything started there. So for code that already exists, Origin is a very good client sitting on top of GitHub rather than a replacement for it. PR comments sync both directions, which is the useful part and also the part that needs GitHub to be up. Which it wasn't. GitHub degraded the same day Origin rolled out, 14:34 to 20:40 UTC, and Cursor's own status page lists Origin among the affected services. Along with Automations, Cloud Agents, Review Agents and Codebase. None of this makes Origin bad. New repos hosted there are a real alternative, and meeting people where their code already lives is a sensible way to launch. It just means the thing being called a GitHub alternative had a six hour outage on launch day because GitHub had one.

• 
  Junead Khan (@junead_kh) reported 20 minutes ago

  I used to be on-call for Azure at Microsoft, and GitHub taking 8 hours to recover from a “simple” failure makes perfect sense. Azure is built on top of Azure. So the person on-call starts with one broken service, pulls in another team, who pulls in another, until the one person who really understands some dependency is asleep 8 time zones away. A few hours later you finally know what’s wrong. Now you still have to change production without making it worse. That’s how a 10-minute bug becomes an 8-hour outage.

• 
  Tech gets old (@GetsTech) reported 21 minutes ago

  I asked Claude to autonomously complete about 15 very simple github UI issues overnight, do all the work in a single branch, and commit it all in a single PR. When I woke up it did four of them and had decided that was enough and gave me pathetic reason why it wouldn't do more. Brutal.

• 
  Alessio Persico (@alepbuilds) reported 25 minutes ago

  weird that there's a "make money reading github issues" button and nobody's pressing it (5+ companies complaining about the same problem on github = budget. an unfinished tool sold for $5k doing this)

• 
  Brandon Roberts (@brandontroberts) reported 26 minutes ago

  Yesterday GitHub was down basically all day Today they're pushing stacked PRs on here How about easing up a bit?

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

  GitHub ate my Monday. Eight hours. Couldn’t merge. CI was dead. Copilot wouldn’t even sign in. Cursor’s agents went down with it. Claude’s been blinking out for weeks. At some point, outages stopped feeling like rare incidents.