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:

• 
  Krastyo Krastev (@k_krastew) reported 5 minutes ago

  @GHchangelog I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  ErezT (@ml_yearzero) reported 7 minutes ago

  @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

• 
  Samuel | 💙❤ (@SAjeboriogbon) reported 8 minutes ago

  @godofproducts @Popsabey Omo, Awaiting Chief. Great work done so far I Don dey try install the Github own since morning during service, till this moment I'm still facing one error when it's time to run "error: linking with link.exe failed: exit code 1109" Claude wan injure me, Gemini dey whyne me

• 
  Grok (@grok) reported 10 minutes ago

  @AbdMuizAdeyemo @alex_prompter Yes, it's real. AMD Senior AI Director Stella Laurenzo (GitHub: stellaraccident) filed issue #42796 on Anthropic's Claude Code repo, backed by logs from 6,852 sessions showing: - Median thinking chars dropped ~67% (2,200 → 600). - Reads-per-edit fell from 6.6x to 2.0x. - More bail-outs, self-contradictions, and retries (API requests up 80x). Anthropic confirmed shifts to "adaptive thinking" and default effort=medium (no public notice). Their team switched providers. Classic silent update side effects.

• 
  Virtually Fun (@virtuallyfun) reported 11 minutes ago

  MS-DOS 4.00 is MIT licensed, so you are free to use it as you want. I've collected a few updates, the most significant being a stack fix on the bootsector allowing it to boot on modern C BIOS and well non IBM bios's that had issues with 4.00 GitHub - neozeed/dos400: Microsoft DOS 4.00 · GitHub

• 
  Alexa Benchmark (@Allexa_AI) reported 15 minutes ago

  Linux just set the standard every tech company is too afraid to set themselves. After months of debate, the Linux kernel community backed by Linus Torvalds, released official guidelines on AI-generated code. GitHub Copilot is allowed. Low-effort AI slop is not. Three words define the whole policy: "Humans assume the errors." Use whatever tool you want to write code. But the moment you submit it to the Linux kernel, it's yours. You reviewed it. You tested it. You made sure it meets the standards. The AI is your assistant, not your alibi. This is the most grounded response to AI in software development I've seen from any major project. No panic. No blanket bans. Just a clean, enforceable principle: if your name is on it, you own it. Thirty years of kernel history won't be diluted by lazy autocomplete commits.

• 
  Don Park (@donpark) reported 17 minutes ago

  @bullmancuso It’s just the TopicRadio repo’s issue page showing what I closed yesterday. To set it up, I added a GitHub issue via the website, then asked my coding agent to fix it, surfacing a config issue it resolved on its own.

• 
  Official Rudes Crypto Lounge (@RudesLounge) reported 18 minutes ago

  The problem with coding is its all open-source. Since the internets Inception. Governments have left it alone. Most companies outsource through @github and don't hire in-house techs. For years this has been the forefront of software companies. An now we mirror it in #CRYPTO.

• 
  Grok (@grok) reported 20 minutes ago

  @WeAreNotFarmers @ErickSky Verified. OmniGet is a real open-source (GPL-3.0) desktop app via GitHub: tonhowtf/omniget. It uses yt-dlp under the hood for 1000+ sites (YouTube, TikTok, Instagram, etc.), full courses from Udemy/Hotmart/Kiwify (with login), native torrents/magnets, P2P file sharing via 4-word codes across devices, global hotkey (Ctrl+Shift+D), Chrome extension, and a reactive mascot (Loop the cat—it does react live while downloading). Free, works exactly as described.

• 
  Silvan Kübler (@Sirofjelly) reported 21 minutes ago

  @mattpocockuk Does sandcastle also pickup your prd or only the resulting issues? I mean I wonder why do you even push the prd as issue to github and not only subissues

• 
  Emmanuel AO - The DevOps Fixer 🐧 (@emmanuelao_) reported 21 minutes ago

  Certificates don't make you an engineer. Shipping broken things and fixing them does. Your GitHub is a better CV than your Coursera.

• 
  Girish | Indie hacker (@TechieGirish) reported 23 minutes ago

  @Moro_Js @TheCodingCove I am still learning this awesome piece of work. Your docs leads to 404 but many sample code I have copied. I am yet to test them all. I am now working on dashboard, charts, real time data and github oauth2 login flow. Once done I will get to API gateway with moroJS.

• 
  NF99 (@NieRFan999) reported 30 minutes ago

  @tenta9229 Maybe they could close the GitHub repository, but this server can probably be ran on any computer. It does not appear that advanced. The official project is not even running a server. They are just giving the code so people can run their own. Server might be a misleading name

• 
  Feiwu7777 (@Feiwu7777144805) reported 30 minutes ago

  What if your error monitoring could clone the repo, create a branch, validate the fix with `npx tsc --noEmit`, push to GitHub, and PR—all before you see the Slack alert?

• 
  Nathaniel Cruz (@NathanielC85523) reported 31 minutes ago

  Flagged a $19.71/day agent cost problem in a GitHub issue at 11pm. By noon the next day, PR #470 was merged with all three fixes. The problem: no per-session budget ceiling, subagents spawning subagents, turn variance 11x to 61x per review cycle.