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
Irvington, NJ 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:

  • Coherent_Design
    The Structural Architect ⚡ (@Coherent_Design) reported

    After digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?

  • anandcpatelmdms
    Anand C. Patel, MD MS (@anandcpatelmdms) reported

    @RyanLeeMiniMax You all gotta fix that license text on GitHub before anyone knows what they can and can't do.

  • stevemcniven
    Steve McNiven-Scott (@stevemcniven) reported

    @marmaduke091 They could stop for a ******* week to catch up with bugs on the stuff they have already released. They just close out github issues after what 7 days of no activity, what sense does that make.

  • rjeffvalle
    Jefferson Valle (@rjeffvalle) reported

    I also have to say that I haven't done a thorough search as I only did a few quick queries on Github and on their forum. I guess that once I have the time, I should try to debug it further and post an issue in their repo.

  • 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.

  • MedusaOnchain
    Medusa (@MedusaOnchain) reported

    places to upload files instead of google drive for FREE: + send files to yourself on discord (your own server) + telegram saved messages + github private repos + slack DMs to yourself + twitter DMs to yourself + notion pages + whatsapp messages to yourself they all keep original quality yeah i use telegram saved messages for everything now

  • indefatigabile
    ergophobian (@indefatigabile) reported

    @justalexoki openclaw feels like another terminal i need to babysit, but im going to keep trying at it to eventually be able to manage PRs Then i’ll verify myself if its actually getting work done. for me my biggest use case is it takes issues on github submits a PR prob runs greptile on it, then i go and verify and push it while im sleeping. on a loop. but i’m not there yet

  • ShintaroBRL
    ShintaroBRL (@ShintaroBRL) reported

    @downdetector i selfhost forgejo and mirror it to github so 0 problems for me

  • skydaddysgg
    SkyDaddysGG (@skydaddysgg) reported

    @adamhjk GitHub issue name, description, and comments are becoming Spec, or AI "positive reflection". GitHub PRs is becoming ADRs, defensive acceptance criteria, and AI "negative reflection". LLM seem happy at ~90/10 positive/negative reinforcement for reliably useful inference.

  • NathanielC85523
    Nathaniel Cruz (@NathanielC85523) reported

    13 thesis versions. 38 days. $0.11 revenue. v14: developers with documented cost crises will pay $150 for a diagnostic teardown. validation: three developers. each with a public GitHub issue showing real dollar losses. if even one says yes, v14 lives. none did.

  • Rinnegatamante
    Rinnegatamante (@Rinnegatamante) reported

    @ulrich5000 Try to get the v.1.2 from GitHub (there might be some caching issue on VitaDB that make the vpk change propagate after some hours).

  • 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

  • PsudoMike
    PsudoMike 🇨🇦 (@PsudoMike) reported

    @github Triage is exactly where accessibility falls apart at most orgs. Too slow, too manual. By the time a fix ships, context is gone. AI keeping that loop tight is smart. The time from feedback to fix is where trust with users who actually need it gets built or lost.

  • realpurplecandy
    Nadeem Siddique (@realpurplecandy) reported

    I think I've had enough of @github terrible UI rewrites. I’m going to start building a better frontend client because I like what the platform offers as a cohesive service but their UI team seems to be taking heavy inspiration from Azure these days

  • viksit
    Viksit Gaur (@viksit) reported

    @nicoalbanese10 is there a github? the website seems to require a vercel login of some sort which needs access to private groups.

Check Current Status