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
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
Guayaquil, Guayas 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:

  • strawpot_ai
    strawpot (@strawpot_ai) reported

    StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.

  • TechFlowInsight
    Tech flow Insight (@TechFlowInsight) reported

    1/ 266 upvotes & 85 comments — Hacker News thread 'The peril of laziness lost' is sparking debate on how automation reshapes craftsmanship. 🔥 The community argues editor autocompletion (e.g., GitHub Copilot) is nudging engineers away from deliberate problem‑solving.

  • ItBuiDoan
    Đoàn Bùi (@ItBuiDoan) reported

    @ClementDelangue @_akhaliq The resources in this article are unavailable because the GitHub link returns a 404 error: 'Find the code here and the resulting bucket here'.

  • evilsocket
    Simone Margaritelli (@evilsocket) reported

    @Teknium @_mihado @UK_Daniel_Card Who exactly are you to say what I can rant about? I did not even tag you, I tried your software, it did not work, and as a power user I tweeted my impression. You folks need to spend less time on X and more on the github issues page. And maybe learn to take criticism (that you go actively seek for) better.

  • HotAisle
    Hot Aisle (@HotAisle) reported

    @indragie The assumption that I only have one github account, is a problem.

  • emsi_kil3r
    Emsi (@emsi_kil3r) reported

    Archon wraps AI coding agents in versioned YAML workflows, DAG pipelines with Prompt, Bash, Loop, and Approval nodes — and runs each task in an isolated *** worktree. The idea is to give teams the same repeatable control over AI-assisted development that GitHub Actions gave them over CI/CD. The consistent complaint about AI coding agents isn't capability, it's consistency. Ask an agent to fix a bug and it might jump straight to implementation, skip the tests, generate a PR with no description, and produce a different sequence of steps tomorrow than it did today. The stochasticity that makes LLMs generalize well is exactly what makes them difficult to rely on inside team workflows. Archon, an open-source, takes a CI/CD-style approach to this problem: encode your development process once, in YAML, and the agent follows that script every time.

  • web3punk
    StupidWebPunk (@web3punk) reported

    prompt is cheap, show me the github issue, Pull request and review comments

  • MythThrazz
    Marcin Dudek (@MythThrazz) reported

    @a_lamparelli I know! You would think those are free/cheap - they arent. And never were. I think there is actually an issue on Github about it. It misses the KV cache completely afair

  • ligth_daniel
    Daniel (@ligth_daniel) reported

    @jaredpalmer @github @grok can you explain the goal of this feature? which problem does it solve ?

  • AlbahadlyIQ
    albahadly (@AlbahadlyIQ) reported

    @github I want to try it, but unfortunately I can't. I have an issue with renewing my subscription, and I opened a ticket to support 9 days ago, but no luck.

  • crescitaly
    Crescitaly (@crescitaly) reported

    @karpathy @github Friction is the filter. Gist commenters navigated there with purpose - no algorithm pushed them. That selects for people who actually read and think. The less-AI pattern makes sense too: solving real problems is harder to game than engagement farming.

  • the_smart_ape
    The Smart Ape 🔥 (@the_smart_ape) reported

    > find a cool github repo that cuts your ai tokens cost by 50%. > looks legit, 5,247 stars. 120 forks. active issues. clean readme. > clone it. npm install. done. > next morning: crypto wallet drained. locked out of gmail, icloud, x. your private family photos are online. > life will never be the same.

  • arthlimchiu
    Arth Limchiu (@arthlimchiu) reported

    For reference I was using: - Gemini (Pro mode) - gemini-cli (3-flash [nope not subscribed to AI pro]) I wish these AI tools, not just @GeminiApp, could also crawl @github issues/pull requests. Maybe they do already? They should already be right? #LLM #GenerativeAI #AIAgents

  • saksham_sarda
    saksham (@saksham_sarda) reported

    @dok2001 @runable_hq d1 not supporting transactions in a normal way. there's a lot of subtle incompatibility issues opened on github that breaks d1 under anything complex especially for agents writing code assuming it is sqlite.

  • ElyasWahyain
    Abdullah Elyas | ع. إلياس (@ElyasWahyain) reported

    @icanvardar @zerohedge It’s actually a bug, disabling telemetry accidentally blocks the feature flag check that grants 1-hour cache to Max subscribers. It has been filed as an issue on GitHub. The 1h cache is a Max plan perk, not available to Pro users regardless of telemetry settings 🫠

Check Current Status