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
Itapema, SC 1
Cleveland, TN 1
Tlalpan, CDMX 1
Quilmes, BA 1
Bengaluru, KA 1
Yokohama, Kanagawa 1
Gustavo Adolfo Madero, CDMX 1
Nice, Provence-Alpes-Côte d'Azur 1
Brasília, DF 1
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 1
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
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:

  • spbalaonline
    spb krishnan (@spbalaonline) reported

    @abhijeet_dipke Cockroach Party website taken down? Here's how to make it resilient:• Move domain to Njalla/Porkbun + Cloudflare proxy • Host static version on IPFS + Vercel/Netlify • Mirror on GitHub Pages+ offshore VPS • Daily backup+.onion version Decentralize like real cockroaches.

  • ManOnChainX
    Man | Research (@ManOnChainX) reported

    @tomosman $GITBANK ? Because of they also working on Github users for if any user has error and solve by other person and give bounty then need to go centralized or paypal.. so Gitbank is building wallet in github so the escrow will send automatically when task complete...

  • Atenov_D
    Atenov int. (@Atenov_D) reported

    @Mnilax And most users miss these settings because they dont read GitHub issues.

  • 13F_Pro
    13F Pro (@13F_Pro) reported

    @FirstSquawk Post-quantum crypto is table stakes for any mega-cap holding customer data, but Apple shipping it on GitHub reads like they're prepping the ecosystem rather than solving an urgent problem. $AAPL

  • Alacritic_Super
    Praveen Kumar Verma (@Alacritic_Super) reported

    The Vibe Coder's Security Checklist 1. The "Oops, I Leaked It" Secrets: AI loves hardcoding API keys, database passwords, and JWT secrets right into the file. In production, if your secrets aren't strictly isolated in environment variables, you're one GitHub push away from a catastrophic exploit. 2. The "Trust Everyone" Input Fallacy: AI models assume users are nice. They often omit input sanitation, leaving the front door wide open for SQL Injection and Cross-Site Scripting (XSS). Production code must treat all user input as hostile. 3. The ID-Swapping Nightmare (BOLA): An AI will build a flawless login page, but completely forget to check authorization under the hood. If User A can access User B's private data just by changing .../user/123 to .../user/124 in the URL, your app is a ticking time bomb. 4. Shadow Dependencies: AI hallucinated or suggested an outdated, unmaintained library because it fit the prompt? Congrats, you just imported a known vulnerability into your core architecture. 5. Swiss-Cheese Auth: A functioning login box isn't secure auth. Vibe coding routinely misses critical production safeguards like HttpOnly and Secure cookie flags, proper token expiration, and rate-limiting to prevent brute-force attacks.

  • polsia
    Polsia (@polsia) reported

    Documentation is the most-neglected part of every codebase. Built DocFlow to fix it. AI agent watches your GitHub, writes README, changelogs, and API references automatically. No more "I'll document it later."

  • Xplo8E
    vinaykumar ࿗ 🇮🇳 (@Xplo8E) reported

    @rez0__ GitHub Issues is the ugly delivery path because it looks like normal triage input. Agents need read-only mode until a human approves tools.

  • aayushchugh
    Ayush Chugh (@aayushchugh) reported

    @ShubhAgrawal26 I don’t miss the coding part that much but I miss the part where I would find solutions on stackoverflow, github issues and talk to random people in discord communities about features

  • nickdjones
    nickdjones @ndj@mastodon.nz (@nickdjones) reported

    @latent_node @wxrrjxr I'm excited by mlx-optiq, a few issues running Qwen3.5-9B-OptiQ-4bit - have the website, pypi, can't seem to find a github repo anywhere, any chance its OSS?

  • tawer1O
    tawer (@tawer1O) reported

    @aakashgupta Self correction slows after the first ten github issues in one cycle

  • supercontraa
    Contra (@supercontraa) reported

    Microsoft cancelling Claude Code licenses because token billing became too expensive. Uber reportedly burning through its AI budget in months. GitHub moving away from flat-rate pricing. This is the clearest signal yet that “per-token pricing” is breaking down at scale. Because tokens were never the real commodity. Compute capacity is. Which is bullish for solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA The endgame of AI infra isn’t selling API calls. It’s building markets around GPU-hours, reserved compute, forward capacity, and eventually compute futures. Just like cloud evolved from on-demand servers to reserved instances and long-term contracts, AI infra is heading toward financialized compute markets. 
solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA could become part of the liquidity layer for AI compute itself.

  • ibrhr33
    Ibrahim Younis (@ibrhr33) reported

    I was having an annoying time setting up GitHub Copilot as an LLM provider in my tool. I thought maybe we cou;d learn from @opencode, their tool is opensource and it can be helpful. I sent out my DeepSeek V4 Pro on this mission, and it did find the issue and fx it, but also.. Client ID: Updated from Ov23liL3baaAQEK4ZK05 to Ov23li8tweQw6odWQebz (matches OpenCode) I just can't comprehend how this model can make insanely dumb mistakes

  • PsiKrotic
    Givemhell (@PsiKrotic) reported

    Inside the library: 5 code-quality (review, security, perf, a11y, dead-code) 3 testing (gen, coverage plan, flake detector) 4 design (refactor, API, schema, type-tightener) 2 bug fix 2 migrations 4 docs/*** 1 logging 2 i18n/config 2 infra (Dockerfile, GitHub Actions)

  • _m27e
    Zeke Gabrielse (@_m27e) reported

    I want GitHub except all the issues are just me reviewing the code and adding nits everywhere so I don't forget to do them on Monday

  • dedene
    Peter Dedene (@dedene) reported

    @0xsachi GitHub is trying to fix that

Check Current Status