Is GitHub Blocked in China? What Developers Need to Know
Is GitHub blocked in China?
No, GitHub is not on China's official block list the way Google or Facebook are, so github.com generally loads without a VPN. That said, access is inconsistent: developers report random timeouts, slow clones, and pages that hang mid-load, especially during peak hours or after network policy changes. Whether GitHub works well for you on a given day depends on your ISP, your city, and what's happening with China's network filtering at that moment. Treat GitHub as reachable but unreliable, rather than either fully open or fully blocked.
Why does GitHub feel so slow even when it's not blocked?
GitHub's servers sit outside mainland China, so every request crosses the international gateway, a narrow, heavily monitored chokepoint shared by millions of users. Deep packet inspection can throttle or reset connections to sites it doesn't fully trust, and GitHub's mix of encrypted git traffic and large binary objects makes it an easy target for that kind of interference. Add normal international latency on top, and a repo clone that takes 10 seconds elsewhere can take minutes in China. The slowdown is usually intermittent, not constant, which is part of why it's so frustrating to debug.
Will git clone or git push time out in China?
Yes, this is one of the most common complaints from developers working in China: large clones, especially monorepos or repos with big binary assets, frequently stall partway through and time out. Pushes can fail the same way, particularly over HTTPS, and CI pipelines that pull from GitHub during a build can fail unpredictably. Some developers work around this with shallow clones or by retrying repeatedly, but that's a workaround, not a fix. A more stable network path reduces how often this happens, though it can't guarantee zero failures.
Does GitHub work the same on mobile as on desktop in China?
The GitHub mobile app and mobile browser face the same underlying network conditions as desktop, so you'll see similar slowdowns and occasional failed loads. Mobile carriers in China can behave slightly differently from home broadband or office networks, sometimes better, sometimes worse, so results vary by device and location. If you're checking a pull request or reviewing an issue on your phone, expect the same reachable but patchy pattern as your laptop. It's not a GitHub-specific mobile problem; it's the same cross-border bottleneck affecting every device on the network.
What about GitHub Pages, raw.githubusercontent.com, and package installs?
This is where things get messier: raw.githubusercontent.com, used by pip, npm, curl-based installers, and many setup scripts, has a history of being unreliable or blocked outright in China, even when github.com itself loads. GitHub Pages sites can be similarly hit-or-miss. That means a pip install from a GitHub URL, a go get, or a curl script pulling a raw file can fail even on a day when browsing github.com feels fine. If your workflow depends on those subdomains, that's often where the real pain shows up, more than the main site.
How do I fix 'failed to connect to github.com' or clone timeout errors?
Start with the basics: retry with a shallow clone, increase git's HTTP buffer size, or switch from HTTPS to SSH, since SSH sometimes routes differently and dodges the interference that hits HTTPS. If errors persist across retries and at different times of day, the problem is almost certainly the cross-border network path rather than your local git config. In that case, a China-optimized connection that routes dev traffic over a more stable path, rather than the congested public gateway, is what actually resolves the pattern instead of masking it. A stable connection for AI tools and coding in China covers the setup for GitHub, npm registries, and similar dev traffic specifically.
Can a VPN make GitHub reliable for daily development work?
A VPN with China-optimized CN2 lines and real-time line scoring can meaningfully cut down on random timeouts and dropped clones, because it avoids the most congested parts of the public gateway. Yoho VPN's Pro plan includes access to all 30+ locations with AI route selection that automatically picks the fastest healthy path, which matters more for developer traffic than a single fixed server would. It won't make GitHub load like it's hosted locally, and no VPN can promise that, since results still depend on your network and location day to day. Smart Split also keeps mainland apps like WeChat and Alipay running direct and unaffected while your dev traffic routes through the optimized path.
Should I set up my VPN before I arrive in China?
Yes, set it up before you land. Downloading and configuring a VPN app is much easier outside China's network restrictions, and you'll want it ready the moment you start pulling repos or joining a call on day one. Yoho VPN supports iOS 15+, Android 8+ including a direct APK if the app store is inaccessible, Windows 10/11, and macOS 12+, all available at yohovpn.com/download. Getting the app, sign-in, and a test clone done before your trip saves you from troubleshooting on unfamiliar hotel Wi-Fi.
What else should developers expect to be restricted in China?
GitHub is actually one of the milder cases; services like Google Search, Gmail, and Google-dependent dev tools face much harder blocking, which matters if your workflow leans on Google services for research or debugging. Docker Hub, some npm mirrors, and various CDNs have also had rocky histories with access from mainland China. For a broader picture of what's blocked and what's merely slow, this rundown of apps blocked in China is a useful reference before you plan your workflow around any single tool. Building in some redundancy, mirrors, cached dependencies, offline-capable tooling, alongside a stable VPN route reduces how much any single outage costs you.