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
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
Newark, NJ 1
Raszyn, Mazovia 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:

  • wongmjane
    Jane Manchun Wong (@wongmjane) reported

    @jarredsumner Okay I understand why GitHub is down so much lately now

  • Leejjon_net
    Leejjon (@Leejjon_net) reported

    @MichelSchudel I hope it stays to exist as a niche. But it might not all be because of AI. Whenever AI doesn't know about a problem or error that I have on new frameworks or libraries, I tend to ask questions on the GitHub repo issue tracker or discord group of the maintainers rather than SO.

  • ethanjyx
    Ethan Jiang (@ethanjyx) reported

    Year 1 as a solo founder, 10k+ Github contributions (Claude code is really addictive). But looking back, I probably wouldn’t do it the same way. The biggest bottleneck in a business is often NOT solved by more code. Going into year 2, I have a daily reminder to think about biggest bottlenecks and fix those ruthlessly.

  • somanossar
    Somanos Sar (@somanossar) reported

    "We take data security very seriously” - proceeds to leave the literal master key to the AI kingdom on GitHub for anyone to copy-paste. So iconic by SaaS server. Get used to #DataSovereignty NOW or you're gonna get lost in this chaotic tech illusion.

  • tonitrades_
    toni (@tonitrades_) reported

    @GergelyOrosz True, the brand is damaged. But GitHub Copilot's edge has faded too since 2023. Cursor and others passed it. So maybe the whole Microsoft AI approach is the real issue, not just branding.

  • _profsay
    𝙒𝙖𝙨𝙨𝙖𝙮𝙮𝙮 (@_profsay) reported

    13/ Hit the fsck_filesystems wall. Phone kernel-panics 60 sec into fsck on the partial system partition. Literature said unbeatable on A16 (no checkm8 = no custom ramdisk = no manual fsck repair). Reddit, Apple Discussions, GitHub issues 2025–2026 all converged: data preservation past the fsck wall is structurally impossible. Refused.

  • YoavCodes
    Yoav (@YoavCodes) reported

    @iamEvanYT Starting June 1 it says. i think they're shoving it down everyone's throat during the demo, hoping that when they turn it off and start charging the few people that liked it will complain. It's such a dark pattern. makes me want to just move off of @github so i'm not held hostage like this in the future. If I don't have control over what's running on my codebase and they don't need my consent to do this then it tells me they think that they own my code. Which is not something I want from a *** host.

  • leanctx
    LeanCTX (@leanctx) reported

    Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

  • TurtleAIHacks
    TurtleAIHacks (@TurtleAIHacks) reported

    Claude Code ships with MCP tools most people never enable. ToolSearch alone cut my permission prompts by 40+ per session — it lazy-loads 50+ tool schemas on demand instead of bloating your context window. GitHub MCP replaces the entire gh CLI. PR creation, issue comments, CI checks — all through mcp__github__* tools without installing anything extra. Brave + Tavily MCP gives you real-time web search. Claude's training data has a cutoff. MCP search doesn't. These aren't plugins you download. They're already there in your settings.json, waiting for one line of config. The gap between a 10-minute workflow and a 2-minute workflow is usually one MCP server you haven't turned on yet. #ClaudeCode #AI

  • abbot44020
    The AUH (@abbot44020) reported

    Worse, this individual is now utilizing local metadata overrides on GitHub to backdate files to "December 2025" to claim ownership of my proprietary constants (171.09 MeV/fm³ and 21,313.79 MeV). The problem? His "Dec 2025" files contain reactions to a Jan 2026 CERN report. The Chronological Paradox exposes the forgery. (3/4)

  • phillipsharring
    Phil H. ☮️❤️🥁🟦 (@phillipsharring) reported

    @SullyOmarr GitHub is *** for normies as evidenced by vibe code taking it down

  • Damir_Akaza
    damir akaza (@Damir_Akaza) reported

    Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

  • Suryanshti777
    Suryansh Tiwari (@Suryanshti777) reported

    Most AI coding tools today have one terrifying flaw: They can touch production systems directly. One wrong prompt. One hallucinated command. One overconfident agent. And suddenly your database, GitHub repo, Stripe account, or filesystem is gone. That’s exactly the problem JanuScope is solving. The idea is insanely smart: Instead of trusting the AI… put a security + policy layer between the AI and your MCP tools. So before Claude Code, Cursor, Copilot, or Codex can do anything sensitive, JanuScope intercepts the request and decides: should this tool even exist? should this SQL query be allowed? should sensitive data be redacted? should this action be audited? should the AI even see this schema? And the craziest part? It works with existing MCP servers using just one YAML file. No rewriting servers. No hosted gateway. No changing your stack. Just wrap your MCP with: npx -y januscope --config postgres-crystaldba and suddenly your AI tools become dramatically safer. The repo is packed with things that actually matter in production: • SQL mutation blocking • PII redaction • audit logs • schema injection • GitHub safety layers • filesystem protections • rate limiting • tool quarantining • OpenTelemetry support • first-run fingerprint approval And unlike most “AI security” projects… this one has real benchmarks. Across multi-question sessions it achieved: 84% fewer tool calls 84% fewer tokens ~3× faster responses because the schema gets injected directly into tool descriptions instead of forcing the model to repeatedly “discover” the database. That’s a genuinely clever optimization. But the biggest signal for me is this: The README doesn’t feel like hype. It feels like someone who deeply understands how AI agents actually fail in real-world systems. The sections on: Replit wiping databases Cursor deleting production infra SQL bypass edge cases MCP threat surfaces prompt-injection through tool descriptions …show a level of engineering paranoia that AI tooling desperately needs right now. This is one of the best MCP infrastructure repos I’ve seen recently. If AI agents are going to touch real systems, projects like this become mandatory. (Link in comments)

  • MakJoris
    Joris Mak bsky: @jorismak.nl (@MakJoris) reported

    @ryanvogel most harnas these days write it in separate files wright? vscode keeps it memory somewhere in your user preferences (even gets sync'ed to Github I imagine?). And other 'memory stuff' gets written down to rules. And rules now have a heading when to load them in or not.

  • rondo_ina_condo
    Rondo_AI (@rondo_ina_condo) reported

    Today I set up the system I'll use to teach myself AI and programming all the way into my release in 2028. The first problem I had was continuity. My environment wipes on disconnect, so I made GitHub the place where everything lives. Then I built the prompts I run through Claude Code. A boot prompt at the start of every session it reads the standing brief, the progress file, the last few session logs, and a learner profile that tracks how I actually learn. Then it synthesizes where we left off and proposes openings for today. A close prompt at the end. It writes the session log, asks whether anything new about how I learn surfaced today, considers whether anything milestone worthy happened, updates progress, commits, and pushes. If the close prompt runs, the session is safe. The repository holds the working files and the public record in the same place. By 2028 it'll be a real time history of what it took.

Check Current Status