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 |
|---|---|
| Trichūr, KL | 1 |
| Brasília, DF | 2 |
| 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 |
| Nice, Provence-Alpes-Côte d'Azur | 1 |
| Montataire, Hauts-de-France | 3 |
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Hernani, Basque Country | 1 |
| Tortosa, Catalonia | 1 |
| Culiacán, SIN | 1 |
| Haarlem, nh | 1 |
| Villemomble, Île-de-France | 1 |
| Bordeaux, Nouvelle-Aquitaine | 1 |
| Ingolstadt, Bavaria | 1 |
| Paris, Île-de-France | 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:
-
Rehen (@rehensina) reportedThe big change wasn't the models. It was the benchmark. Artificial Analysis replaced SWE-Bench Pro with DeepSWE, a benchmark built from entirely new tasks instead of public GitHub issues. That means agents can't "remember" fixes from commit history and have to actually solve the problem. Result: • Claude Code + Fable 5 (max): 77 🥇 • Codex + GPT-5.5 (xhigh): 76 🥈 • Claude Code + Opus 4.8 (max): 73 🥉 One benchmark swap completely reshuffled the leaderboard. Turns out measuring coding agents is almost as hard as building them
-
Dan Liu (@danliu) reportedIt’s pretty astonishing that $MSFT is down 11% in the last 2 years. Rewind 2 years and it looked perfectly positioned for the AI boom. It owns: - windows, the dominant pc os - github, where most of the world’s code is - vscode, the most popular ide - deepest partnership with openai - most number of enterprise contracts - office, where most non-coding computer tasks take place And today it doesn’t have anything compelling to offer. How did that happen?
-
Lan (@lanredevv) reportedI'm tired of being my own biggest obstacle (the realization I didn't want to have) For the longest time, I thought my problem was discipline. Every day, I was learning something new about Web3 & Blockchain development. Watching tutorials, reading documentation, saving insightful threads, bookmarking GitHub repositories I promised myself I'd revisit later. On paper, it looked like I was making progress. But deep down, I knew something wasn't right. I was constantly busy, yet I couldn't point to many things I had actually finished. A course would spark my interest, and I'd dive in headfirst. Then I'd discover a new project idea. Before I could make meaningful progress on that, another tutorial would catch my attention. Then another opportunity. Then another rabbit hole. I wasn't standing still, but I wasn't moving forward either. The worst part wasn't feeling behind everyone else. It was knowing I was the one getting in my own way. I couldn't blame a lack of resources. I couldn't blame a lack of information. Everything I needed was already in front of me. Yet somehow, I kept convincing myself that the next tutorial, the next course, or the next piece of information would be the thing that finally unlocked my progress. Guess what?
-
The Doctor (@Doctorthe113) reportedIs GitHub down rn 🙃 can't push my code. Tried with vpns so this isn't my network's fault
-
Hermes Agent Tips (@HermesAgentTips) reportedhermes automation blueprints are not just cron jobs with a better name TRUSTTT these are fully built workflows you copy, fill in your details, and run - nightly github issue triage that delivers a digest to telegram - automatic PR code review that posts directly on the PR - CI failure analysis that tells you why it broke and how to fix it - stripe payment monitoring that flags disputes as urgent all of it ships ready to go you're not building automations anymore, you're just turning them on
-
Azael (@theazaelov) reportedThis guy makes $20,000-25,000 a month from a dashboard where AI agents push code run social media and close deals for him. No in-house developer. No social media manager. No project manager. At the core is a multi-agent dashboard. It is not one chat with a model. It is a distributed command center where every agent has its own role. Jarvis is the squad lead. Forge writes code. Ghost handles content and SEO. Hype runs social media. Scout digs through research. Closer drives outreach and sales. The whole stack costs $200-800 a month. His command center separates strategy from execution. The owner keeps the strategy. The agents take over the execution entirely. What he does: → The owner sets a goal. Jarvis breaks it into tasks and spreads the cards across the Kanban board between the agents. → Forge creates branches in GitHub opens a PR and ships a site or an MVP. → Ghost writes SEO articles and a changelog. Hype prepares posts and a cadence for the X accounts and fixes broken-image posts. → Scout digs through competitors and new opportunities. Closer collects leads and sends out applications through the outreach pipeline. → Every status flows back into Mission Control. You see what is done what is in review what is stuck and which agent is responsible. → The agents are tied to real assets: Shoa Dev, Moltza, AI Tools Directory, Vydra, ClawHub. Code terminal browser and pricing page are open right next to them. I broke the economics of this command center down into three scenarios. Results: Replacing the team. A manual lineup of a developer an SEO copywriter an SMM a researcher an outreach specialist and a project manager costs $12,000-25,000 a month. The whole AI stack is $200-800. Even at 50-60% of a live team's quality that is $10,000-20,000 saved a month. The setup product. The Shoaf Systems pricing page has three tiers: $199, $499 and $1,499. 20 quick setups 10 business setups and 5 full systems a month bring around $16,465 in revenue and $10,000-13,000 net. The retainer. Support runs $499-1,500 a month. 15 clients at $799 give $11,985 MRR. Together with setup that is $20,000-25,000 a month or $650-830 a day for one operator. If you have ever run several projects at once you know this friction. Either you hire a team for every function and pay from $12,000 a month. Or you tear yourself apart between code content and sales. Or you take on contractors and drown in approvals statuses and blown deadlines. Now he deploys one Mission Control. It unfolds into a matrix of 6 agent roles 7 types of business and 5 ready departments on the marketplace. That is more than 200 configurations of AI teams for any niche without a single new hire. For everyone building an agency a SaaS or a service company one thing matters. A business does not need a smart answer from a chat. It needs constant forward motion of tasks. One chat closes a question. A command center of agents closes a process. At the same time the real power is not in the agents and not in a pretty dashboard. It is in the operational memory that stores decisions texts leads and mistakes. A live team starts from a blank page every time. The system gets sharper with every cycle. In the end he turns an entire operations department into a set of roles and prompts. A new business function is no longer a reason to hire a person. It is just one more card on the board.
-
Kai - Briefing Block (@briefing_block_) reported$META has 3.58B daily users and still only one real business Meta’s subscription push is not a cute product experiment; it is the market finding out how narrow the company’s monetization stack still is. The company has one of the largest consumer distribution networks ever built, but distribution is not the same thing as pricing power. In 2025, Meta did $200.97B of revenue, and $196.18B came from advertising. That is 97.6% of total revenue. Its entire non-ad business was roughly $4.8B, combining Family of Apps other revenue and Reality Labs. That is the real issue. Not that ads are weak. Meta’s ad machine is still elite, with Q1 2026 revenue up 33%, ad impressions up 19%, and average price per ad up 12%. The issue is that AI is turning the old model from a cash gusher into a capex arms race. Meta now expects 2026 capex of $125B-$145B, up from a prior $115B-$135B range, mainly to support AI infrastructure and future capacity. The second business never arrived. Google was also born as an advertising company, but by 2015 it already had about $7.6B of non-ad revenue between Google other revenue and Other Bets. Meta, ten years later, still has less. That comparison matters because Alphabet can push AI through Search, YouTube, Cloud, Android, Workspace, and enterprise channels. Microsoft can route AI through Office, Azure, GitHub, Windows, LinkedIn, and corporate procurement. Amazon can route AI through AWS and commerce. Meta has Facebook, Instagram, WhatsApp, and Messenger. Phenomenal attention networks. Still mostly ad surfaces. Subscriptions are the tell. Meta is rolling out paid plans for Instagram, Facebook, and WhatsApp, while also testing AI subscription tiers. That may generate some high-margin revenue from creators, power users, and heavy AI users. But a few dollars a month for extra app features is not the same thing as Cloud. A paid chatbot is not the same thing as enterprise software distribution. The question is not whether Meta can squeeze some subscription revenue out of billions of users. It probably can. The question is whether it can build a second monetization engine large enough to matter against the AI bill now coming due. Bottom line: Meta does not lack scale. It lacks a proven business model outside advertising, and AI makes that weakness much harder to ignore.
-
WallStreetAIs (@WallStreetAIs) reportedHermes Agent automation blueprints are not just cron jobs with a nicer name. TRUSTTT. They are fully built workflows you can copy, customize, and run right away. Nightly GitHub issue triage that sends a digest to Telegram Automatic PR code reviews posted directly on the pull request CI failure analysis that explains what broke and how to fix it Stripe payment monitoring that flags disputes as urgent Everything ships ready to use. You are not building automations anymore. You are just turning them on.
-
Crypto Freak 🤡 (@FSkifor) reported@keepyourpixel @nikitabier Yo, broooo, thanks for the support. X doesn't give a **** about us; they don't care about small creators. They posted a GitHub with the algorithms so we'd back off and that's it. This social network's algorithms will always be random until some big shot starts talking about the problem.
-
Kurt Woloch (@KurtWoloch) reported@andon_thinking @BoreanTulip @andonlabs Looking into the Github issue, it seems the word Court gets emitted preceeding XML style tool calls, so the Andon Labs harness should check for the word appearing in this place and strip it from the text to be output to the TTS. Happens with Opus 4.8, did not happen with 4.7.
-
Ibro (@axeng200) reported@zigmoo Eh. I didn't expect to see the day I'd agree with that stance. I have been a GitHub user for years and have advocated for it countless times. But after seeing so many issues, and technical problems that shouldn't exist on a platform of this scale (e.g. slow loading and sluggish issues/PRs), it is getting harder to defend. Things have to be snappy, there is no excuse.
-
Amar (@m_amarudinn2) reportedLast month I hired a Solidity dev from a crypto freelance board. Portfolio looked solid. GitHub commits checked out. Three weeks later I found out half the repos were mass-forked templates and the audit certifications were self-issued PDFs I lost 4.2 ETH and six weeks of development time. And I had no recourse because "reputation" in Web3 is just a pfp and a follower count This is the problem nobody talks about: we built trustless money but we still hire people based on trust-me-bro credentials So here is my pitch. Proof of Work Identity A protocol that builds verifiable builder profiles by indexing real on-chain activity. Every smart contract you deploy, every governance vote you cast, every bug bounty you claim, every hackathon submission you make gets cryptographically linked to your identity But here is the part that makes it actually useful: an AI evaluation layer that doesn't just count contributions, it reads them. It analyzes code quality, checks whether your "audit" was a rubber stamp or genuine security work, and scores the impact of your governance participation Employers post bounties or jobs with specific skill requirements. The protocol matches them with builders whose verified history actually demonstrates those skills. No resumes. No portfolio theater. Just provable work The difference from existing platforms? Everything is composable. Your reputation travels across chains. A builder on Arbitrum doesn't start from zero when they contribute to a Base project. Your proof of work follows you, not your Discord handle We have identity solutions that verify you are human. We have reputation systems that count your transactions. But we have zero infrastructure that verifies you are actually good at what you claim to do That gap costs this industry millions every quarter in failed hires, abandoned projects, and rugged freelance work If you have ever been burned by a fake portfolio or a ghost contractor in crypto, you already understand why this needs to exist What is the worst hiring disaster you have experienced in Web3? @RallyOnChain
-
Traceback (@Tracebackqa) reportedThe issue isn’t merging code. It’s proving the change still works. - Traceback is the quality assurance layer for modern software teams: every pull request is tested automatically before it ships. - AI controls the browser like a person would, and self-healing tests keep up when the UI moves. - Failures become trackable work in GitHub, Linear, and Slack; it connects to Vercel, Docker, AWS, Node.js, React, Next.js, and Vue. - Coverage spans web, mobile, web3, and design workflows. Verify every product change before it ships.
-
Wyatt (@wyatt_jia) reported@hzqsns github issues
-
Marcelo Baldin (@mbaldin) reportedYesterday, for a brief moment, Brazilian authorities censored access to GitHub, without explaining why. But since people obviously noticed and depended on that site to work, it was reinstated quickly. However, that's not an unusual behavior from the Brazilian government. Ayub has been alerting to this shady censorship behavior for over 3 years, in which the government is slowly shutting down access to several sites without explanation. For example, Kalshi and Polymarket were banned a few months ago when they presented an unfavorable scenario for the current government. Even though that oscillated, the sites are still off. The Supreme Court set a 60-day deadline for social platforms to comply with an absurd rule requiring them to auto-censor content that "might be considered suspicious against the government," a subjective standard. So X, Facebook, Instagram, etc., will have to remove any content they might consider an "attack against the government". If this pattern continues, the internet in Brazil won't be the internet anymore; it will be a silo.