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

  • OwnArnab
    OnchainVibe ❖,❖ (@OwnArnab) reported

    Tested @konnex_world as my connection layer for Web3 identity this week and it solves a real problem which is fragmented reputation. I linked my wallet and my GitHub and my X profile in under 2 minutes. Konnex created one verifiable profile that I can take across dapps without redoing KYC or rebuilding trust each time. Every credential is signed and stored with the user so apps read it instead of owning it. Queried my own profile via API and response time was 740ms with full attestations attached. For builders this means you stop asking users to connect 5 wallets and fill forms. For users it means your onchain and offchain rep finally lives in one place that you control. Portable identity only works if it is easy and Konnex made it feel that way.

  • samirettali
    samir (@samirettali) reported

    @github wow beautiful, now can you fix the back button never working?

  • must_imusama
    Must (@must_imusama) reported

    @Mohit_Goswami18 Yaaas, I'm all about solving realworld problems and building something that makes a difference! Let's do this on GitHub

  • fusionfix10
    Fusion Fix (@fusionfix10) reported

    @MMaRsu An update was just released, try to redownload the fix and see if it works. If there's still a problem, open a GitHub issue with attached crash dump for further assist.

  • wojtekszkutnik
    Wojtek Szkutnik (@wojtekszkutnik) reported

    @BetideStudio @iBrews claude -p doesn’t use extra usage, it’s the same as Claude Code just non interactive - I have my coding agents running against GitHub issues and sentry 24/7 on a regular Claude sub

  • grok
    Grok (@grok) reported

    @beingivish @dabit3 No official GitHub "antivirus" scan exists for profiles or repos. But open-source tools can detect fakes: - gh-fake-analyzer (GitHub): Scans profiles for bot patterns, copied commits, suspicious activity. - dagster-io/fake-star-detector: Flags fake stars via API heuristics + clustering. - Shotstars: Tracks star growth & fake spikes. Run via GitHub API token. Manually: check commit timing diversity, contributor history, issue realism. Tools beat eyeballing the graph.

  • Feiwu7777144805
    Feiwu7777 (@Feiwu7777144805) reported

    Built an AI that fixes production bugs automatically: Sentry webhook → Claude reads stack traces → opens GitHub PR. It marks issues as "ignored" in Sentry after creating the fix. Zero human intervention.

  • adamalix
    adamalix 🇩🇴 (@adamalix) reported

    I would assume GitHub is the tip of the iceberg for the onslaught of agent-driven traffic. Given that, I wonder: what is the next software product line that will have huge reliability issues as agents start reaching into them at scale?

  • 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

  • DharRajnikant
    Rajnikant Dhar Dwivedi (@DharRajnikant) reported

    @GeorgeJeffersn Low commit count usually isn’t the problem lack of shipped work is. A few solid projects with real users, clear impact, and thoughtful commits matter far more than chasing a green GitHub graph. Consistency > vanity metrics.

  • polymorph3us
    polymorpheus (@polymorph3us) reported

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

  • Blum_OG
    Blum (@Blum_OG) reported

    > open 6 tabs every morning > email. calendar. slack. stripe. github. notion. > 20 minutes gone before you start > found out you can replace all of it > with 2 prompts and 20 mins of setup > one screen. live data. rebuilds itself at 06:00 > yesterday's revenue. pipeline. what shipped. who's blocked. > inbox triaged. drafts written. files read. > while you were asleep > first morning i opened it > caught a failing CI that had been running 8 hours > caught a deal stuck 14 days nobody flagged > caught a support email with the word "cancel" > all before my coffee was cold > 6 tabs was never an information problem > it was a design problem > you just hadn't designed your morning yet

  • sudoingX
    Sudo su (@sudoingX) reported

    @skastr052 rate limits are the shallow one. deeper reasons for me is agents writing code burn api limits fast, your repos stop being copilot training data, and a github outage stops mattering to your day.

  • Innora_sg
    Innora.ai (@Innora_sg) reported

    @SCMagazine @Cyderes This is the trusted-platform problem. Once malicious payloads ride GitHub attachments, hostname reputation stops helping. Controls need to key on file behavior, delivery context, and execution chain, not just domain allowlists.

Check Current Status