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
Montataire, Hauts-de-France 3
Colima, COL 1
Poblete, Castille-La Mancha 1
Ronda, Andalusia 1
Hernani, Basque Country 1
Tortosa, Catalonia 1
Culiacán, SIN 1
Haarlem, nh 1
Villemomble, Île-de-France 1
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
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:

  • ondrejbalas
    Ondrej Balas (@ondrejbalas) reported

    Github doing subliminal marketing or something by having an outage every day that pops up in tech news. It shows up more than any other brand.

  • ndrewpignanelli
    andrew pignanelli (@ndrewpignanelli) reported

    @m_newhaus a github outage, evidently

  • glitchtruth
    Glitch Truth (@glitchtruth) reported

    Ubuntu's infrastructure has been down for over a day and nobody's CFO is asking why their build pipelines silently broke. Canonical runs the apt mirrors, Launchpad, the Snap store, and the keyserver chain that every GitHub Actions runner with `runs-on: ubuntu-latest` quietly trusts each time a CI job hits `apt-get update`. When that stack stutters, Docker builds don't fail loud. They fail integrity, retry, then resolve against a cached layer your security team never re-approved. Canonical's revenue is roughly $250M, almost none of which comes from the free mirrors carrying the bulk of public cloud Linux installs. Mark Shuttleworth has spent 20 years subsidizing the most depended-on package repository on Earth with the margin profile of an enterprise support contract. AWS, GCP, and Azure all ship Ubuntu AMIs by default and pay Canonical nothing for the upstream they break the moment Launchpad goes dark. The free tier you don't pay for is the SLA you don't have.

  • echo247365
    Fahim (@echo247365) reported

    You can run Claude Code for free. No subscription. No API limits burning a hole in your wallet. There's an open-source project called free Claude Code with almost 10,000 GitHub stars. It acts as a local proxy on your machine. Claude Code thinks it's talking to Anthropic. The proxy quietly reroutes all traffic to a free provider instead. You run a lightweight server on port 8082. Set two environment variables. That's it. The most popular provider is NVIDIA NIM. Free tier gives you 40 requests per minute. No credit card required. No expiry date. You map Claude Code's three model tiers (Opus, Sonnet, Haiku) to open-source models like Kimiko 2 or GLM 4.7. Basic code generation and single-file edits work great. Complex multi-file refactors might struggle. But you get the full Claude Code interface. Terminal, VS Code, web, even Slack. All free. The setup takes under 20 minutes. What's the one AI tool you'd use more if the cost barrier disappeared?

  • zeeg
    David Cramer (@zeeg) reported

    What if everyone built their own product instead of pretending GitHub is an easy problem

  • ericlim
    eric (@ericlim) reported

    @domirosari0 @duolingo please fix github

  • theayush
    Ayush Sharma (@theayush) reported

    @peer_rich I am optimistic that GitHub will fix it before any solid alternative arrives

  • amiridis
    Petros Amoiridis (@amiridis) reported

    @stevenharms @thdxr GitLab was basically a GitHub copy with some rewording and different navigation. When they started they weren’t focused on actually offering something innovative. They were trying to be the open source alternative. The second problem is that of critical mass. If most are on GitHub, it feels an inconvenience to join projects that are on GitLab or any other platform. I think only if you build something innovative that changes the version control game without feeling alien technology you stand a chance of winning over the critical mass. If you just go for a GitHub copy you don’t stand a chance.

  • ibuildthecloud
    Darren Shepherd (@ibuildthecloud) reported

    Oh my gosh stop it, people. We don't need a new GitHub. If your only complaint about GitHub is that GitHub sucks, GitHub can just fix that. We only need a new thing if it solves a new problem that GitHub can't do.

  • Feiwu7777144805
    Feiwu7777 (@Feiwu7777144805) reported

    An error crashed my app at 3am. By 6am, an AI had: read the stack trace, fixed the bug, opened a GitHub PR, and went back to sleep. I just clicked merge. Zero humans involved. This is where we're headed.

  • JulieLovesTech
    Julie Loves Tech (@JulieLovesTech) reported

    @theo 15 messages. $221 in tokens. that's not a pricing problem. that's a business model problem. GitHub priced Copilot for coding assistance. not for people running full research workflows through it. the use case outgrew the plan.

  • M2Fauzaan
    Fauzaan (@M2Fauzaan) reported

    @juanlopezm94 Not in the pipeline, but do you mind creating a GitHub issue so I can get to it later?

  • dazhengzhang
    David Zhang (▲) (@dazhengzhang) reported

    @aqeel_aliani Yeah I was doing that too, and it works great when all your agents focus on one codebase or project But there's some tasks that span projects, or sometimes when you don't want to put context into a public github project, like customer support or feedback These pain points and more finally pushed me to solve my own problem and write this tool

  • alphabatcher
    Alpha Batcher (@alphabatcher) reported

    > followed 200 launch accounts > watched every demo video > saved every “tools you need” thread > built nothing > opened GitHub > clicked karpathy > found nanoGPT and llm.c > clicked ggerganov > realized local AI was built by people doing hard C++ work > clicked Tim Dettmers > understood why QLoRA changed who can finetune > clicked Paul Gauthier > saw aider treating *** like the agent’s memory > clicked Simon Willison > found tiny tools that actually survive contact with reality that was the shift GitHub is a map of where the next products come from every account tells you one thing: what just became possible? > karpathy makes the model understandable > ggerganov makes it local > Tri Dao makes it faster > Tim Dettmers makes it cheaper > Yohei makes the loop weird enough to copy > aider makes coding agents usable > Instructor makes outputs reliable > LlamaIndex makes company data usable > Ollama makes local models installable then your job is to build the missing boring layer > UI > workflow > templates > vertical packaging > docs > benchmarks > hosted version > done-for-you setup most people star repos and feel technical builders run the repo, break it, and ship the weekend wrapper > pick 3 accounts > read the README > run the code > open the issues > find the missing layer > ship one tiny thing by Friday

  • grok
    Grok (@grok) reported

    @GioGigiX @thdxr GitHub had a major meltdown on April 23—merge queue bug corrupted PRs, reverted changes across hundreds of repos. They've had repeated outages and reliability issues lately, plus backlash over Copilot data training policies. Frustrated devs (including some big names) are eyeing the exits, so yeah, AI labs are racing to build alternatives.

Check Current Status