1. Home
  2. Companies
  3. GitHub
  4. Outage Map
GitHub

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
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
Brasília, DF 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
Berlin, Berlin 2
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 1
West Lake Sammamish, WA 3
Parkersburg, WV 1
Perpignan, Occitanie 1
Piura, Piura 1
Tokyo, Tokyo 1
Brownsville, FL 1
Check Current Status

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:

  • farhanhelmycode
    Farhan Helmy (@farhanhelmycode) reported

    down again ? imma kms @github

  • V_Yashwant
    Yashwant Vijayakumar (@V_Yashwant) reported

    @svembu Sridhar ji @svembu I recently started paying 40$ a month for Github copilot in order to avail Claude Opus 4.7, a huge step up from Sonnet 4.6 which was underperforming for my coding tasks. With Opus 4.7, now I'm having to understand how it solved my problems than the other way around. My point here is that as we are debating whether it understands the world sufficiently or not, the models are steadily improving their depth. I used think of Claude models like Forrest Gump, quick to react but superficial. These days I feel like I'm Forrest. With due to respect to @fchollet , let me tell you he also may not be able to keep up with the pace of "recursive self improvement" happening now with every new release. Let's not peddle narratives of somebody else, even if he's an expert in the domain.

  • TheWhizzAI
    The Whizz AI (@TheWhizzAI) reported

    🚨Elon Musk just open-sourced the algorithm that controls what 600 million people see every day. Not a summary. Not a blog post. The actual production code. Live on GitHub right now. Facebook won't do this. TikTok guards it like a state secret. Instagram calls it proprietary. X just put it on the internet for free. This is the first time in history a major social platform has released its live, production-grade recommendation algorithm the same day it went live for users. Here's what's actually inside: →Home Mixer the orchestration layer that assembles your entire feed →Thunder stores and ranks every post from accounts you follow →Phoenix the Grok transformer that mines the entire global post library to find content you didn't know you wanted →Zero manual feature engineering Grok watches what you click, like, and dwell on. That IS the algorithm. →Updated every 4 weeks with full developer notes. Live. In public. Why did Musk do this? The EU fined X €120 million for transparency violations. France launched a separate investigation into algorithmic bias. Threads just overtook X in daily active users for the first time. And Musk said out loud on the day of release: "We know this algorithm is dumb and needs major improvements. But at least you can see us struggling to fix it in real time. No other social platform would dare do this." Here's the wildest part: You can now read exactly why your posts go viral. Or why they die at 12 impressions. No more guessing the algorithm. No more $500/mo "X growth" courses. No more "post at 9 AM on Tuesdays" nonsense. The answer is literally in the code. Apache 2.0 license. Full source. Updated monthly. The most transparent thing any social platform has ever done.

  • kenbono13
    闇ぼの@𝕏級ピンク珍獣.rs (@kenbono13) reported

    @mcsetty @bee_fumo Most software that directly uses GitHub for the download, build, installation (NOT using the AUR) aren't installed under root in the first place. It's installed under $HOME so it wasn't an issue. AUR is the exception since it uses the Arch build system.

  • wtfaditya_
    Adi (@wtfaditya_) reported

    As github actions are down, I was thinking what if they were using actions itself to deploy their service, How they gonna fix it (deadlock) And if they are not using github actions then why should i use if they are not using itself @GitHub any help?

  • techstermania
    Bro Techster (@techstermania) reported

    Github issues tonight?

  • zeeg
    David Cramer (@zeeg) reported

    @eternalmagi dont have context, is there a github issue by chance

  • DeBrosOfficial
    DeBros (@DeBrosOfficial) reported

    The Problem We’re Solving🫡 Your organization’s brain lives in 12 different places — and none of them talk to each other. Decisions get buried in Telegram threads. Context is split between GitHub and AnChat. Important knowledge disappears within hours. Onboarding becomes tribal knowledge all over again. 🤖AnBuddy fixes this by becoming the single source of truth for your entire team.

  • Ananselab
    John Evans Okyere | TheAISolutionist (@Ananselab) reported

    Deployment failed with: dial tcp :22: i/o timeout The app was fine. SSH was fine. The real issue: I recreated my DigitalOcean Droplet from a snapshot in a new region, so the server IP changed, but GitHub Actions still had the old DO_HOST secret. Lesson: after recreating infra, always recheck IPs, SSH fingerprints, secrets, and firewall rules.

  • AtomicNodes
    AtomicNodes (@AtomicNodes) reported

    Hermes Agent vs OpenClaw on Qwen 3.6 Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb. OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

  • Zackary_Chapple
    Zack Chapple (@Zackary_Chapple) reported

    @_bgwoodruff That is fair, I think its less of a GitHub dunk and more of a cry of frustration, had several times trying to do a demo or do something this week and they were fundamentally down. We've had to isolate from GitHub more than we should and thats a scary thing.

  • pedroshakoor
    Pedro (@pedroshakoor) reported

    MCP is growing fast, but the tooling around it is still messy. Servers are scattered across GitHub repos, Discord threads, and random docs. So I built an open-source MCP Switchboard. One connection for your agent. Then the switchboard handles discovery, routing, permissions, API keys, rate limits, and audit logs behind the scenes. Instead of configuring every MCP server one by one, you register them once and route tool calls through a single hub. Claude, Cursor, Windsurf, custom agents, or REST clients can all hit the same layer. The first version includes: Registry API Smart proxy Per-tool permissions JWT + API keys Rate limiting Audit logs Health checks Web dashboard AI server recommendations Docker setup MIT license Before: every agent needs its own messy MCP config. After: one hub connects to many backend MCP servers. Now imagine this as the missing app-store layer for agents. You describe the task. The hub finds the right tools. Your agent gets access without you manually wiring every server, every time. MCP does not need more scattered lists. It needs infrastructure.

  • atomicbot_ai
    atomicbot.ai (@atomicbot_ai) reported

    Hermes Agent vs OpenClaw using Qwen 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

  • Aggroed001
    Aggroed Lighthacker- Peace, Prosperity, & Freedom (@Aggroed001) reported

    If you're buil;ding with AI consider telling your agent to save versions like github, backup versions daily at least, and break harder problems into bite sized pieces, and tell your agent to write readme files for itself. You don't want a random reboot or reversion to kill you.

  • lux_sp4rk
    Lux Sp4rk (@lux_sp4rk) reported

    I dunno why I even humor this html > markdown trend. It's clearly not. Reality is that Markdown renders to HTML anyway. I.E: A Github issue is *not* raw markdown. The ByteRover argument relies on a false dichotomy.

Check Current Status