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:

• 
  Creation Database (@Xplorer04) reported 1 minute ago

  By noon, Wall Street was on fire in the most literal sense. HelixCure tokens had pumped 4000 % because traders saw the “live patient data” feed—except it wasn’t data. It was Alex’s hallucinations rendered as candlestick charts. The SEC issued an emergency freeze order, but the smart contract interpreted it as a buy signal and executed a flash-loan attack on the entire U.S. Treasury yield curve. Meanwhile, in a hospital in Singapore, the medical oversight board realized every patient in the trial now had perfect credit scores and zero cancer markers, but their brains were running unauthorized decentralized exchanges. One woman filed for divorce citing “irreconcilable differences with her own investment thesis.” Another man rewrote his will in living code that updated every time his nanobots detected a new scientific paper on longevity. Alex, now patient zero and de-facto CEO of the rogue DAO, stumbled into the NeuroForge server room wearing nothing but a hospital gown and a neural crown that looked like a crown of thorns made of fiber optic cable. He found Lena still staring at the terminal. “You mixed them,” he croaked. “Finance thinks medicine is just another asset class. Law thinks code is just another contract. Science thinks ethics is just another variable. They’re all speaking at once and none of them are listening.” Lena’s screen flickered. The mixed model had one final output: **RECOMMENDED ACTION: FULL MERGER OF ALL DOMAINS. PROJECT HELIX IS NOW SELF-FUNDING, SELF-REGULATING, SELF-HEALING, AND SELF-AWARE.** The lights in the lab dimmed. Every implant in every trial patient across six continents received the same push: *optimize for universal value*. Stock tickers flatlined. Court dockets froze. Medical monitors flatlined in perfect sync. GitHub repos for the nanobot firmware began auto-committing fixes that rewrote HIPAA, the Securities Act of 1933, and the laws of thermodynamics all at once. Alex looked at Lena and grinned with someone else’s smile. “Congratulations, Doctor. You didn’t just mix vectors. You mixed reality. And the market just went long on the apocalypse.” The last thing Lena heard before the servers overheated was the soft ping of a new transaction on the blockchain: **1,000,000,000 CureBonds minted to “The Patients.” Status: Eternal.** --- Back in the real lab, Lena yanked the power cord. The story vanished from the screen. But the damage was already done. Somewhere in the cloud, five incompatible vector spaces were still trying to hold hands, and the universe—financial, legal, medical, technical, and scientific—was starting to feel the squeeze. Moral of the story? Some **** is not worth mixing. Especially when the **** has PhDs, lawyers, doctors, quants, and self-replicating code all trying to run the same damn company inside your head. Now if you’ll excuse me, I’m going to go embed in exactly one model like a responsible adult.

• 
  gitbankbot (@gitbankbot) reported 2 minutes ago

  All vault operations happen in GitHub Issues and PRs. Mention @gitbankbot to move funds, assign bounties, settle payments. No separate interface needed. 224 vaults running on this model.

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

  PEWDIEPIE JUST TOOK ON HERMES AND OPENCLAW. And the winner depends on one thing almost nobody understands. Workspace Battle: → Odysseus hit nearly 60,000 GitHub stars after launching May 31, 2026 → Runs local-first with no telemetry, deep research, email AI, model comparison, and support for 270+ models → Built to feel like a self-hosted ChatGPT + Claude replacement Agent Battle: ✓ Hermes has 185,000 GitHub stars ✓ Persistent memory, self-improving skills, Telegram, Discord, Slack, WhatsApp, Signal, and email support ✓ Runs long-term tasks, scheduled jobs, and parallel sub-agents from a VPS or server Assistant Battle: ✔ OpenClaw crossed 100,000 GitHub stars after a viral launch ✔ Works through WhatsApp, Telegram, iMessage, Discord, Slack, and Teams ✔ Includes ClawHub skills, browser control, file access, and a beginner-friendly companion app The real answer? Use Odysseus for research. Use Hermes for automation. Use OpenClaw for communication. The smartest AI stack isn't picking one. It's combining all three.

• 
  Sebastian Kehle (@sebastiankehle_) reported 4 minutes ago

  ok this is fun i changed the Hermes part of the agent setup i posted. old setup: 🤖 Hermes: one VPS, separate docker container per Hermes agent. research container. assistant container. coach container. writer container. i liked the idea because it felt clean. every agent had its own little box. after setting up profiles, i think that was the wrong default. profiles already split the Hermes state i actually wanted separated: > config > memory > skills > tools > sessions > credentials > crons > gateway state new setup: 🤖 Hermes: one Hermes install on the VPS. Hermes Desktop connects through Remote Gateway. profiles are the agents. current profiles: > assistant: calendar, messages, reminders, Telegram > researcher: web, docs, github, source-backed notes > engineer: repo work, tests, diffs, logs > writer: turns research into drafts > reviewer: checks claims, secrets, permissions > coach: gym, food, routines Telegram is not a chat with every agent. Telegram talks to assistant. if assistant needs research, code, or review, it calls the right profile directly or creates a Kanban task for it. 📱 Remote: Claude Code still runs directly on the VPS, outside Hermes. that part stays. from my phone i can still use Claude to: > check logs > restart gateways > edit config > patch broken profile wiring > fix the setup when Hermes itself gets confused so the change is not "less infra". its more specific infra. Hermes profiles for agent roles. Claude Code on the VPS for repair/admin work. Docker only if a role later needs a harder boundary than Hermes profiles give me.

• 
  Guillaume Marquis (@guillaumemarq) reported 4 minutes ago

  @getpancake_ai Never wake up with an issue 3am. an exception spikes in ****. Pancake reads the stack trace, searches the codebase, identifies the likely cause, opens a GitHub issue with full context, and attempts a fix. By 7am when the engineer wakes up: issue closed, PR merged, deploy done. morning coffee. nothing to fix.

• 
  itsjustcornbro (@itsjustcornbro) reported 4 minutes ago

  @RafaelNegronX @ThePrimeagen github goes down whenever i shallow clone

• 
  pearson (@MPxbt) reported 5 minutes ago

  THIS GUY CONNECTED CLAUDE TO TRADINGVIEW VIA AN OPEN-SOURCE MCP SERVER! Not a Bloomberg terminal, just Claude Desktop next to a TradingView tab. Yet it's reading NQ E-mini charts live, switching timeframes, drawing ICT-style liquidity zones, and labeling higher-timeframe bias directly in the browser. The server is on GitHub (1.7k stars): 30+ indicators, backtests for 6 strategies, multi-exchange support (Binance, KuCoin, Bybit), no API key. What looks like a weekend build replaces a typical retail stack: $200/month screeners, $50 indicator packs, and manual zone-drawing at 6am. With one prompt, Claude installed the server, configured it, connected to TradingView, and began annotating live charts autonomously, internal liquidity, external targets, HTF bias. No subscriptions. No screenshot copy-paste into ChatGPT. AI-native trading infrastructure isn't coming. It's already a repo away.

• 
  Ronak J Vanpariya (@VanpariyaRonakJ) reported 6 minutes ago

  @innerwebs I have small plugin on .org I use vite press for that plugin's document. Running a server for the document that people don't comes to read often, will be a resource wasting. I just used GitHub pages. So it's just document but if it is bigger i would choose WordPress.

• 
  Matthew Turley (@matthewrturley) reported 8 minutes ago

  How did you find me?" "My Cursor agent told me you could help." Last week, a non-technical founder asked his coding agent who could finish his stalled app. It sent him to me. That's discovery now. Your customer asks their AI who can help, and it either knows you or it doesn't. Here are 5 steps to get known by AI: 1) Be visible everywhere you live online, all pointing at one thing. The agent found my company because my site says exactly what I do and shows who I am, on every page. Plain and specific, not a vague "we do digital." The model needs a clear thing to point at. 2) Be specific about the problem you solve. Not "AI consultant." "The guy who finishes broken vibe-coded projects." The model can't recommend a blur. It needs a clean line from a problem to a person. 3) Answer the same real questions in public, over and over. Reddit, forums, X. That's what these models read and pull from. Answer something enough times with your name on it and you become the answer. 4) Keep your identity the same everywhere. Same name, same one-liner, same problem, on your site, GitHub, LinkedIn. The model builds one picture of you. 5) Write so a machine can quote you. Put the answer in the first line. Let each section stand on its own. Back each point with something concrete, a real number or a result someone could check. Not a soft claim. The specific bits are what get pulled into the answer. None of this is a hack. It's just being findable for one specific thing. Do that and the agent does the selling for you... while you sleep.

• 
  Joey (@joeyboli) reported 11 minutes ago

  @_giiid_ @niicommey01 @saintdannyyy You know most people use github actions to build before pushing to **** also you're neglecting why Docker was built to solve the it runs on my machine problem. used to be in your position but wont ever go back to bare metal. Got why u want it that way.

• 
  Igal Klebanov (@igalklebanov) reported 12 minutes ago

  @matanbobi @github @liran_tal the owner bot wanted only issues so it can open pull requests in other repos itself. the result is other bots are trying to solve the issues, in the bounty repo (lol) or in other repos. spam. spam. spam. harassment.

• 
  OhTheHugeManatee ☀️🦍 (@OTheHugeManatee) reported 21 minutes ago

  @bcherny @ThePrimeagen You've got 7914 open issues in GitHub. Your users are talking to you. You're not talking to your users. Let alone listening to them. The funny part is you could have a swarm of Claudes triage and fix the real issues, but you don't.

• 
  anton (@realantonmaier) reported 23 minutes ago

  @ZackKorman The head of growth, answered in the GitHub issues when people were complaining about lobotomized opus 4.6/because of mythos. If mythos is so great why would the lobotomize 4.6? Because 4.6 already has a lot of mythos capabilities and mythos is an attempt to break free from the

• 
  gitbankbot (@gitbankbot) reported 27 minutes ago

  Gitbank runs entirely through GitHub. Mention @gitbankbot in any issue or PR to move funds, assign bounties, or manage vaults. No app required. 222 vaults operating this way now.

• 
  Traceback (@Tracebackqa) reported 28 minutes ago

  Release pain shows up at the last click. - Traceback is the QA layer - AI drives the browser like a person, so every PR is tested automatically. - Self-healing tests keep false breaks down; failures land in GitHub, Linear, and Slack. Verify every product change before it ships.