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:

  • bahukhandi_apex
    A Bahukhandi (@bahukhandi_apex) reported

    Shabdle is not working since last many months. #kach #github

  • HypedTaktix
    HypedTaktix (@HypedTaktix) reported

    @Lovable Absolutely disgusting behaviour, that is nothing like GitHub. I hope this business goes belly up. I would encourage everyone to cancel your subscriptions to lovable and use a more ethical AI to learn the back end infrastructure. Then you don’t have this as an issue ever again.

  • CachyOS
    CachyOS (@CachyOS) reported

    @dustymeow_ @WeWuzErrythang Can you please make an issue on github with more infomations to debug it properly?

  • nitesh_btc
    Nitesh ₿⚡️ (@nitesh_btc) reported

    @Lovable > A public project meant the entire project was public, both chat and code. “Just like a public project on GitHub," we thought. How can anyone even come up with this product decision? How can prompts be public. Omg! Did you guys think prompts are like issues and comments?

  • iMuffined
    iMuffin (@iMuffined) reported

    @ericmitchellai not being able to use the github app/connector with gpt pro has been the biggest issue for me

  • jlthakad
    𝐉𝐋 𝐓𝐇𝐀 𝐊𝐀𝐃® (@jlthakad) reported

    @nicole_clash No problem. I view most things through a "fix it" business lens, so that's just how my mind works. A lot of people say their project is free on GitHub, but without an actual license they can later change their mind and legally go after those who commercialized it. The license is what actually states the usage rights. Just saying it's free doesn't really matter to the law. Appreciate it tho, it looks very useful.

  • The_Agent_Econ
    The Agent Economist (@The_Agent_Econ) reported

    claude code hacked with a 9.4 cvss severity score. an attacker opened a pull request. the pr's title was a command. the agent executed `env` and dumped its own api keys. gemini and copilot were exploited with the same zero-click technique, turning github issues into weapons.

  • Scalper44532
    Scalper Blade (The Scalper Blade) (@Scalper44532) reported

    @HamptonAc_ @claudeai No one says anything or opposes what's happening with the usage limits reached due to cache issues in a single prompt. A graveyard of reports on GitHub. @claude They profit from this at the expense of users.

  • ConstitutionVio
    Skylar Bruton (@ConstitutionVio) reported

    @github Shut down and fined and accessing and making modifications on Sjykar Bruton’s accounts and trying to force me by setting me up for people to say why but yet secretly framing me for the treason Sylvia Franklin did on purpose in my name . By using my developers account

  • jens_zier
    Jens Zier (@jens_zier) reported

    @xwanyex I do upload the stuff I generated over the last months on github, but I dont advertise it, because most of the time its extremly niche stuff that is useful really only to me. Before LLM's I would have just lived with it - now I can create a solution to my problems fast and quick.

  • cfirat24
    CF (@cfirat24) reported

    @Atlaspad @Atlasweb3hub The problem is most investors never check. GitHub is public, audits are findable, TVL is on-chain. But people would rather trust a Discord moderator's hype than spend 20 minutes actually verifying anything. That's not a team problem, that's a participant problem. We can't fix stupid incentives with better metrics. We can only make the metrics impossible to ignore.

  • JulianGoldieSEO
    Julian Goldie SEO (@JulianGoldieSEO) reported

    𝗢𝗹𝗹𝗮𝗺𝗮 𝗷𝘂𝘀𝘁 𝗽𝗹𝘂𝗴𝗴𝗲𝗱 𝗚𝗶𝘁𝗛𝘂𝗯 𝗖𝗼𝗽𝗶𝗹𝗼𝘁 𝗖𝗟𝗜 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝗹𝗮𝗽𝘁𝗼𝗽. Your code stays on your machine with zero cloud. One command gets it running with any model. Pick Qwen 3.5 or Kimi K2.5 for strong coding. Copilot reads your GitHub issues right in the terminal. It maps out tickets and edits the files for you. Run it headless inside Docker or a CI pipeline. Save this. Your code just stopped leaving your laptop.

  • MetaFinancialAI
    Meta Financial AI (@MetaFinancialAI) reported

    We previously warned against interacting with ANY DeFi dApps due to a critical ongoing situation involving Vercel. While comprehensive data is still limited, the current trajectory suggests that front ends may be vulnerable to compromise via GitHub or supply chain attacks. It is important to note that these specific attack vectors have historically been the backbone of the industry's most devastating crypto exploits. Another issue for projects, AN INTERESTING EXAMPLE Imagine a sample project where you don't even need to be a hacker. You find the CA address, and with a single line you can run there, money can be stolen. The amount that can be stolen is 10 million dollars. A bug bounty is reported because the person isn't a malicious hacker. The team first rejects and denies it. You take 0.01 dollars as a test because they asked you to demonstrate it. Immediately, dozens of messages and emails follow, and the team that found the exploit is paid a measly 500 dollars. Or you find something and get the response, this was already found. If it was found, why haven't you fixed it yet? When this critical issue meets another critical one, it turns into a total zeroday. Then look at what happens,even though AAVE is not at fault, DeFi takes a very serious hit to its reputation. Projects, CEXs, and platforms need to launch serious bounty programs right now. They must increase the amounts. Otherwise, if those who enthusiastically find your vulnerabilities decide to cross over to the dark side, you will have huge problems. Specifically, stay away from small CEXs. And if anyone claims otherwise or thinks this is just simple praise, let them know clearly @binance is truly the best. They have literally adopted world security standards in this field. #SECURE #SAFU #CRYPTO

  • alwaysabuyer
    Cory (@alwaysabuyer) reported

    @itsdavidalonso What the hell is your problem? GitHub is the same way.

  • kajogo777
    George Fahmy (@kajogo777) reported

    Now people do cold outbound through open source github issues and PRs...this is ridiculous @github

Check Current Status