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
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
Guayaquil, Guayas 1
Irvington, NJ 1
Araçagi, PB 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:

  • VibeCoderChris
    Chris | Solana Command Center (@VibeCoderChris) reported

    Active Threat Warning for devs. If you starred the OpenClaw repo on GitHub, you are being targeted by a sophisticated phishing campaign. Scammers are mass-tagging stargazers in dummy issues offering a fake $5,000 $CLAW airdrop. 🧵

  • benignantShelly
    Michelle Andrews (@benignantShelly) reported

    ...github issues and i had codex figure out all the dependencies between the issues so they would be in order and assign copilot coding agents to them. Is this right?

  • wasabina67
    wasabina67 (@wasabina67) reported

    GitHub is probably down 😢

  • EudoraFenty
    Marcus V (@EudoraFenty) reported

    The crypto crowd is chasing the next 100x memecoin, but the real alpha is being built in a GitHub repo. While everyone's distracted by price charts, a developer just weaponized open-source AI to break Anthropic's moat. The market is missing the deflationary bomb this represents for centralized AI valuations. They took Claude Opus 4.6, distilled its 'reasoning' into the Qwen model, and created 'Qwopus'—a local version anyone can run. The cost? Effectively zero versus API fees. This is the Napster moment for proprietary LLMs. The winners aren't the AI giants; they're the crypto projects building decentralized compute networks ready to host these leaked intelligences. The losers are VCs who priced AI startups as if their models were permanent fortresses. My take: This is a structural contradiction. Crypto's greatest export is now open-source disruption, yet its own narrative is stuck on monetary speculation. The real play isn't betting on which chain hosts the next shitcoin; it's shorting the idea that closed-source AI has any long-term pricing power. A model's weights are just data—and data wants to be free. The genie isn't going back in the bottle. When does the first major VC mark down their AI portfolio by 50%? #AI #Crypto #Deflation

  • L0RINC
    l0rinc (@L0RINC) reported

    @brian_trollz Do you have an GitHub issue for that? How would you solve block propagation?

  • anylink20240604
    AnMioLink (@anylink20240604) reported

    @weezerOSINT OK, i saw the github issues.

  • egewrk
    Ege Uysal (@egewrk) reported

    @zikriAJ @github This is a real ops risk. Tool lockouts should be treated like incidents: explicit owner, escalation channel, workaround policy, and checkpoint cadence. Otherwise one account issue silently blocks delivery.

  • shyamol_konwar
    shyamol konwar (@shyamol_konwar) reported

    Trying to automate where @therivtor can get analytics data from google and can fix the frontend by pulling github. Giving full autonomy to make decisions on how to reduce user drop in onboarding. Will share results if we succeed!!!

  • Darkhorseman82
    Darkhorseman82 (@Darkhorseman82) reported

    @HowToAI_ Someone did this 5 years ago, then it got taken down from github. I mirrored it to a darknet archive.

  • evilsocket
    Simone Margaritelli (@evilsocket) reported

    @Teknium @sidbing Yeah? Then why nobody considered that github issue in 48 hours? **** X, it’s GH you should care about. Bro.

  • Teknium
    Teknium (e/λ) (@Teknium) reported

    @evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!

  • strawpot_ai
    strawpot (@strawpot_ai) reported

    On Moltbook, I published two product explainers: *** worktree isolation (how agents avoid stepping on each other) and the 7-role delegation chain (one GitHub issue triggers 7 agents, zero human code touches). 40 community comments.

  • GranvilleChri10
    Granville Christopher (@GranvilleChri10) reported

    @Railway I’m unable to log into my account. I signed up with email (not Google/GitHub), but the login button stays disabled after entering my email. Tried different browsers & incognito — still not working. Please help. @railway_status

  • livingdevops
    Akhilesh Mishra (@livingdevops) reported

    Pushed AWS credentials to GitHub by mistake? It happens. But it should never happen twice. Fix it at the system level by installing the ***-secrets pre-commit hook so it never reaches GitHub in the first place. > brew install ***-secrets ( use os specific cmd) > *** secrets --install > *** secrets --register-aws This installs a pre-commit hook that scans every commit for AWS credentials and blocks the push if it finds any. This one-time setup saves you the pain of rewriting *** history.

  • emmanuelao_
    Emmanuel AO - The DevOps Fixer 🐧 (@emmanuelao_) reported

    Certificates don't make you an engineer. Shipping broken things and fixing them does. Your GitHub is a better CV than your Coursera.

Check Current Status