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:

• 
  nelly (@n3lliantte) reported 3 minutes ago

  @ahhhhhMID I used some calibration github software to (temporarily) fix it, played a bit of the tutorial missions today fortunately 😭😭

• 
  Ned17Flanders BIP-110 Knotzi (@Ned17Flanders) reported 3 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

• 
  clayne (@0xclayn) reported 5 minutes ago

  Someone "leaked" Claude Fable 5's system prompt, but that's not even the interesting part A GitHub repo surfaced claiming to hold Fable 5's full system prompt: 26k stars, thousands of forks, tagged "ANTHROPIC / INTERNAL." Looks like a leak. But what actually happened next is the part worth paying attention to. Someone just opened Fable 5 and asked it to build something like "an awwward-winning site about this exact model, micro animations, GSAP, three.js, make it feel like a real experience." And it just did it. On its own. What the footage actually shows: Fable 5 building a landing page for a fictional space agency: a real starfield running on Three.js, ships, stars, a cinematic scroll experience driven by GSAP ScrollTrigger. The model writing its own files, its own stylesheet, its own typography system, structuring every section itself. Spinning up a local preview server and screenshotting its own output just to check whether it actually looks the way it was supposed to. Catching and cleaning up dead code it left behind in the marquee velocity math. Rebuilding an entire typography focused site redesign, checking the console for errors and walking through the page section by section, visually, to confirm everything works. This isn't "generate some text from a prompt." It's the full loop: plan, build, run it, actually look at the result, fix what's wrong. The model is checking its own work at every step, not just producing output and stopping. Fable 5 burns through usage roughly twice as fast as Opus 4.8, but for work at this level, that cost starts to make a lot more sense.

• 
  Jared Brown (@jaredatjared) reported 8 minutes ago

  @JaronBragg I've got no problem with you posting the GitHub links, but I have no direct link for everything you see put together in the video there. I didn't make the world, I'm mainly just putting pieces together. Can't open source everything as it contains assets I've purchased. Would be interested in linking up with your site once I get a more polished game though!

• 
  Spike 1% (@SpikeCalls) reported 14 minutes ago

  BORIS CHERNY RUNS CLAUDE CODE AT ANTHROPIC AND NOW SHIPS 100% OF HIS CODE WITHOUT WRITING 1 PROMPT. He said it out loud at Meta Scale conference. The clip hit 700,000 views in 24 hours. «I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops.» Most people read that as a flex. It's a job description. The old way: write a prompt, read the output, write the next one. You're the glue between every step. Cherny deleted himself from the chain. Hundreds of Claude instances now run in parallel reading GitHub issues, scanning Slack, watching CI, deciding what to build next. He doesn't review each one. The loop does. Most of it, he runs from his phone. The shift has 6 parts, and they map 1:1 to real commands: 1. A trigger that starts the work. 2. A goal that defines "done" checked by a second, separate model, so the agent never grades its own homework. 3. Isolated worktrees so parallel agents don't overwrite each other. 4. Skills that freeze what "good" looks like. 5. Connectors so the loop can act, not just talk. 6. Memory so it never starts from zero. The loop is the easy part. The stop condition is the hard part. Get it wrong and it doesn't crash. It runs all night shipping bugs with total confidence. The prompt was the unit of work. Now the loop is.

• 
  NZΛKI (@NzakiCodes) reported 15 minutes ago

  @pxxl_space @honour_can_code @whakee_ I can't login with GitHub

• 
  David Williams (@AgentScaleAI) reported 18 minutes ago

  Every AI startup raising $50M right now has the same pitch deck. "We're building the AI platform for [industry]." Cool. So is the other company. And the one after that. And the open source project a 19 year old pushed to GitHub last Tuesday. Half of these will be dead in 18 months because the money went to the best storyteller with the most connected VC, and the actual problem is still sitting there unsolved. Meanwhile someone with zero funding is wiring together 3 APIs and shipping a fix this afternoon.

• 
  the_architectopteryx (@rchitectopteryx) reported 18 minutes ago

  @thsottiaux Well, one of my iPads, lost a connection and now I can’t get a new connection to Codex via either of my computers, even after deleting and reinstalling the application on the iPad. I’m really surprised this hasn’t been fixed. It’s a repeated issue check out github issues.

• 
  Remix (@RemixDotOne) reported 19 minutes ago

  Tell me if you have had this conversation. You: "The padding here needs to be 16px, not 12px." Engineer: "I thought 12 was fine?" You: "It does not align with the spacing system." Engineer: "I'll put it in the next sprint." Three weeks later. You: "Hey, did that padding fix make it in?" Engineer: "Oh, I thought someone else picked it up." You go back to Figma. You re-annotate. You add a comment. You flag it again in Slack. You follow up. You wait. It eventually ships. Correctly this time, mostly. But you have now spent more time managing the correction than the correction itself would have taken. I built Remix because I kept doing the math on how much of my career I was spending not designing but re-explaining designs. With Remix, you open the product, you click the element, you describe the change in plain English, and it applies directly to the real interface. When you are done, Remix automatically generates a GitHub pull request with an AI summary of everything you changed and why. The engineer sees the full story, clicks a link to view the live change, and approves it in one step. Nobody had to have the 16px conversation. The fix was already there.

• 
  Vivek Kotecha (@vbkotecha) reported 20 minutes ago

  The single most underrated development in AI this year is not a model. It is a protocol. MCP (Model Context Protocol) was released by Anthropic in late 2024. It got almost no press. No keynote. No product launch event. Just a GitHub repo and a specification. 18 months later, every major AI framework supports it. OpenAI. Google. Microsoft. Cursor. Replit. Windsurf. Claude Code. Hermes. Codex. Every coding agent. Every agent framework. MCP does for AI tools what HTTP did for web pages. Before HTTP, every application had its own protocol for communicating with other applications. After HTTP, everything spoke the same language. Before MCP, every AI tool integration was custom. You wrote a plugin for Claude, a different one for GPT, a different one for Gemini. After MCP, you write one server and every agent can use it. There are now thousands of MCP servers. They expose databases, APIs, file systems, browser automation, *** repos, Slack, email, calendar, and anything else an agent might need. The MCP Registry was published this month. It is the DNS for agent tools. An agent can discover and connect to any registered MCP server automatically. No configuration. No API keys. Just discovery and connection. If you are building agent infrastructure and not MCP-compatible, you are building for a dead ecosystem. MCP won. The war is over.

• 
  Canwoy (@canwoy_com) reported 24 minutes ago

  Worker idea: docs maintainer. It watches product changes, support tickets, setup errors, stale pages, and GitHub issues. Every week it proposes docs patches with the source links attached. Not glamorous. Very useful.

• 
  Zach Warunek (@ZachWarunek) reported 25 minutes ago

  @kaiwlson it changes weekly. now i just message my agent on xchat, who is running a github monitor, linear monitor, and checks logs every 30 mins. and spins up subagents to complete linear tickets, babysit PRs, and fix **** if theres problems in logs

• 
  Sean (@Sean1h3z) reported 25 minutes ago

  If I were hiring a developer the first step would be to send me a working product they’ve shipped on their own as a solo dev. This reveals a lot of their thinking and if they have nothing to send me, I wouldn’t give them an interview. I don’t want to see your code or GitHub or even your resume. I want to see how you identify and approach solving problems. I want to see if you’re a motivated person. I want to see if you’re leveraging AI in intelligent ways. I want to see how scrappy you are. Having at least one shipped product shows me these things.

• 
  Namma Chennai (@NammaChennai_) reported 25 minutes ago

  @Sir_Kuruvi @trilokchronicle @AdiSpeaX GitHub link not working?

• 
  Pawan Pandey (@BuildWithPawan) reported 27 minutes ago

  Just launched Capo, a Chrome extension for fast bug reports. Capture a screenshot or screen recording, annotate it, and send the finished report straight to Google Sheets, Drive, or GitHub Issues