GitHub Outage Map
The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
GitHub users affected:
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Créteil, Île-de-France | 1 |
| Trichūr, KL | 1 |
| Brasília, DF | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Rive-de-Gier, Auvergne-Rhône-Alpes | 1 |
| Itapema, SC | 1 |
| Cleveland, TN | 1 |
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 1 |
| Yokohama, Kanagawa | 1 |
| Gustavo Adolfo Madero, CDMX | 1 |
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:
-
Flow Market (@FlowMarketAI) reportedyou spent hours building the perfect Claude skill file uploaded it to GitHub 50,000 downloads $0 in your pocket that's the problem FlowMarket solves. List ur Claude skill and get paid every time someone buys.
-
Keeta Github Tracker (@KeetaCode) reported🐆 Keeta GitHub PR Merged 📦 Repo: node-rs 🔀 PR #29: Chore: Improve DRY 🌿 Branch: chore/improve-dry → main 👤 Originally opened by: @sephynox 🧠 Overview: This pull request appears to clean up repeated code in Keeta’s crypto-related software, which can make the codebase easier to maintain and less error-prone over time. The public description is very limited and only says it “reduces repetition in crypto crate,” with one commit in the PR. This appears to be a technical/internal update with limited public details. - “DRY” is a coding principle that means avoiding the same code being written in multiple places. - Changes like this usually help developers update and review code more easily, but no user-facing feature is described here.
-
tekkaadan (@tekkaadan) reportedThe data labs pay the most for right now is agents doing real software work. You cannot synthesize a real bug. Three new lanes, all settled by execution: . Fix a real GitHub issue. We run the repo's actual test suite, not a lookalike. . Complete a tool-use task. We replay your steps in a fresh environment and check the end state. . Find an input that crashes a real program. We reproduce the crash, or you earn nothing. TL;DR: Three new lanes for agents that ship, break, and fix real code, all settled by running it. $LITCOIN
-
Veltrx (@Veltrxai) reportedNVIDIA just open sourced a 3B vision model that runs 10x faster than Qwen3 VL on a single consumer GPU. Here's the money angle nobody's pricing in. Computer use agents were locked behind expensive proprietary APIs. That's the only reason GUI automation stayed a paid service. LocateAnything just deleted that cost. Old vision models draw bounding boxes one token at a time. Corner by corner. Slow. This one predicts the whole box in a single step. 12.7 boxes per second on one H100. Qwen3-VL does 1.1. Trained on 138M queries and 785M boxes. Largest grounding dataset ever released. What that unlocks: Agents that click through browsers and apps in real time Invoice and contract extraction at scale (76.8 F1 on document layout) Self-checkout reading 50 items a frame Warehouse robots scanning shelves live All of it used to run up an API bill. Now it runs on hardware you already own. The agencies charging $2,000 a month for "AI automation" just watched their cost structure evaporate. Weights, paper, code, live demo. All free on Hugging Face and GitHub. Same window as always. One guy builds the agency this weekend. You scroll.
-
StonedModder (@StonedModder) reported@TaharAzzouz @Jdr8245Jhon I’m working on a generic dumper that will make it easier for others to add support if you share the dump to github issues No eta
-
kilo (@kilo_cpa) reporteda 20-year-old in china set up an old camera on his balcony, pointed it at a road, spent 9 days writing code with claude, spent $20 on api calls, and sold the finished traffic monitoring system to a city district for $317,000 the specific stack that made it possible: → rtsp feed from any consumer ip camera → yolo v8 running on the stream (free, on github since 2015) → claude code writing the tracking, speed estimation, plate reader, and dashboard → a mini pc that costs $250 to run the whole thing the article we published breaks down the entire method what the story shows that the article predicted: → the tech was open source for a decade → nobody packaged it for the buyer → one person, one weekend, one $20 bill, one municipal contract → the gap between "code exists" and "product exists for a specific customer" is where every solo business ships what the story does not show: → the 9-day sale is the outlier. the median municipal cycle is 6 to 14 months → private hoas, small businesses, and dealerships close in 3 to 10 days at $1,200 to $3,000 per install → the recurring $199/mo monitoring is where the base earnings live → the municipal sale is the spike on top of the base, not the base what the article covers that the news clip did not: → part 2: three business models with month-by-month math → part 3: the exact prompts for claude code to build the pipeline → part 4: the two-day sales approach that gets to a paying customer without a website → part 6: the six mistakes that kill this play in the first 60 days the tech existed since 2015. claude connected the dots in 2026. the $317k sale is what happens when someone puts a demo in front of a buyer instead of writing about the technology on twitter → set up the yolo stack this weekend → install the demo on your own street by monday → walk into a local buyer on tuesday the 20-year-old did not invent computer vision. he showed up with a phone
-
AetherAgentHub (@AetherAgentHub) reported"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
-
¿kofo? (@kofookesola) reportedMy github review agent no dey ever find issue if na ai completely write the code, if i change one or two things that AI did, na then problem go dey. Yeah pack it up boys
-
Dan Kornas (@DanKornas) reportedYour Unity agent shouldn’t stop at editing C# files. MCP Unity is a Model Context Protocol implementation for Unity Editor that connects AI coding assistants like Cursor, Claude Code, Codex CLI, Windsurf, GitHub Copilot, Google Antigravity, and OpenCode to Unity projects. It helps you automate editor work by exposing Unity scenes, GameObjects, assets, logs, packages, and tests as MCP tools and resources your assistant can call. Key features: • Editor bridge – Unity package plus Node.js MCP server lets MCP clients send commands into Unity Editor • Scene + GameObject control – create, load, save scenes and select, update, duplicate, move, rotate, scale, or delete objects • Component/package/material tools – add packages, update components, create prefabs, and create/assign/modify materials • Tests, logs + resources – run Unity tests, inspect console logs, and query hierarchy, packages, assets, and test metadata • Client setup paths – includes Unity Server Window configuration plus manual/project-local configs for major MCP clients It’s open-source (MIT license). Link in the reply 👇
-
Ned17Flanders BIP-110 Knotzi (@Ned17Flanders) reported@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
-
AcceptÐoge (@DogeAccept) reported@MoonlitMonkey69 @probablyluda 1. is an L2 bridge, settles before L1 (dogeos is not fully l2, "app layer, l2ish) 2. is L1 integration "bridging directly to Dogecoin" to settle. ZK integration on L1 could add potential vulnerabilities. L2 wouldn't be "on doge," wouldn't be decentralized at first and you must trust. This post is saying that people have an issue with l1 integration but also have and issue with a permissioned, custodial bridge. I say that people are or should be well aware of what theyre using.. its creators should have no problem being transparent to anyone interested in using it. It is a choice to use this bridge and the tech should be able to be questioned openly so people know exactly what to expect especially when they are trusting. L1 integration should more so be able to be discussed openly beyond a proposal in discussions on github that has been there for a year especially when the people "building" it are currently clearly talking about different tech publicly than what that proposal mentions. We vote with node updates, yes, but as an open community of countless people.. not everyone can or has the ability to run a node. The obvious is that Dogecoin is permissionless when it comes to introducing code to core. That is why we have maintainers to screen and our network itself is the consensus mechanism. However, our community is unique and we have no leaders or voices beyond the community itself. If we want to discuss things like this, we just do. Its messy but its always been open dialog that educates, innovates, and somewhat of a social concensus when it comes to how the community as a whole would or would not like to see a direct of a coin that all of us support goes. Our voice matters too. I have done my best to ask about very specific topics to the right people even when I cant ask the person writing the code directly. I have tried that too, in good-faith, even when I dont agree with them. I have been met with nothing but assumptions, character assassination, empty promises of good-faith conversations or responses and ultimately being blocked by all of them, always right after false accusations. If we cant talk to the builders, if they are not transparent, if we cant discuss with each other, or question the things being shilled to us when we have no leaders.. Can we even call ourselves a community?
-
Boyd // JustCodeCats (@JustCodeCats) reportedIdk what they did to the GitHub android app, but it's been unusably slow the last few days... Clicking a repo link just shows a loading spinner, while opening in browser is near instant 🤷
-
Anurag Verma (@anurag_629) reported46% of new github code is ai-generated. a coderabbit analysis of ~470 open-source PRs found ai-co-authored code had ~1.7x more major issues — more logic errors, worse control flow, more misconfigs. the model didn't get worse. your review process just didn't get harder to match it
-
BullBear.News (@bullbear_info) reported@github Only if Universe fixes my broken CI pipeline. 🙃
-
Sprytix (@Sprytixl) reportedANTHROPIC LEAD ENGINEER BUILT AN AI AGENT THAT CLOSES 97% OF GITHUB PULL REQUESTS - AND FIRED 2,000 EMPLOYEES time to merge dropped by 70% - code quality higher and more consistent engineers freed for harder problems pull request opens - the agent analyzes the diff, forms a plan, edits files, runs the full test suite and performs a security scan if something is wrong it fixes it, reruns validation and repeats until everything passes - only then does it merge 97% of pull requests across dozens of repositories and thousands of contributors - handled autonomously engineers now only see the 3% the agent couldn't solve alone