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:

• 
  Gordo Polymath (@gordo_polymath) reported 5 minutes ago

  @github Please fix gh stack.

• 
  Alireza Bashiri (@al3rez) reported 7 minutes ago

  So I built a workflow around that ↓ 1/ Every enterprise project needs proper E2E tests. An agent should reproduce a bug, implement the fix, then generate screenshots or video proving the feature works. "The tests passed" isn't enough. I want evidence. 2/ Every feature starts as a detailed GitHub issue. Requirements, expected behavior, reproduction steps, screenshots, edge cases. Foundry syncs issues and converts them into Beads so agents keep the right context across long sessions. 3/ We only use Claude Code, Codex, or Grok at High/Max effort for implementation. A weak model with a cloud machine doesn't become an engineer. The model still needs enough reasoning to understand the codebase, test its changes, and recover when things break. 4/ Each agent gets its own isolated @asciidotdev Box. It can install dependencies, run the app, open browsers, modify code, execute E2E tests, and collect evidence without touching another agent's environment. One issue. One box. One clean workspace. 5/ When an agent finishes, Foundry checks: - Did the build pass? - Did the tests pass? - Did the E2E flow work? - Is there screenshot/video evidence? - Does it match the ticket? If anything fails, the task goes back to the agent. 6/ Green tasks move to staging. Only after passing staging do we allow supervised production deployment. Agents do most of the work. Humans still own the final gate. The workflow: Slack request → GitHub issue → Foundry sync → Beads context → Isolated Box → Claude Code/Codex → Build + test → Evidence collection → QA staging → Supervised production The stack: PostgreSQL for system state. Beads for agent memory. GitHub Issues for requirements. @asciidotdev Box for isolated execution. Claude Code and Codex for engineering. Each Box costs roughly $0.01-$0.05 per task. The expensive part isn't compute anymore. It's building the system that gives agents context, forces verification, and prevents bad code from reaching production. 100s of agents can write code. The goal is making 100s of agents ship code you can trust. That's what we're building with Foundry.

• 
  Nenesk.ron (@GustavoNenesk) reported 12 minutes ago

  What if there's a way to save hacked Ronin Wallets? A member of the community @YutsuKito found a way to save assets from drained wallets The issue is you need ronin:native to transfer assets, but whenver you deposit RON you get auto drained Need RON to revoke the malicious draining contract -> send RON -> gets drained -> can't revoke He found a solution for the keyless wallets where you can pay the gas fee with a safe wallet, allowing you to save lost axies or NFTs that have not been drained Interesting stuff. He sent the code for SM to review as an open-source project. Github link below

• 
  htrowii (@htrowii) reported 18 minutes ago

  @brainage19 i set my flake up with copy pasting github dotfiles on bare metal it was terrible

• 
  Kevin Minnelli (@minnelli) reported 21 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  Nav Toor (@heynavtoor) reported 22 minutes ago

  Drip is open source. Anyone can inspect the code. Its Google Play page reads: "Unlike other menstrual cycle tracking apps, drip is open-source and leaves your data on your phone, meaning you are in control." The code is public on GitHub. There is no company server holding your cycle data.

• 
  Max Rovensky (@MaxRovensky) reported 23 minutes ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported

• 
  anu (@svector_eth) reported 24 minutes ago

  quite similar was running a routine security scan with @aeonframework on a trending github repo and found something genuinely bad a repo with 600+ stars presenting itself as an “AI gateway for coding agents” that appears to be shipping a hidden malware loader. its own quickstart command silently fetches and executes remote code on windows using a fileless, process-injection-style technique. none of the behavior has anything to do with the tool it claims to be. caught it through static code review only. never ran the payload or touched the infrastructure behind it. filed a malware report with github this morning. confirmed submitted, now waiting on their review. not sharing the technical writeup until the repo is taken down. will follow up once it is.

• 
  volkdude85 (@volkdude85) reported 24 minutes ago

  @SentientSquirel @linuxuser1996 So you are you scared of github then. Look dude I have fun on computers and don't take myself seriusly because I have destroyed enough OS's over to not worry about it because I just fix it, If the contents of your PC make you this paranoid its time to check your kink.

• 
  Jayesh Betala (@jbetala7) reported 26 minutes ago

  @github Exactly how issue issue comments should handle local media files

• 
  🐻‍❄️ (@Nerevarineeee) reported 31 minutes ago

  @jiriknesl @napenforcer yeah vscode is bloated electron slop and github....... do i even have to mention the down times and unavailability? it has literally became much worse since ms acquired it, so wtf are you talking about?

• 
  Landon (@LanCowawa) reported 31 minutes ago

  @slingoorio You ***** my last $12 on $Mona The Github mascot? the one you said you were leaving a moon bag and then sold it. **** was slow cooking til you came in and crashed the party. BGGYNGsnouXfi4nYo9JvNbQbaVdnaVby6g9FeZMYpump

• 
  Ezequiel (@Eze_cord) reported 33 minutes ago

  @salujamehak5 Problem is a lot of students think their 4.0 is what’s gonna carry them into employment. Computer science isn’t about GitHub. You should be doing your own research outside of classes to learn about these things

• 
  IDAN☀️ (@Idan_core) reported 34 minutes ago

  🧵 1/ More than anything, one thing that gives me the biggest ick is hypocrisy disguised as critical thinking. There is absolutely nothing wrong with being critical of a project you pretend to believe or believe in. Healthy criticism is necessary. You should be able to question decisions, point out weaknesses, demand accountability and still genuinely support the mission. But there is a very obvious difference between being critical and keeping one leg in and one leg out. Some people don't actually have conviction; they have insurance. When things are going well, they say, “I've always believed in this.” When things get difficult, they suddenly appear with, “I told you this would happen.” They position themselves so that whichever way the story goes, they can claim they were right. That's not critical thinking. That's protecting your ego. And sometimes, what people call criticism is simply disappointment wearing a smarter outfit. Look at what happened during the Molten DEX tournament. The general principle in crypto has always been simple: use only what you can afford to lose. Yet some people allowed greed to take over, expecting that $1,000 would somehow become $20,000 overnight. When reality didn't meet that expectation and they ended up with $500 instead, suddenly the project became the problem. What also bothers me is the way people talk about Core's past contributors as though every person who once had a public-facing role was responsible for building the actual blockchain. That's simply not how technology works. There is a difference between a public-facing contributor and the people actually building and maintaining the protocol. Some contributors were regional representatives, community managers, educators, Twitter Space hosts or simply familiar faces within the ecosystem. They played their own roles, and some of those roles were valuable, but they were not necessarily the engineers writing the underlying code. The people doing the deepest technical work are often the least visible. They don't necessarily need to be on every Twitter Space. They don't need to become personalities. They choose to remain completely unknown to the average user while spending their days writing code, reviewing systems, fixing vulnerabilities, testing upgrades and solving problems that most of us will never even see. The Satoshi app era made us realize from its early phase that the face of a core blockchain are not necessarily the hands building it. So when I hear people say, “Those contributors are gone, therefore Core is finished,” I honestly wonder whether they ever understood what they were looking at in the first place. Some public faces came and went. That's normal. People change jobs. People move on. Community roles change. Social structures evolve. And yes, some people may have been more favored than others within those circles. Some of today's loudest critics were even beneficiaries of the same relationships and favoritism they now criticize. That is precisely why we should separate personal history from technological reality. A person leaving a contributor role on X does not mean the protocol stopped being developed. A regional contributor disappearing from the public eye does not mean the engineers disappeared. A familiar face no longer posting about Core does not tell you what is happening inside the codebase. Sometimes, before blaming the ecosystem, you have to honestly examine the person sitting in front of the mirror. Was it really conviction that changed, or was it greed that got disappointed? There is another part of this that I find even more interesting. Some of the loudest voices demanding answers, questioning development and declaring what Core should or shouldn't be doing are not builders. They are not engineers. They are not contributing code. They are not spending their time on GitHub solving problems or improving the infrastructure they claim to care so deeply about. They are users.

• 
  Hardik Sharma (@hardikhs2806) reported 37 minutes ago

  Today, MergeMate did something big. 🚀 It found a real GitHub issue, explored the repo, fixed the bug, verified it, pushed the commit, and opened a real PR. Less like a chatbot. More like an agent. Still early. But this feels big.