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
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
New Delhi, NCT 1
Kannur, KL 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:

  • Avajonam
    Manojava (@Avajonam) reported

    आपको पता है यदि USA, gitHub पर प्रेशर करके बस ये कह दे कि github service not available to non USA citizens or allied then within a few seconds 70% coding work of world will stop and 80% software will be down ... All mobile, all computers all suddenly collapse .. So much dependency on GitHub every software developer have .. But nothing will happen to China .. Don't be surprised , in 2013 , china put the foundation to cope up with such types of worst scenario cases and they developed their own "Gitee" fully funded by local government. और हम चले विश्व गुरु बनने ..

  • richkuo7
    Rich Kuo (@richkuo7) reported

    @lydiahallie yea but the github actions part is kind of odd, i just copy and paste the issue into claude code, kind of an inconvenience?

  • Saasnext_db
    SaasNext (@Saasnext_db) reported

    TanStack packages got hacked through GitHub Actions cache poisoning 🤯 npm in 2026: “enterprise-grade security” also npm: `npm install` = execute stranger.exe Fix your CI: ❌ `pull_request_target` ❌ shared caches ✅ isolated runners ✅ pinned actions

  • skywalkerr0x
    Haroon (@skywalkerr0x) reported

    The Dart VM running in-browser via WASM uses the built-in ARM interpreter, that's how hot reload works without any server. 7.6 MB gzipped, hosts on GitHub Pages directly.

  • Incultnito
    Incultnito Studios (@Incultnito) reported

    Not entirely the maintainer story it looks like. Anthropic moved the official GitHub MCP to Go (github/github-mcp-server, 29.5k stars). The Node v2025.4.8 build is legacy — but it is still on npm and still in user configs in the wild.

  • realsamratc
    Samrat Chowdhury (@realsamratc) reported

    @JohnnyNel_ Interesting, tell me more ? Like how you start with it like what is your base tracking strategy for the number of tasks/issues ? Do you use linear or github issues?

  • jmatux
    Jose Luis Matus (@jmatux) reported

    From CodeRabbit's analysis of ~500 open-source GitHub PRs: AI-co-authored code has 1.7× more issues than human-only code. Logic errors: 75% more common. Security vulnerabilities: nearly 3× as frequent. The testing surface is expanding. The people covering it are losing ground.

  • stilic_dev
    Stilic (@stilic_dev) reported

    @ManOfSomething1 Then it's best if you ask them in their GitHub issues I don't think criticism like that is deserved if you know how to fix it, especially when the project in question is open-source

  • BeauJohnson89
    Beau Johnson (@BeauJohnson89) reported

    browser debugging is becoming agent infra ChromeDevTools/chrome-devtools-mcp > 39,363 stars on github > official chrome devtools mcp server for coding agents > lets claude, codex, cursor, gemini, copilot, and more control a live chrome browser > performance traces, network requests, console logs, screenshots, and puppeteer automation the point is simple: coding agents cant fix what they cant see terminal logs are not enough once the bug lives in the browser this is the missing bridge between write code and verify the actual app

  • its_anewworld
    its-a-new-world (@its_anewworld) reported

    @Knoebelbroet Post has been removed and the github is down. Wtf are they trying to hide?

  • randomqazaq
    Din (@randomqazaq) reported

    8/9 37) Landing page builder from one sentence 38) RAG pipeline with evals + monitoring 39) GitHub issues manager agent 40) Multi-modal document processor

  • D_E_V_sparsh
    Sparsh Shandilya (@D_E_V_sparsh) reported

    Building Nexus: Give it a Linear issue, it autonomously plans, writes, and commits code to GitHub What's working today: - Planner reads the real ticket + repo files - Coder creates a branch and commits actual working code - Full typed pipeline: BullMQ + custom MCP servers + Groq Reviewer and deployer are next Thread with more details soon 🧵

  • assorium
    Spartak (@assorium) reported

    @heyandras I know a lot of good indians but this is sad pattern. Banning the country from github would solve all the problems it seems.

  • bankkroll_eth
    bankk (@bankkroll_eth) reported

    After the tanstack hack I spent a hours scanning actions across major github orgs and the number of repos sitting on the exact same vulnerability right now is crazy. the tanstack attacker poisoned the Actions cache during a fork PR, then closed it and deleted the branch. ~7 hours 51 minutes later a maintainer merged an unrelated CSS fix and restored the poisoned cache being malicious code that ran inside the trusted release context, grabbed the OIDC token from runner memory, and published 84 packages through tanstack's own pipeline. no npm token stolen. valid SLSA provenance on every malicious version. the PR was gone before anything detonated. three things you actually need: 1. guard your pull_request_target workflows: `if: github.event.pull_request.head.repo.full_name == github.repository` 2. use cache keys that don't overlap between fork PRs and release workflows 3. scope id-token: write to only the job that actually publishes

  • sanbag_
    San (@sanbag_) reported

    @cprkrn EwrGp4tDun3pVvHpidcoWbtSaU5gDpUJwuz3F7gEpump this is the CA find it on pumpfun login w ur GitHub wallet addy click CLAIM CREATOR REWARD FEES

Check Current Status