Does GitHub Pages Work in China? ICP Hosting, Reachability & the Compliant In-Country Layer

GitHub is one of the best places in the world to build and ship a static site, and nothing here asks you to leave it. Your repository, your Actions build and your Git workflow stay exactly where they are. This article is about the one thing a public, mainland-China audience adds on top of that: a presence that is both licensed to operate inside China and actually reachable from inside it. That is a compliance-and-delivery question, and it is the half of “does GitHub Pages work in China” that no amount of build tuning answers — because it was never GitHub Pages’ job to answer it.

The short version is a partnership, not a replacement. GitHub remains your source of truth and build pipeline; 21YunBox sits in front of the site GitHub builds as an ICP-filed, in-country entry for mainland visitors. Below is what GitHub itself documents about where a Pages site lives, the ICP door an offshore static host structurally cannot hold, the reachability gap that makes a github.io site unreliable in the mainland, and the lawful way visitor data is handled at the border — in GitHub’s own words and China’s own law, so you can take it to counsel.

GitHub Pages in China at a glance

What GitHub gives you — and where the mainland boundary is

GitHub’s description of its own service is worth reading before anything else. In its words, “GitHub Pages is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on GitHub,” and “You can host your site on GitHub’s github.io domain or your own custom domain.” For shipping a static site to a global audience this is close to ideal, and it is exactly why your code belongs on GitHub.

What that same description makes plain is where the site actually lives. A github.io address — or a custom domain pointed at GitHub Pages — is served from GitHub’s own infrastructure, which sits offshore from mainland China. GitHub publishes no mainland-China region and no in-country hosting option for Pages, not as an oversight but because Pages is a global static host, built to serve the open internet from the outside in. Two separate things follow once the audience is the Chinese public, one about delivery and one about law, and they are the subject of the next two sections.

Will the site even load? The reachability half

The first problem is delivery, and it is the one most teams hit before they ever think about licensing. GitHub Pages hands visitors a github.io address, or a custom domain fronted by GitHub’s offshore hosts, and access to foreign-hosted domains from inside mainland China is governed by the country’s network controls. In practice the github.io domain and GitHub’s asset hosts are frequently blocked or throttled inside the mainland, so a site that loads perfectly everywhere else can arrive slowly — or not at all — for a visitor in Shanghai or Shenzhen.

We do not publish a first-party load measurement for github.io on this page, so we state this as the reachability reality rather than as a number. But it is the reason a GitHub Pages site can be effectively unreachable in China even though nothing is wrong with your code. This is a delivery gap, and it sits on top of a second, legal one.

The ICP door GitHub Pages can’t hold

Showing a public website to people in mainland China turns on a permission that has nothing to do with performance: an ICP filing (备案). Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, that filing attaches to a hosting resource physically inside the mainland and to a mainland legal entity — a site with neither cannot file. A github.io site has neither: it runs on GitHub’s offshore infrastructure, and there is nothing in-country for the filing to sit on.

This is an ownership-and-location fact, not a knock on GitHub. The filing needs a licensed host inside the mainland to attach to, and a global static host — by design — keeps everything outside it. GitHub Pages is doing exactly what it is built to do; it is simply not, and was never meant to be, an in-country China presence.

Serving mainland visitors, and their data, lawfully

There is one more thing to be deliberate about: visitor data. A mainland visitor’s real IP address is itself personal information under China’s Personal Information Protection Law. Serving a mainland audience from offshore and carrying each visitor’s real IP and request logs out of the country is a cross-border transfer of personal information that PIPL governs (Chapter III, Articles 38–43: notice, separate consent, and one permitted transfer mechanism — a CAC security assessment, the CAC standard contract, or certification; Article 40, with Cybersecurity Law Article 39 (formerly Article 37), adds an in-country storage duty for a critical information infrastructure operator or a large-volume handler).

A purely static site is lighter here than a data-heavy application, but the moment it serves the mainland public from offshore the question is live. The lawful design answers it by terminating mainland visitors at an in-country, ICP-filed entry and sending a single, fixed in-country IP to your origin, rather than forwarding each visitor’s real IP across the border. Your origin seeing one in-country address instead of every visitor’s own is the design working as intended, not a defect to engineer around. Whether a particular site must also store personal data inside the mainland depends on your role and data volumes, which is a question for counsel rather than a default.

Where 21YunBox fits — a compliant overlay, not a migration

You keep building and shipping on GitHub exactly as you do today — the same repository, the same Actions build, the same Git workflow. 21YunBox adds the two pieces a global static host structurally cannot: ICP-filed delivery from inside mainland China, and reliable in-country reachability, placed in front of the static site GitHub builds from your repo — no rebuild, no second codebase, and no leaving GitHub. Our China team maps which obligations apply to your entity and your data, handles the ICP filing, and stands up the in-country entry that serves your mainland audience while GitHub stays your source of truth.

Get a compliance assessment →

Related reading:

• What is the China ICP license, and how do you get one?
• Cross-border data transfers under PIPL