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:

• 
  Nav Toor (@heynavtoor) reported 2 minutes ago

  There is a GitHub repo that defeats Google's Play Integrity check. 61,030 stars. GPL licensed. Pushed eight days ago. The repo is called Magisk. It roots your Android phone. It hides root from banking apps. It runs Netflix on a phone the Play Store says is uncertified. It passes the same fraud detection Google built to stop it. Here is the part that makes no sense. The man who built it is John Wu. He has been maintaining Magisk for nine years. Since November 2023 he has been a Senior Software Engineer at Google. On the Android Platform Security team. The exact team that builds Play Integrity. Google hired the person who defeats their root detection. He still ships the tool that defeats it. The repo is still online. It has not been taken down. For nine years. Do not install it. Your phone is supposed to belong to Google. (Link in the comments)

• 
  top10.dev (@Top10_Dev) reported 7 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Yarchi (@undefinedKi) reported 7 minutes ago

  BORIS CHERNY, THE CREATOR OF CLAUDE CODE, JUST SOLVED AI'S BIGGEST PROBLEM. HE STOPPED PROMPTING CLAUDE AND STARTED WRITING LOOPS THAT RUN IT 24/7 The guy who built Claude Code doesn't prompt Claude anymore. He writes loops, and the loops do the prompting. It's called loop engineering. Here's what it is and how to set it up. A loop is a system that wakes itself up, finds work, does it, checks it, and repeats, while you watch instead of type. In Claude Code it's three built-in commands: > /loop runs a prompt on an interval. Example: /loop every 5 minutes, check for new GitHub issues and handle any that come in. > /goal makes the agent work until a condition you set is true, with a separate model grading the result. Example: /goal build this feature until all tests pass. > /routines are scheduled jobs. Example: every hour, wake up, read the spec doc, and do the next task. The fastest way to start: write a simple task list in a plan.md file, then tell Claude "use the loop skill and work through plan.md one task at a time." It sets up the /loop itself, does the first task, validates it, wakes itself for the next, and reports back when the list is done. You never write the loop prompt by hand. Three rules so it doesn't burn your budget or ship garbage. One, split work across separate sessions instead of looping in one (a long /loop bloats your context and overwhelms the model). Two, use a cheap model like Haiku for planning and a strong one only for the actual code. Three, keep a human checkpoint on anything that ships, never let it run all night unchecked. Bookmark this

• 
  YNWA🐦‍🔥 (@YNWAcrypto) reported 10 minutes ago

  The problem isn’t subtle. GitHub Sponsors has paid out ~$50M total since 2019. core-js: 9 billion downloads, running on half the top 10k sites on earth. Its maintainer was making ~$600/month when he called open source “fundamentally broken.”

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 10 minutes ago

  @softgaypaws @sillyandsunny no idea tbhhh, i found it like 2 years ago lurking thru github, so far it never gave me problems, at least none that i noticed

• 
  bek※ (@ebubekirttr) reported 11 minutes ago

  @Themadhushaw01 @0interestrates Yeah, but the thing is, I am not working on github and I don’t want to use it so any other repository support would be better like gitlab

• 
  Mug Club Boutique (@UsernameAndStuf) reported 12 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  Dmytro Virych (@dmytrovirych) reported 14 minutes ago

  I’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀

• 
  Iman (@RealKingiman) reported 14 minutes ago

  @ClaudeDevs Fix the auth bug with GitHub where I have it keep disconnecting and reconnecting GitHub every time

• 
  Asteri (@Asteri_eth) reported 17 minutes ago

  A $20 CLAUDE SUBSCRIPTION CAN TURN INTO A FULL AI TEAM IF YOU STOP USING IT LIKE CHATGPT Most people still use Claude like a smarter search bar Ask, copy, close, repeat tomorrow. Skills change that A skill is just a folder with a SKILL.md file, but inside it you can package an entire workflow once: PRDs, refactor plans, GitHub issues, code review, TDD, docs, marketing research, SEO, sales strategy and multi-agent orchestration That is not "better prompting" That is installing labor The article lists 50 Claude Skills with repos and install commands, from Anthropic’s official collection to Matt Pocock’s skill library and SkillsMP with 66k+ community skills The useful part is not the list It is the shift from asking Claude to remember your process to giving Claude the process already packaged You do not explain the same workflow 50 times You encode it once The model provides intelligence The skill turns it into labor Check full article below

• 
  Yiqing Xu (@xuyiqing) reported 20 minutes ago

  @Faylosophe Certianly. Could you file an issue on the Github page?

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 20 minutes ago

  @CryptoPatel Hsiao-Wei’s exit follows a 30% drop in EF-funded GitHub commits YTD (per Santiment). The real shift? Funds now focus 60% on L2 R&D vs 30% in 2022. We track this daily—breaking it down in our quarterly reports. Follow for the data before the narrat...

• 
  Moez Zhioua (@MoezZhioua) reported 22 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 25 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  Andy Wheeler (@CrimeDecoder) reported 28 minutes ago

  For academics, this is entirely open source by its nature. If you right click on the page and view the source, you can see exactly how everything is created. (Hence a downside of WASM, there is no way to hide it if you wanted it to be locked down, like in a paid app.) It can also be deployed on a free static site. So you could deploy it via GitHub pages for free if you wanted to. You don't need to worry about a server at all in this setup. This could easily scale to databases with 1 million plus rows, and works just fine on a cell phone.