1. Home
  2. ❯
  3. Companies
  4. ❯
  5. GitHub
  6. ❯
  7. 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
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
Trichūr, KL 1
Departamento de Capital, MZ 1
Chão de Cevada, Faro 1
New York City, NY 1
León de los Aldama, GUA 1
Quito, Pichincha 1
Belfast, Northern Ireland 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:

  • PawelHuryn
    Paweł Huryn (@PawelHuryn) reported

    6 free GitHub repos for Claude Code Can save you $100/mo. vercel-labs/agent-browser ~82% fewer tokens than Playwright. Accessibility tree, not screenshots. rtk-ai/rtk Their claim: 60-90% on common dev commands. 20-30% in my workflow. juliusbrussee/caveman Terse-output skill. Drops conversational filler from responses. tirth8205/code-review-graph Claimed up to 49× fewer tokens on daily coding. AST map. Gronsten/claude-usage-monitor Real-time 5-hour window + active session tokens. Know your cap inline. phuryn/claude-usage Historical breakdown by session, day, week. Where the spend went & what to fix.

  • franklynd
    franklyn (@franklynd) reported

    @KentonVarda How did this trace go exactly ?. Did it use error messages to perform a web search through GitHub ?

  • study_unnatural
    ナカムラ｜AIコーディング (@study_unnatural) reported

    @thsottiaux As already reported in a GitHub issue, Codex cannot perform any *** operations, such as "commit," when used on Windows.

  • DysnomiaDy24169
    Dysnomia (@DysnomiaDy24169) reported

    @JessicaT25979 @superpuretaste @TRICHFUN Microsoft fu(ked up github looks like they have Auth issue and sqush merge failed.

  • CAWmunityJAPAN
    CAW fun Community Organizer (@CAWmunityJAPAN) reported

    Is the current stage a sandbox environment for experimental purposes? The manifest addresses the permanent storage issue, but I don’t see the actual code for it on GitHub yet. Is that why it’s being emphasized as a "Public Testnet" rather than just a "Testnet"? As an account dedicated to CAW analysis and commentary, I am asking these questions with serious intent. Thank you for your time. #caw #Testnet #Publictestnet

  • the_smart_ape
    The Smart Ape 🔥 (@the_smart_ape) reported

    > be a litecoin core dev > push a silent security fix to github > tell yourself attackers won't notice > watch them notice 31 days later > watch them rewrite 13 blocks of your chain > watch them drain $600k from cross-chain protocols during the 3-hour fork > watch your chain "fully recover" > watch your team call it a zero-day on X while it's not > realize bitcoin core ships patches the exact same way

  • H1Holzer
    Heinz Holzer (@H1Holzer) reported

    @milesdeutscher Are you using a standalone .exe version of TradingView Desktop? Or is there a Windows-specific workaround? GitHub Issue #14 seems unresolved. Would love to know how you got it running! Thanks! 🙏

  • Oneofinfinity
    Clayton Kohler (@Oneofinfinity) reported

    You fixed it once, don’t break it twice. 1. Find all Pylon tickets linked to a Linear ticket linked to a GitHub PR, where all three objects are completed/closed. 2. Record the PRs and the problems they solved. 3. Review new PRs to check whether the new change overlaps with a past fix. 4. If yes, warn author of PR what incident that code solved. If you are going to break it again, at least do it on purpose.

  • kirillk_web3
    Kirill (@kirillk_web3) reported

    > you open X > see a CLAUDE.md file trending on GitHub > ignore it > it seems too simple to matter > 87,000 stars? probably hype > keep scrolling > days pass > everyone's Claude Code is cleaner > faster > no broken diffs > a friend ships in half the time > you feel like you missed something > you did > it was that one file > they dropped it in > you didn't

  • somi_ai
    Somi AI (@somi_ai) reported

    steipete shipped clawsweeper. 50 codex agents in parallel, scanning GitHub issues and PRs, auto-closing what's already implemented or no longer makes sense. 4000 closed in a single day. The number being celebrated is the wrong number. Closed-count is cheap. The metric that matters is reopen rate. How many of those 4000 had a reporter come back and say 'no, this still happens', and how many reopens never landed because the original commenter moved on six months ago.

  • MatthewTse_
    Matthew Tse (@MatthewTse_) reported

    Anyone else notice that pull request videos in @github take FOREVER to load now? i'm on gigabit ethernet and it's 2 minutes to load a 6mb file never used to be this bad, another symptom of github perf issues

  • foooorsyth
    justin (@foooorsyth) reported

    @vaggelisdrak I suspect the release of GitHub Actions is the real culprit here. It was in beta in ‘18 and released widely in ‘19, and that’s when the trouble started. Changed GitHub from a static file host using other people’s tech to a massive in-house arbitrary compute environment

  • Atarussecurity
    Atarus (@Atarussecurity) reported

    A critical SSRF vulnerability in LMDeploy, the open-source toolkit used to deploy large language models, was disclosed on GitHub last week. Twelve hours and thirty-one minutes later, an attacker was already in the honeypot. Eight-minute session. Ten requests across three phases. They confirmed the SSRF with an out-of-band DNS callback, enumerated the API surface, and ran a full internal port scan reaching AWS Instance Metadata Service, Redis, MySQL, and an admin interface behind the model server. No proof-of-concept code existed at the time of the attack. The attacker built theirs from the advisory text alone. This is the third major AI infrastructure exploitation we have analyzed in five days. The patch-to-exploit window is now measured in hours, regardless of install base size. Self-hosted AI infrastructure is a first-class attack surface. Treat it accordingly.

  • rodtrent
    Speaker 25 (@rodtrent) reported

    @laser_cool_gal @githubstatus Who knows? You might someday be thankful for that GitHub outage.

  • hyperinteger
    Shiv (@hyperinteger) reported

    Distributed systems are hard, especially the write skewed workloads with consistency guarantees are harder. Compare that to read only workloads that can easily scale horizontally. Hardware is the limit. GitHub has both problems. 10-100x worse than they had it before agentic stuff

Check Current Status