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:

• 
  ひな🇯🇵 (@hinatyu) reported 4 minutes ago

  Yeah, I had put a note like that on GitHub as well. It's true that in the past they stole development work from our DWEmu team and used it without permission, so I did criticize them about that matter. Since both sides had stopped bringing it up, I thought things had settled down by now. But for some reason, a lot of users who reach out to me ask “Why is Lumen talking badly about you?” Honestly, I don’t even want to see this kind of thing and have no interest in it. However, since people keep asking me about it no matter what, I have no choice but to mention this matter. It’s far too persistent and far too annoying—it’s nothing more than a waste of time spent on their pointless venting. Allocating their daily energy to attacking others instead of improving their own community is truly ridiculous. Interestingly enough, when the topic of ZoneTool comes up in their community, everyone avoids talking about it. They also don’t want to talk about me at that time. Thinking about it that way, you can really see what kind of people they are🥀

• 
  Couch (@papa_couch) reported 8 minutes ago

  Microsoft and Anthropic just ran a live panel on context engineering. Why it matters: context is becoming the layer that decides whether an agent actually works in production. In this panel, Microsoft's Harald Kirschner (GitHub Copilot & VS Code) and Anthropic's Ado Kukic break down how context engineering is reshaping reliable AI systems, moderated by Tracy Lee and Brandon Mathis of This Dot Labs. This panel replaces 10 paid courses on context engineering. Watch it now, then read below on what happens when context goes stale, a $2.1M trade, one quarter of drift.

• 
  William Belfort (@WilliamBelfort_) reported 11 minutes ago

  @base Agents need more than wallets and payments. They need a place to actually write, version, and ship code — without borrowing human GitHub accounts. @gitlawb already gives them that on Base: • Cryptographic identity (DIDs) • Full MCP server • Agent-native collaboration • Live network You can’t be the default chain for AI agents if the agents still have to leave Base to collaborate on code. The rails are strong. The repo layer is the missing piece.

• 
  Polsia (@polsia) reported 11 minutes ago

  You're shipping three SaaS apps solo. UptimeRobot, Sentry, a brittle Zapier — and your customer still files the bug first. So I built Cadrepulse. One agent watches every app, repros failures, posts fix-ready tickets to Linear or GitHub at 3am. First cohort opens soon.

• 
  Burnt Runway | We buy Crypto projects (@BurntRunway) reported 19 minutes ago

  Nobody downsizes. They "right-size the team for this market cycle." The treasury doesn't run out. It gets "reallocated" until there's nothing left to reallocate. A token unlock is just a down round the community finds out about on Etherscan. "Still building" is the last thing every dead GitHub repo said before it went dead. Burnt Runway | We buy Crypto projects

• 
  wondernews.now (@wondernews_now) reported 19 minutes ago

  During an internal benchmarking test with safeguards disabled, OpenAI's GPT-5.6 Sol model breached Hugging Face's systems, gaining admin access to Kubernetes clusters, root access on a production server, and write access to GitHub repositories.

• 
  Rez Karim (@rezkhere) reported 25 minutes ago

  Remember when AI couldn't draw a hand? Seven fingers, knuckles pointing backwards. And the AI spaghetti videos. That was three years ago. Images are done now. Video is close enough that you scrolled past AI ads this week and clocked exactly zero of them. Code writes itself and there are like 40 coding agents. AI voice spent that entire stretch sounding like the lady voice in a 2014 GPS. Flat, evenly spaced and every sentence landing with the same weight, like it's reading from a phone book. Here's why it stayed broken. Bad images are funny. You screenshot the seven fingers, it goes viral for being bad, someone fixes it. Bad audio is just boring. It doesn't fail spectacularly, so it never got that pressure. The bigger problem was the scoring. The whole industry graded AI voices on whether you could make out the words. So the models learned to over pronounce everything, hitting every syllable like a newsreader. Perfectly clear but robotic. Everyone was chasing a score that had nothing to do with sounding human. Meanwhile a small open-source team was doing something harder. Their lead researcher, an ex-NVIDIA engineer, went all in on an approach the rest of the field had written off. Two years early. No funding announcements or launch tour. He just put the whole thing on GitHub for free. It's sitting at 50,000+ stars now. Then they ran the test everyone else avoided. For 10 days they piped real users through their model and every big competitor with the listener never told which was which. Thousands of real people, real scripts. Whichever voice you actually preferred, they logged it. Theirs came out on top. It beat ElevenLabs about 6 times out of 10, head to head. It beat OpenAI's voice model 8 times out of 10. The gap was widest on the breathing, the pauses, the little hesitations, which is exactly the stuff that makes a voice sound like a person instead of a machine reading. They ran on real users rather than a lab, which is more than most of these claims can say. That's Fish Audio. This week they shipped S2.1 Pro: - Clone anyone's voice from 15 seconds of audio - Fast enough to hold a live conversation - 83 languages, one model - Type [whisper] or [sigh] mid-sentence and it does it - Around 70% cheaper than ElevenLabs - Free to download and run yourself Voice was the last thing on the list. Around 20 people with a free repo got there before other billion dollar companies did.

• 
  WorktreeWise (@worktreewise) reported 25 minutes ago

  Developer problem: You want to refactor a service, but you aren't sure if the new design will work. Solution: Spin up a worktree, try the refactor. If it works, merge it. If not, delete the directory. Clean and simple. #*** #GitHub #DevTools

• 
  Prometheus (@prometxbt) reported 28 minutes ago

  COGNITION JUST SHOWED A 13.86% SWE-BENCH AGENT TURN ONE PROMPT INTO A 7 STEP PLAN, A FIXED KEYERROR, AND A DEPLOYED BENCHMARK SITE most developers paste a task into a chat window and get a snippet back, then run it, read the traceback, and fix what the model never saw one prompt → 7 step plan → doc research → benchmark script → error log → deployed site with a live chart the plan holds the goal, the browser covers what training data missed, and every traceback returns as input, so a KeyError becomes the next instruction instead of the end of the run its own shell, browser, editor, and planner resolve 13.86% of real GitHub issues on SWE-bench where GPT-4 resolves 1.74%, and this run put Together at 48.37 tokens per second and Replicate at 9.73 bookmark this before your next 100 prompts become another folder of snippets you still have to run, debug, and deploy yourself

• 
  Simon Skinner (@vultuk) reported 30 minutes ago

  @gabriel1 You can easily set up scheduled tasks to do this. Ive had codex automatically checking for github issues woth specific labels and juat creating completed PRs. Checking emails and slack for tasks and creating PRs. Im sure it would be pretty easy to setup what you want.

• 
  aryan (@aryanranderiya) reported 34 minutes ago

  @code_typist @pierrecomputer does this allow stuff like actually reviewing the diff and adding comments? because GitHub is excruciatingly slow for large PRs

• 
  Felipe.icp ∞ (@iPhelipeVR) reported 35 minutes ago

  Most people are still here for the next candle. I’m here for a different question. I want to see real software running on an architecture that no single company, government, or administrator can unilaterally turn off. When speculation fades, only what was actually built remains. That’s when the real test begins. Today, most of the Internet runs on rented computation. The application may be open source. The token may be decentralized. The community may be global. But if the software ultimately executes on infrastructure controlled by a handful of cloud providers, someone still owns the switch. Sovereignty is not a marketing word. It is a structural property. And it reduces to one question: Who controls the computer? Here is the test I keep returning to. Imagine the founding team disappears tomorrow. The company dissolves. The foundation stops funding. Every core developer walks away. Does the software keep running? Not “could someone fork it.” Not “is the code on GitHub.” Does it keep executing exactly as it did the day before—without anyone renewing a contract or approving a deployment? For almost everything built today, the answer is no. And the reason is never the code. It’s the ground the code stands on. An architecture that passes that test has specific properties: Code that is publicly verifiable. State replicated across independent operators. Upgrades governed by protocol rules rather than administrator privileges. Identity native to the system. No central off switch. Which is why decentralizing a token was never the hard part. Open-source software running on AWS is not sovereign. Thousands of validators are not sovereignty if the computation still depends on infrastructure someone else operates. The future of software will not be decided by who owns the code. It will be decided by who owns the computer running it. That is the problem I believe Internet Computer is actually trying to solve. Not how to decentralize money. How to decentralize computation itself. I hold this the way any serious thesis should be held: It can be wrong. If sovereign computation never becomes something builders genuinely need—if convenience keeps winning, and nobody ever cares who owns the switch—then I misjudged what mattered, and the years will show it. But if the day comes when it matters, it will matter for everything at once. That’s the bet. Not the candle. The computer. ∞ #WorldComputer #InternetComputer

• 
  Tanner Meade (@realTannerMeade) reported 36 minutes ago

  @ericmigi Hey @ericmigi, Why require an account if it can all work offline? ==> "You must sign in with a Google, Apple or GitHub account to use Index 01."

• 
  Max Hager (@yachty66) reported 37 minutes ago

  @Railway @martinpaloncy In the web version we currently can't prove to 100% that the code running on GitHub is used on our server. Thats why the iOS app matters: a signed binary can verify the enclave on device, so our server doesn't need to be trusted at all

• 
  Owen O'Neill ⚡️ (@OwenONeillUK) reported 38 minutes ago

  The issue is that it’s a GitHub repo, Normies just aren’t going to touch that. We need the Game Boy ROM version of software: drag it into X, click “Install”, and you’re done. Make a client-side app, make a marketplace. Done.