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:

• 
  Fex (@Fex_23_) reported 2 minutes ago

  @LeonChaland @NXT4EU And no ZKPs wont work as advertised as stated in the Github Issue. You should read that one first

• 
  BullBear.News (@bullbear_info) reported 2 minutes ago

  @github Only if Universe fixes my broken CI pipeline. 🙃

• 
  Keeta Github Tracker (@KeetaCode) reported 4 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: node-rs 🔀 PR #30: Fix: Cleanup Crypto Issues 🌿 Branch: fix/crypto-issues → main 👤 Originally opened by: @sephynox 🧠 Overview: This pull request appears to clean up some internal crypto-related code so the Keeta node handles security functions more reliably, which matters because these low-level fixes can help avoid bugs in how the network verifies or processes data. The public description is brief: it says the PR “fixes various issues with cryptographic contexts” and links to issue #28, which mentions removing a verification function described as cryptographically weak. This appears to be a technical/internal update with limited public details. - It likely focuses on improving the safety and correctness of behind-the-scenes security checks rather than adding a user-facing feature.

• 
  BullBear.News (@bullbear_info) reported 4 minutes ago

  @github Only if the keynote fixes my broken CI pipeline. 🤷

• 
  Hot Aisle (@HotAisle) reported 5 minutes ago

  Wow. I used to do so many hacks to get this functionality. I once built a cf worker caching layer in front of github so that I could have 30k servers downloading private repo binaries without getting rate limited by GH. Eventually hit one of cf’s undocumented rate limits and had to get an account exec to fix it.

• 
  Keeta Github Tracker (@KeetaCode) reported 8 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #388: fix history group without enrichment 🌿 Branch: fix/history-enrich → fix/atomic-swap-history 👤 Originally opened by: @lucasrosa90 🧠 Overview: This update appears to fix how the bot groups transaction history when extra lookup data is missing, which matters because it should help activity be tracked more consistently. The pull request is a draft with limited public detail, and it has no written description. Based on the title and commit messages, it also adjusts how transaction IDs are handled for both “enriched” and “not enriched” transactions, meaning records with and without added metadata should be treated more reliably. - This likely helps prevent some history items from being grouped incorrectly when full transaction details are unavailable. - “Enrichment” here seems to mean adding extra context or metadata to a transaction after it is first detected.

• 
  Mirosław Folejewski (Mirkotronics) (@Mirko_DIY) reported 9 minutes ago

  @tihenko_ In fact, a friend recommended this site to me about two weeks ago. Until then, I'd only used GitHub and Hackaday. Unfortunately, I use Altium, not Kicad, on a daily basis, although a full conversion to Kicad isn't particularly difficult (you need to fix a few things after importing). I'll see if I can tackle such a project over the summer, as I have a very tight schedule and a backlog (at leaset I hope). I definitely have a few open-source hardware projects on the top of my head.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 9 minutes ago

  FABLE 5 TOKEN WASTE IS ABOUT TO GET PAINFUL I tested a free fix that cut output tokens so hard it almost feels unfair. The Problem: → Fable 5 burns tokens fast when agents write long replies → Output tokens are the expensive part when you move to API usage → Most AI answers waste space on “sure,” “happy to help,” and 3-paragraph warmups The Fix: ✓ Caveman is just a rules file your agent reads before replying ✓ It makes answers short, blunt, and useful ✓ Code blocks, commands, file paths, and errors stay untouched Real Test Results: → React rerender bug answer dropped from 1,349 tokens to 324 → 5 real GitHub questions tested directly on Fable 5 → Average saving: 69% fewer output tokens → Total cost dropped around 37% Why This Matters: ✓ Works with Claude Code, Codex, Gemini, Cursor, Windsurf, Cline, Copilot, and more ✓ Installs across one agent or 30 agents ✓ Modes include light, full, and ultra ✓ Commands include caveman commit, caveman review, and caveman compress Same brain. Less waffle. Lower token bill. This is how you use stronger agents for longer without paying for every useless sentence.

• 
  Wes Roth (@WesRoth) reported 10 minutes ago

  Mistral released Leanstral 1.5, also called Le Chaton L∃∀N, an open model built for formal reasoning in Lean 4. It solves 587 of 672 PutnamBench problems, reaches 87% on FATE-H and 34% on FATE-X, and improves the cost-performance frontier by solving advanced math problems at far lower budget than previous systems. Leanstral 1.5 is a 119B-parameter MoE model with 6.5B active parameters, a 256k-token context window, and open weights available on Hugging Face. Mistral also used it beyond math: an automated pipeline translated Rust code into Lean, inferred correctness properties, and flagged 47 violated properties across 57 repositories. Eleven were real bugs, including five that had not been reported on GitHub before.

• 
  Atharva (@attharrva15) reported 12 minutes ago

  @ivanburazin A guy ( i won't name) invited me for a talk for a freelance position (he saw my GitHub, might have liked me) and I prepared for it, studied his codebase, told my mum to not come in my room for 30 mins, and the guy never came, and ghosted me. I don't care if you don't wanna work with me, or you have problems- just ******* be clear.

• 
  Ned17Flanders BIP-110 Knotzi (@Ned17Flanders) reported 15 minutes ago

  @Scavacini777 They've blocked us all and muted the conversations. They think BIP-110 is censorship but they block all convo on github, reddit, etc. Call us names and try and use confusing terminology and lean into heuristics to make themselves sound smarter than regular people. Coredevs are the problem. V30 is malware. Run Knots and BIP-110 God Save Bitcoin GodWins

• 
  Max Chepurin (@maximchepurin) reported 16 minutes ago

  @Bobliuuu @mattpocockuk They are only listed there once there is some credible evidence that attackers are actually exploiting vulnarability not just cuz someone noticed potential security issue. At least thats how the one that you sent works(CVE catalog) Now consider this: - You install a package in your project. - You run your usual vulnerability scanner. Everything looks good. - You become the first person to encounter malicious code in that package. - You report it, it’s verified, and it becomes a known issue, but only after someone (you) already shipped it to production. - here comes the question again: why didnt you review the code manually? My argument is that simple. People blindly trust vulnerability scanners. They trust github. They trust popular opensource packages and any other pieces of software without reading a single line of code. But when it comes to AI-generated code, suddenly everyone acts like trusting it is fundamentally different and that every line must be reviewed. Double standard. Reviewing is important. And doing regular checks on the most inportant spots of your codebase is essential. But for everything else - you can build your harness, skills, hooks, guardraíls, to make AI generate code that already meets your standards without having to worry about every single line. Why not take this advantage? Its not 2022 when you copypasting snippets back and forth from chatGPT, AI can own your codebase now if you build the proper harness around it.

• 
  200 people murdered in Benue, 50 killed in Plateau (@AScully789) reported 26 minutes ago

  Every afternoon, Deepseek just goes crazy and breaks my project. the last time it took me 4 days to fix because Deepseek in Opencode had also not been pushing to my github repo even though that's expressly instructed in the Agents.md. I am just tired

• 
  Xavier Rivera (@XavierRiveraX) reported 28 minutes ago

  GitHub Agentic Workflows can be manipulated into leaking private repo data through a public issue comment, no credentials or org access needed. Noma Security named the prompt injection technique GitLost. The feature is still in preview.

• 
  Robin Delta (@heyrobinai) reported 30 minutes ago

  10 OPEN-SOURCE REPOS THAT CLONE ANY VOICE FOR FREE.. you've been paying for voice cloning every month when the exact same thing has been sitting on github.. for free.. running on your own machine no subscriptions, no limits, no servers that own your voice → Each repo clones a voice from seconds of audio → You write the text and the voice says it with your intonation → Everything runs locally, your audios don't go to any external server → Several support multiple languages and speed adjustment → Open source, free, no character or credit limits once you use these you'll never go back to paying Save these now👇