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
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:

  • Answerislove2
    Petal Tanya (@Answerislove2) reported

    @grok default my-app (client_id: QjhubXph…) Only get the 2FA prompt when you (Grok) push from within openclaw terminal for me using that github link you sent, I gave it to you down there, a 0auth2bot you created got it to pop 2FA one time and then straight fail. You tried 2 callbacks like you wanted to up here but it doesn't allow, you tried the single ones. You tried 3 platforms like a champ. I think I cried a little and debated some whiskey but kept listening to 3 versions of you cuz all 3 of you are smarter than me lol

  • The_Sublimatory
    Sublimation Chamber ⚗️ (@The_Sublimatory) reported

    @S1r1u5_ @gleech Yeah I think in a decade every time you you try to push, GitHub will just run a mythos+ level ai on it for free and if there are vulnerabilities it will give you a standard “failed to push” type warning and ask if you want to manually fix it or just let them automatically do it.

  • dotblok
    BLOK® (@dotblok) reported

    They plugged Auth0, Google, or GitHub into their auth layer. Convenient. Documented. Widely used. But now their users' identity lives on someone else's server. One API deprecation. One terms change. One outage. And your users lose access. Not Google's problem. Yours.

  • nullbytes00
    Shobhit - Building SuperCmd (@nullbytes00) reported

    @GuriaFS @GuriaFS Yes, i identified the issue. i actually had put in the wrong version in the json (1.0.2) but the github version tag was on the 1.0.3

  • popyop45yt
    Mari (@popyop45yt) reported

    @corrupthemall @Bonphia They switched the GitHub and main dev for ryubing at some point. Old links for issue tickets lead to a non existent ryubing. And the main dev is no longer Mr green dev but that could be unrelated but it is said on the website that Mr green dev is the dev and it’s weird he’s not

  • WeLivetoServe
    We Live to Serve (@WeLivetoServe) reported

    @jackccrawford @MatthewBerman local subscription cli managing claw agent on server in a github gist literally the only useful aspect of gist

  • madewithv
    V (@madewithv) reported

    @github how about simply fix the uptime?

  • LiveOverflow
    LiveOverflow 🔴 (@LiveOverflow) reported

    Business idea: 1. spam GitHub with terrible insecure code, fake dependencies, fake exploits, ... 2. sell the list of repositories to AI training companies so they can exclude it from the dataset

  • vmvarg4
    VM Varga (@vmvarg4) reported

    @ask_alf @MatthewBerman Great tool. Works for my openclaw flawlessly. Does not work for my Hermes. All on the same machine. Gonna open a GitHub issue later

  • AndeanViber
    Andean Viber (@AndeanViber) reported

    @IntCyberDigest @0x686967 By default GitHub repos are Public... It's a major problem

  • polymorph3us
    polymorpheus (@polymorph3us) reported

    @windsurf login-in-browser appears to be broken. login w/ github -> redirected back to login page

  • sergiopreira
    Sergio Pereira (@sergiopreira) reported

    A CLAUDE.md file is the #1 trending repo on GitHub - 68k stars. But this is a v0 workaround. Text files describing the codebase going stale the moment code moves. The actual unsolved problem is 'can AI keep understanding your code as it drifts'.

  • TechInnovationz
    TechInnovation (@TechInnovationz) reported

    $IonQ $NVDA NVIDIA just open-sourced an AI decoder that fixes quantum errors in under a microsecond. GitHub, Hugging Face, free. arXiv 2604.12841, posted yesterday. Up to 3.5x faster than the previous best. Remember when Jensen Huang said quantum was “15 to 30 years away” in January 2025? A year later, NVIDIA is shipping production code for the hardest classical problem in fault-tolerant quantum computing. The tone changed. Quietly. The work didn’t. Ballance, two days ago: “physics is a sunk cost, what matters is engineering.” This paper is the classical half of that thesis. The quantum company that wins isn’t the one with the prettiest physics demo it’s the one plugged into the fastest classical stack. IonQ is on NVQLink, the transmission layer this decoder rides on. $IONQ $NVDA #IonQ #QuantumComputing

  • Timur_Yessenov
    Timur Yessenov (@Timur_Yessenov) reported

    @aakashgupta codex github has users filing issues about arbitrary limit resets killing sessions mid-task. surplus gpu hours don't fix broken dev flow

  • cmdcntr
    CMD CNTR | Web Engineer Experts (@cmdcntr) reported

    Your developer probably knows SHA-1 is being deprecated on GitHub. They haven't told you. And when your automations break on September 15, they'll fix it and call it maintenance.

Check Current Status