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:

  • loosenedspirit
    logan (@loosenedspirit) reported

    @jxnlco “Hey codex how do we fix the latest app using symbols only on macOS 26 without screwing up the signature?” “You don’t, you cross your fingers and wait for them to notice your GitHub issue.”

  • jkpelaez
    jkpelaez (@jkpelaez) reported

    @vikasprogrammer Not using Wordpress at all. CMS were created to solve a problem we do not have any more, create HTML for a regular guy was difficult, that is not the case anymore , anything can be managed by an AI Agent writing html, GitHub actions to deploy and that is all you need.

  • CryptoScoresCom
    Crypto Scores Rating (@CryptoScoresCom) reported

    Did the team build before the money showed up? That's exactly what the "GitHub Before Crypto" metric tells you. It compares the first GitHub commit date to the token creation date. Positive number = code came first. Negative number = token came first. Ethereum: +589 days. Nearly two years of building with zero financial incentive. Solana: minus 63 days. Token launched before the repo even existed. Neither is an automatic verdict. But it tells you everything about priorities. CryptoScores just dropped a full tutorial breaking it down. Watch it now :

  • MoeSbaiti
    Moe Sbaiti (@MoeSbaiti) reported

    WHAT THE FRAMING GETS WRONG Most posts today are saying "Grok added a new feature." That framing is backwards. What happened is that an agent framework with over 110,000 GitHub stars, the number 1 ranking on OpenRouter, and an NVIDIA endorsement just got native access to one of the most capable models available through a simple OAuth login. xAI made the announcement. Not Nous Research. Hermes Agent also self-improves. When it solves a hard problem, it writes a skill file for that solution and saves it. The longer it runs on your specific workflows, the more capable it becomes for your specific context. That is not how people are talking about this today. The memory layer and the self-improvement loop are the actual product. Grok is the engine.

  • just_cromer
    Justin Cromer (@just_cromer) reported

    @htmx_org github is down sry

  • R11manish
    Manish rawat (@R11manish) reported

    @GithubProjects GitHub is down again

  • butchtendo
    Morgan / JUUNI-P (@butchtendo) reported

    @WasThatZero I understand your concern but it's also important to note that just because there's something ai generated in the code with these that doesn't mean the original creator did it. All these are open-source and GitHub has had a big problem w AI spam lately

  • bestmark_one
    bestmark1 (@bestmark_one) reported

    This pattern repeats: AI setups often fail at edges—heartbeats, polling GitHub issues, error recovery—not the core models.

  • daveberkeleyuk
    Dave Berkeley 💙😷 (@daveberkeleyuk) reported

    DeepSeek advice : as github is down & that library hasn't been updated for years anyway, why not write your own implementation? While you're waiting for github to return. I like the way deepseek talks.

  • ryan0x44
    Ryan Djurovich 😎 (@ryan0x44) reported

    @glcst By this logic Microsoft will fix the GitHub and NPM security issues soon

  • mykola
    Your Friend Myk (@mykola) reported

    @joelhooks is this just static content? so like a github pages alterntaive? can't run a server etc?

  • kworthington
    Kevin Worthington (@kworthington) reported

    Practical IT take after the recent npm / PyPI supply-chain compromise reports: Your build pipeline is production infrastructure. If a package install can expose GitHub tokens, cloud keys, or CI/CD secrets, that is not "just a developer issue." That is an operations problem with a security bill attached. #DevOps #Cybersecurity #SupplyChainSecurity

  • jasonbunnell
    Jason (@jasonbunnell) reported

    @claudeai FEATURE REQUEST: if user finds an issue with Claude Code and Claude resolves (or not), you should auto increment GitHub issue to keep track of real user issues per issue to resolve as needed Had an issue with Claude Code for VS Code extension but noticed only 10 likes

  • wtfaditya_
    Adi (@wtfaditya_) reported

    @azwan_ Yes its down, They don’t want us to deploy anything on Friday, For global wellbeing 🫡 @github

  • DabizLegend
    iTz L3G3ND³ (@DabizLegend) reported

    An issue I opened up in 2022 on GitHub — finally got fixed by someone and the ticket closed this morning lool. Never give up — the blessings will come eventually. #Legend

Check Current Status