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
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:
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 |
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:
-
🖕 Arbiter of Based 🖕 (@GamehopperPlays) reportedThey are actively hiding my valid complaints on the toxicity of #fluxer on both github my issue has been deleted and on #Flathub they have hidden my request for removal. Makes ya wonder doesn't it? Oh and now I am not allowed to make any new posts on Flathub whatsoever.
-
M (@mmijj_m) reported@DanielLockyer "Why is github down"
-
OnchainVibe ❖,❖ (@OwnArnab) reportedTested @konnex_world as my connection layer for Web3 identity this week and it solves a real problem which is fragmented reputation. I linked my wallet and my GitHub and my X profile in under 2 minutes. Konnex created one verifiable profile that I can take across dapps without redoing KYC or rebuilding trust each time. Every credential is signed and stored with the user so apps read it instead of owning it. Queried my own profile via API and response time was 740ms with full attestations attached. For builders this means you stop asking users to connect 5 wallets and fill forms. For users it means your onchain and offchain rep finally lives in one place that you control. Portable identity only works if it is easy and Konnex made it feel that way.
-
Andy🟢 (@AndyWallsQ) reportedGithub down, they removed Cloud Opus 4.6 for 4.7 , they are charging x7 tokens vs X3 for this garbage
-
Davidd (@rex2630) reported@cl_minmodels @teamspeakdev It's not, it's only laziness to do a proper site where u can download ts6-beta server. Reporting issues there doesn't make too much sense too, since u can report them on the forum and it makes them only duplicate. Other than that there isnt anything interesting on github.
-
Fusion Fix (@fusionfix10) reported@MMaRsu An update was just released, try to redownload the fix and see if it works. If there's still a problem, open a GitHub issue with attached crash dump for further assist.
-
Plextora (@Purekustora) reported@NotZylice as far as i understand: github discussions page for ideas, github issues page for bugs, and if you REALLY dont want to use either of those platforms then the osu!dev discord
-
Nathan Shearer (@lifeonautosite) reported@cursor_ai Incredible. Now can we fix the GitHub changes loader timeout on opening a project. Reload window used to work fine, now its reboot Cursor!
-
polymorpheus (@polymorph3us) reported@windsurf login-in-browser appears to be broken. login w/ github -> redirected back to login page
-
Mert Deveci (@gm_mertd) reportedThe cloud dev environments using sandboxes were a mystery to me so I dug down and built my own flow on my own infra 1. Connect Github 2. Run `runtime switch` to checkout a branch 3. Work on it with any coding agent I want 4. Publish the port to test 5. Merge Easier than I thought except the UX I wanted needed some polish around it I stopped using worktrees altogether. People were right that cloud environments for parallel agent work is awesome. Except in most cases it is too difficult and cumbersome to use.
-
Ai or Die Now (@aiordienow) reportedGitHub Copilot just paused new signups and cut usage limits. Classic playbook. Here's why this keeps happening and what to do instead. 🧵 The pattern: 1. Launch with subsidized pricing to get devs hooked 2. Usage grows faster than revenue 3. Quietly raise limits, cut model access, pause signups 4. Existing users get a worse product than what they signed up for This isn't a GitHub problem. It's the subscription model problem. From the official blog post: "It's now common for a handful of requests to incur costs that exceed the plan price." Translation: we gave you a deal we couldn't afford. Now we're taking it back. Every SaaS subscription is a temporary subsidy. They buy your loyalty with below-cost pricing. Once you're dependent, they adjust the terms. You stay because switching is painful. This is not a bug. It's how the model works. The HN thread is full of devs right now saying: "I hit my limit and I'm looking at running Qwen locally." That was always the answer. You just needed a rug pull to make it obvious. The self-hosted alternative for AI coding: - Ollama (local model runner) - free - Qwen 3.6 or Llama 3.3 - free weights - OpenCode + local model = zero monthly cost Steeper setup curve. Zero dependency on GitHub's business decisions. Same story plays out in WordPress plugins every year. Akismet, Yoast, WPForms - they all started cheap. Now they're $100+/year each. The answer is the same: own your tools. One-time purchase. No subscription hostage situation. The lesson from Copilot applies everywhere.
-
Tom Clancy's Floomfie Soldier (@bonnie1020RBLX) reported@geysergod_ @Victummz Yeah it's been a while since I used Perforce and it was a bit **** to use, that's probably why my uni swapped to GitHub in my third year since it was easier to use, but when Brad Wardell mentioned large binary file sizes it made me wonder what the actual issue is.
-
Zeke Sikelianos (@zeke) reported@lucatac0 no not really. working on making the school agent encourage students to share feedback via github issues, and even try to fix the issues themselves. but that prompt tweak just shipped yesterday
-
TechInnovation (@TechInnovationz) reported$IonQ $NVDA NVIDIA just open-sourced an AI decoder that fixes quantum errors in under a microsecond. GitHub, Hugging Face, free. arXiv 2604.12841, posted yesterday. Up to 3.5x faster than the previous best. Remember when Jensen Huang said quantum was “15 to 30 years away” in January 2025? A year later, NVIDIA is shipping production code for the hardest classical problem in fault-tolerant quantum computing. The tone changed. Quietly. The work didn’t. Ballance, two days ago: “physics is a sunk cost, what matters is engineering.” This paper is the classical half of that thesis. The quantum company that wins isn’t the one with the prettiest physics demo it’s the one plugged into the fastest classical stack. IonQ is on NVQLink, the transmission layer this decoder rides on. $IONQ $NVDA #IonQ #QuantumComputing
-
BP (@everyonebpup) reported🚨do you know what's happening with GitHub CLI? it went out in v2.91.0 a few hours ago. every gh command you run now sends a ping to github: command name, flags, OS, version, a device_id, and a field called "agent" that last field is the whole point. claude code, copilot CLI, cursor, and codex are all driving gh usage now, and github had no way to measure it. from their own issue (12522, january): "we do not have client side telemetry, it's not possible to say this with certainty" opt-out is three commands, any one works: export GH_TELEMETRY=false export DO_NOT_TRACK=true gh config set telemetry disabled small weirdness: the config command prints "unknown key" but actually writes telemetry: disabled to ~/.config/gh/config.yml. it works, the warning is a bug