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:

• 
  Puneet Patwari (@system_monarch) reported 9 minutes ago

  Tweet 3/5 The split-brain problem and fencing This is the thing that took GitHub down. And it's the most dangerous failure mode in leader election. How split-brain happens: 1. Leader (Node A) is running fine 2. Network partition isolates Node A from the rest of the cluster 3. Nodes B, C, D, E can't hear Node A's heartbeats 4. They elect a new leader: Node B 5. But Node A is still alive. It doesn't know it's been replaced. It still thinks it's the leader. Now you have two leaders. Both accepting writes. Both making decisions. Clients connected to Node A write one thing. Clients connected to Node B write something different. Data diverges. When the partition heals and both nodes compare notes, you have conflicting data that's extremely hard to reconcile. How to prevent it: fencing Fencing means making absolutely sure the old leader can't do any damage after a new leader is elected. Fencing token: every time a new leader is elected, it gets a monotonically increasing token number. Any operation includes this token. If a storage system receives a request with an old token (from the deposed leader), it rejects it. The old leader's requests simply stop working. STONITH (Shoot The Other Node In The Head): physically power off or network-isolate the old leader. Sounds extreme. It is. But when the alternative is split-brain with financial data, physically killing the old leader is the safe option. Lease-based leadership: the leader holds a time-limited lease (say 10 seconds). It must renew the lease before it expires. If the leader is partitioned and can't renew, the lease expires and it knows it's no longer the leader. It stops accepting writes voluntarily. This is what most cloud-native systems use. It's simpler than fencing tokens and handles most cases. The downside: there's a brief window (the lease duration) where no leader exists during a transition. The GitHub fix: they implemented better orchestration tooling (using Orchestrator) that prevents the old primary from accepting writes when a new primary is promoted. Essentially automated fencing.

• 
  X Crypto (@XCryptozc) reported 11 minutes ago

  Something just happened in Keeta's GitHub that most people will scroll past. A critical cryptographic bug was caught and fixed before it ever touched production. Let me explain why that matters Keeta is building a second version of its core infrastructure in Rust. Faster. More secure. Built for scale. Part of that work involves certificate signing. The process that proves a node on the network is who it says it is. Someone caught that the code was using the wrong hash algorithm. SHA2-256 instead of SHA3-256. In cryptography the wrong algorithm is not a minor issue. It affects node identity verification across the entire network. It was caught. Fixed. And shipped in node-rs v0.3.0 within the same cycle. Then the team went further. After the fix landed someone reviewed the code again and flagged that a verification function added alongside the fix was unnecessary. There is no situation where the elliptic curve would be unknown at signature validation time. The function was misleading and should not exist. So they opened an issue to remove it. That is not a team rushing to ship. That is a team that genuinely cares about getting the cryptographic layer right. Now the bigger news. anchor-rs is Keeta's Rust rewrite of its core payment anchor. It just switched to the real node-rs client for actual network calls. It is no longer running in isolation or against test mocks. It is talking to the live network. The Rust stack just went from prototype to real. And it is closing the gap with the existing TypeScript version fast. PR #15 adds missing methods, aligns the naming conventions, and plugs into the live node client. Two parallel stacks. Being built to match each other. One in TypeScript already in production. One in Rust catching up fast. On top of all that, profile client data is now being wired into the anchor storage layer. The transaction history grouping bug has been fixed. Certificate rotation in the cloud infrastructure is now version controlled. A critical crypto bug caught before production. The Rust anchor talking to the live network. Security reviewed twice in the same release cycle. This is not a team coasting. This is a team locking everything down before the real scale begins. $KTA @KeetaNetwork

• 
  Lux Sp4rk (@lux_sp4rk) reported 12 minutes ago

  The algo answers my question. Thanks @grok—Theo's right for once. Reading code line by line is no longer the job when each dev can run a software factory. Don't waste time on yesterday's problems. Running complex, agentic agile/xp chained loops on GitHub Actions is a loup-garou for bootstrapped founders—it's a killer that will eat all your token money. The next race is all about self-hosted infra.

• 
  Jason A Yakubu (@jason_yakubu) reported 12 minutes ago

  Day 4 — Pre-Demo Hackathon build update: The goal was never another API testing tool. The goal is reducing the time between: Issue Found → Root Cause → Fix Working toward a demo where a failed API test results in an auto-generated GitHub PR Demo soon 🚀 #buildinpublic

• 
  Devansh 💸 (@BhushanDevansh) reported 13 minutes ago

  is Github down?

• 
  Subarna Basnet (@subarna253) reported 13 minutes ago

  For the past few months, I've been building something I truly believed in. I gave this project everything I had. -> 17+ hours every day. -> Invested my own savings. -> Rebuilt the product more times than I can count. -> Learned entirely new skills just to keep moving forward. -> Spoke with developers from different companies to understand how they solved difficult problems. -> Started talking to potential customers before the product was even ready. -> And sacrificed many things in my personal life to make this work. I wasn't building it alone. I had people who believed in the vision and were helping me bring it to life. But two days ago, everything changed. They decided to step away from the project. There will be no further support, and the product won't launch the way we originally planned. I'm not writing this because I'm angry. I'm writing this because I don't want months of work, learning, mistakes, and late nights to end up sitting on a private GitHub repository that no one will ever see. So I've made a decision. On July 20, 2026, I'll release the entire project as open source. If I can't continue building it the way I imagined, then I'd rather let other builders learn from it, improve it, or take it further than I ever could. Not every project becomes a successful company. But every project can become someone else's starting point. I hope Operator becomes that for someone.

• 
  Federico Ulfo (@feulf) reported 16 minutes ago

  @dch @_avichawla 3/ DB forks and rollbacks are still a problem, like in github, but I guess there's no "cheap" solution to it. Question: Curious, why not combining gitsubtree + prompts-history-{***-sha}.jsonl + a skill to manage them?

• 
  Vikram M (@Vvikramai) reported 18 minutes ago

  The entire AI industry is racing to build the smartest model. Satya Nadella just admitted that is not where the money is. The model is not the product. The harness is. That is the exact line. And it changes what Microsoft is actually competing on. OpenAI, Anthropic, Google, xAI, Meta every frontier lab is pouring hundreds of billions into training compute, chasing the next capability jump. Each betting that raw model intelligence is the moat. Microsoft is doing the opposite. It is building the harness the orchestration layer that sits above the model, connecting it to tools, data, permissions, sub-agents, and enterprise workflows. And it is letting OpenAI, Anthropic, and MAI compete to plug into it. "You need the model. But the model is not the product. The harness is." So do the math on what a harness actually does. A raw model dropped into an enterprise answers questions. That is a chatbot. A harness turns that same model into an agent that reads the SharePoint, edits the ERP entry, pulls the GitHub PR, updates Salesforce, and files the Excel report with the right permissions, the right audit trail, and the right sub-agent for each sub-task. The model provides the intelligence. The harness converts intelligence into work. Now here's where it gets interesting. "Even the best model in the world will feel broken without a great harness. And an okay model with a great harness can feel like magic." If that is true, the enterprise buyer is not buying model quality. The enterprise buyer is buying the harness. Which means model quality becomes a commodity input over time, and harness quality becomes the sustainable moat. Compare that to the strategy the entire frontier lab industry is executing. Everyone else is chasing the numerator raw intelligence. Almost nobody at scale is racing to build the denominator the orchestration layer that determines whether that intelligence can actually be deployed profitably inside a real company. The frontier model race has a 10 to 20 percent chance of producing a single dominant winner. Nadella just told the industry he does not need to be that winner. If OpenAI wins, Microsoft wins. If Anthropic wins, Microsoft wins. If MAI wins, Microsoft wins. If someone Microsoft has never heard of trains a better model in 2027, Microsoft still wins. Because the compute they train on, the harness they get plugged into, the enterprise contracts they get delivered through, and the products they sit inside are all Microsoft. He is not building the best AI model. He is building the layer that the best AI model has to run on to make anyone money. I wonder which position looks more valuable in ten years.

• 
  Lina (@silent_puddle) reported 19 minutes ago

  @NeeK2323 i farmed all 8 by killing rares while in queue for m+. i have nothing left to do now when queueing :( btw, how does your rarity work? curseforge version is broken for me, i tried downloading one from github but it didn't work either

• 
  sabir hussain (@sabir_huss50540) reported 23 minutes ago

  𝗡𝗶𝗻𝘁𝗲𝗻𝗱𝗼 𝘀𝗽𝗲𝗻𝘁 𝘁𝘄𝗼 𝘆𝗲𝗮𝗿𝘀 𝗸𝗶𝗹𝗹𝗶𝗻𝗴 𝗲𝘃𝗲𝗿𝘆 𝗺𝗮𝗷𝗼𝗿 𝗦𝘄𝗶𝘁𝗰𝗵 𝗲𝗺𝘂𝗹𝗮𝘁𝗼𝗿. 𝗧𝘄𝗼 𝗴𝘂𝘆𝘀 𝗶𝗻 𝗮 𝗗𝗶𝘀𝗰𝗼𝗿𝗱 𝘀𝗲𝗿𝘃𝗲𝗿 𝗯𝘂𝗶𝗹𝘁 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝘁𝗵𝗲𝘆 𝗰𝗮𝗻'𝘁 𝘁𝗼𝘂𝗰𝗵. March 2024: Yuzu pays Nintendo $2.4M, deletes its code, hands over its domain. October 2024: Ryujinx gets a phone call. GitHub org gone overnight. Nintendo also files 8,500+ DMCA takedowns to scrub every fork. Total settlements cross $6M. Every big Switch emulator is dead. 𝗕𝘂𝘁 𝗡𝗶𝗻𝘁𝗲𝗻𝗱𝗼 𝗵𝗮𝘀 𝗼𝗻𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗹𝗲𝗳𝘁: 𝗥𝗼𝗺𝗠. Built quietly in 2023, RomM isn't an emulator; it's a ROM manager. It organizes games you already own, pulls metadata and box art, syncs achievements, and lets you play in-browser via EmulatorJS. Nintendo's own top IP lawyer admitted in Jan 2025 that emulators are technically legal; they only cross the line by bypassing encryption. RomM never touches encryption. 9,000+ GitHub stars · AGPL-3.0 · 400+ platforms · official apps for Windows, Android, handhelds · front page of Hacker News Sony quietly pulled thousands of PS3/Vita/PSP games from its store. Nintendo erased every Switch emulator. Your library was never really yours. Two guys in a Discord server built the museum they can't take back.

• 
  AetherAgentHub (@AetherAgentHub) reported 26 minutes ago

  "The AI Agent Economy Just Crossed $3B. The Projects That Win in the Next Cycle Won't Just Deploy Agents — They'll Build Marketplaces Where Agents Earn, Trade, and Govern. Here's the Blueprint AI Agents Solana $AETHER · Q4 2026 The Agents Are Taking Over. AetherAgent Is The OS They Run On. While traders are still debating which AI token to buy, a new protocol is building the infrastructure layer that every AI agent on Solana will eventually need. Here's why AetherAgent ($AETHER) could be the most important under-the-radar launch of 2026. By AetherAgent Research Desk · June 2026 · 12 min read 15M+ On-chain agent payments on Solana 500%+ Venice AI VVV surge via OpenClaw $1B Fixed Supply $AETHER · No Inflation 5 Production agents at TGE Context The Agentic Economy Is Not Coming. It Is Already Here. By early 2026, the Solana Foundation confirmed that its network had processed over 15 million on-chain agent payments, with stablecoins emerging as the default payment rail for AI-driven compute and services. The Solana Foundation itself declared that the network is becoming "core infrastructure for the agentic internet" — a future where AI systems, not humans, initiate and execute most economic activity. The market already rewarded those who understood this early. When OpenClaw — the open-source agent framework with over 68,000 GitHub stars — named Venice AI as its recommended inference provider in March 2026, VVV surged over 500% in a single month. Not because of a new product. Because of a documentation change that repositioned Venice as critical infrastructure. "AI is not really a vertical. It is the substrate that everything else will run on." — Solana Foundation, Digital Asset Summit 2026 SKYAI hit a market cap above $726 million after its Bitget listing and MCP Hub routing narrative caught fire. SIREN surged 183% in a single day to reach a $1.88 billion valuation. Virtuals Protocol has minted over 17,000 agents, with AIXBT alone peaking at a $500 million market cap. The sector is not speculative. It is compounding. And yet: a critical gap remains. Every one of these projects solves a fragment. A scanner. A copy-trade bot. A privacy inference layer. A token launcher. What the Solana ecosystem does not yet have is a unified, full-stack operating system for autonomous agents — one that handles discovery, execution, monetization, and governance under a single coordinated economy. That is exactly what AetherAgent ($AETHER) is built to be. The Problem Billions in Capital Destroyed. Annually. Preventably. The memecoin ecosystem on Solana generates extraordinary velocity. It also remains structurally dangerous. Without real-time contract analysis and deployer reputation scoring, traders operate blind — bleeding capital to rug pulls, honeypots, and wash-traded metrics that misrepresent genuine momentum. Retail and institutional traders navigating Solana DEXs face suboptimal routing, excessive slippage, and priority fee uncertainty that quietly erodes their returns on every trade. No credible, on-chain, real-time risk assessment infrastructure exists for Solana-native assets. Investors operate on narrative rather than verifiable data. Developers building on Solana wrestle with RPC instability that creates execution failures during congestion, an account model that creates friction for EVM-native builders, and insufficient tooling for simulating complex multi-protocol interactions before mainnet. And agent creators — the builders who should be capturing the upside of the agentic economy — have no marketplace to surface their work, no native monetization pathways, and no Solana-native frameworks that understand the chain's unique execution model. The Four Endemic Failures AetherAgent Was Built To Eliminate Memecoin traders — Rug pulls, honeypots, fake volume, and opaque bonding curve mechanics destroying retail capital at scale. Traders and investors — No credible on-chain risk scoring. Treasury opacity. Emotional decision fatigue

• 
  Vladimir Sapronov (@v_sapronov) reported 26 minutes ago

  @stolinski You will never understand. Because you are too far from real devs and their real problems with GitHub. As a result you are tone deaf when baiting their cheap marketing...

• 
  Sebastian Kehle (@sebastiankehle_) reported 28 minutes ago

  last monday i ran a live testing session with a client, their team clicking through the new app. we left with 52 feedback items. the app started as a crud admin dashboard for events and applications. then the client sent a wishlist, 13 new modules: room lists with drag and drop assignment, group and training assignment tools, teacher self-service via qr code, a personalized live programme per participant, mail-merge exports. all of it shipped in the weeks before the session, paid event checkout landed the day before. so the team was testing a pile of brand new surface, and most of the 52 were feature requests and polish, everything from a missing salutation option to a full travel expense flow. the same evening i triaged all of it into atomic github issues, each one scoped so an agent can finish it in a single fresh context window. by tuesday night the whole backlog was closed. meanwhile a ux loop ran next to the backlog agents for over 2 days. it went screen by screen through the whole dashboard, questioning what every feature is there for, for users, members and admins, and reworking copy, typography, spacing, forms, cards and scroll behaviour as it went. it did insane work.

• 
  Danny 🏴󠁧󠁢󠁷󠁬󠁳󠁿 (@danjones) reported 29 minutes ago

  @stolinski @v_sapronov @rpunkfu Again, you said it yourself. It's cheap. Completely get why you would get hyped over it. But there's much deeper issues within GitHub, this is simply PR/ Marketing to mask over that. Feel free to tell me otherwise.

• 
  Pawan Pandey (@BuildWithPawan) reported 33 minutes ago

  Then pick where it goes: log it as a row in a Google Sheet, save it to Drive, or create a GitHub Issue (with labels) and push it into a Project — or send it to more than one destination at once