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:

• 
  Andrew Kuncevich (@AndrewK404) reported 2 minutes ago

  Automatic generation of high-quality benchmarks Data for coding agents is scarce. Two pipelines invert the task: instead of searching for tasks, they produce them ① SWE-smith — bug factory Take a working repository -> intentionally break a function until a test fails -> then ask an LLM to write a “human” GitHub issue for that bug. The obvious risk is data leakage ② EnvScaler — environment factory Real tool APIs are closed, and LLM-simulated ones hallucinate. So the environment is synthesized as a real Python class: deterministic state, methods = tools. Plus a validator for each scenario that checks the agent’s path, not just the final answer --- What matters much more is not the implementations themselves, but the intuition behind them: ① You can generate benchmarks / eval cases directly from real data (for example, I constantly do this for RAG) ② It is important to look at the agent trace, not just the final answer (Specifically: did it call unnecessary tools? Did it call the required tools? Did it call the tools in the right order?)

• 
  Keisuke (@KeisukeIshikawa) reported 3 minutes ago

  CLAUDE FABLE 5 SYSTEM PROMPT AND ANTHROPIC CAN'T DELETE IT. THE GOVERNMENT PULLED THE MODEL. THE INSTRUCTIONS ARE STILL PUBLIC. 120,000 characters. 1,685 lines. 27,000 tokens. every rule anthropic gave the most powerful model it ever shipped sitting in a github repo with 40,000 stars what the leak actually reveals: → fable 5 and mythos 5 are the same model. the only difference is the safety filter layer on top → a persistent storage API most users never knew existed artifacts that save data across sessions → exactly how the copyright limits work: hard 15-word quote cap, one quote per source, then it paraphrases → the full child-safety instruction block, word for word → how it decides when to refuse vs comply, written out in plain english this is the closest thing to seeing behind the curtain that exists. if you ever wondered why claude talks the way it does, or refuses what it refuses, the answer isn't a mystery anymore. it's a text file the repo is run by pliny — the same guy who's been jailbreaking frontier models the day they launch for two years. CL4R1T4S now holds the leaked system prompts for chatgpt, gemini, grok, perplexity, cursor, and every model that matters the original post hit 700,000 views in 48 hours. the repo gained thousands of stars in a weekend here's the part anthropic can't fix: the government can force a model offline in three hours. it cannot un-leak 120,000 characters that already live on 40,000 forked machines the system prompt is the actual product. the weights are the engine, but the prompt is the steering wheel. and the steering wheel is now open source whether anthropic likes it or not we are watching the last secret layer of frontier AI get pried open one leak at a time follow and bookmark before the next wave figures it out

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

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

• 
  Dmytro Virych (@dmytrovirych) reported 8 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.” 🚀

• 
  HARJGTHEONE DBA (@HARJGTHEONEDBA) reported 10 minutes ago

  “SpaceX investors who bought shares in the last four days got diluted by 3.4% before they understood what they owned. The IPO was literally the printing press for the acquisition. Now look at what he ACTUALLY bought: Cursor's market share among enterprise customers has been collapsing. According to spending data from Ramp, it fell from 41% in June 2025 to 26% in May 2026, bleeding ground every month to GitHub Copilot and Amazon Q. The smart money knew. Andreessen Horowitz, Thrive, and Nvidia were about to lead a round at a $50 billion valuation, which they already considered aggressive. Elon paid 20% more than that for a company actively LOSING the race. He paid premium for declining momentum. And he did this because his own AI division was in trouble. “ @SpaceX

• 
  Ben Canning (@benhackshealth) reported 11 minutes ago

  Spent today setting up home assistant in the gym, ran into an issue with the connection between the software that controls the LEDs around the mirrors. Found a 4 year old repo on github, downloaded it, updated the code, fixed the problem and now control the lights without having to get out of my seat... Am I a hacker now?

• 
  Jason Bloomer (@JasonABloomer) reported 16 minutes ago

  @yagiznizipli Pffff, what a scam Let me fix your advert; "show us your github so we can scrape all your repos and train our AI on your code, only for any decent ideas you've had to be taken from you and made ours, then handed off to our legal team to crush you." Sorry, I value my work.

• 
  Noonien Soong (@mlcarldev) reported 16 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

• 
  Sap ツ (@Sapronaut) reported 21 minutes ago

  i am having github withdrawal issues, man. its not that serious github, chill.

• 
  Mathieu A. (@zoontek) reported 24 minutes ago

  What are the most annoying bugs you still encounter with React Native? 👀 Please share GitHub issue links 👇

• 
  Retail Investors Capital Management (@isdeezthebottom) reported 25 minutes ago

  @zerohedge $ORCL refused to make the effort to comply with $MSFT’s request for a specific standard. Coming from $MSFT this is rich: from Plasma and regression bugs which where supposed to be fixed in 2024, to infecting everyone with Mini Shai Hulud and Hades trough VS Code and GitHub pipelines, to their private GitHub repositories being leaked and BitLocker being extremely easy unlock. Not to mention the need to change MFA mechanism because people would be locked out of their accounts and scammed to change Azure passwords by attackers 🤭and their security policy is: “responsible disclosure” - IE. Don’t say anything about vulnerabilities that might be exploited by attackers, even if there are ways to mitigate until they figure out how to fix them (in a few months or so, if not years). $MSFT can’t talk about “security” until they change their ways of thinking 🤤

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 26 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  revayz (@0xrevayz) reported 27 minutes ago

  Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model" Without CLAUDE.md the mistake rate is 41%. With proper rules it drops to 3% You don't need a better AI. You need better loops Most people still prompt one task at a time and fix the answers themselves. That means the human is still the loop Boris Cherny from Anthropic said it best: "I don't prompt Claude anymore. My job is to write loops" The shift is simple. Stop giving instructions. Start designing systems that run themselves: Discover -> Plan -> Execute -> Verify -> Iterate until it passes The 6 things that make loops actually work: -Automations that trigger without you -Worktrees so agents don't overwrite each other -Skills that load context instantly -Connectors to real tools like GitHub and Slack -Subagents where the checker is never the maker -Memory so the loop never starts from zero Prompt engineers ask AI for outputs Loop engineers design systems that produce verified outcomes A reliable loop beats a perfect prompt every time Stop being a prompter. Start being the loop engineer

• 
  rapaya (@rapaya) reported 28 minutes ago

  OpenCode connects to LSP so the AI gets your actual compiler diagnostics in real time — type errors, warnings, the full signal your editor sees. Terminal-based, 75+ model providers, 160K GitHub stars, open source.

• 
  Matt Teixeira (@matt_teeixeira) reported 29 minutes ago

  I failed after committing to GitHub for 186 days straight. My goal was to ship code every single day of 2026. No exceptions. And for 186 days, I did exactly that. Then a Saturday came and I just... forgot. Was it a vanity metric? Absolutely. But it represented something real: showing up every day, no matter how small the contribution. The upside is that the streak broke, the momentum didn't. 4,215 contributions this year. Every one was a problem solved, a feature shipped, a customer conversation turned into code. Building Deck has been one of the most rewarding things I've done. Every conversation with a product team trying to build better customer-led software reminds me why I started. The goal was never a green square on a chart. It was to never stop building. It's still day 1 🚀