VPN for China: Why Every Specific Claim Is Stale on Arrival

Any article naming a service that works on a heavily restricted network is out of date, and often was before it was published. The condition it reports is not a property of the service; it is the state of an active contest between people building tunnels and people identifying them, measured at one moment, from one network, by one person. Publishing it widely is itself part of what ends it.

This page therefore contains no recommendations, no service names, and no methods. What it can offer is more useful for planning a trip: an accurate model of why the information is unreliable, and how to prepare so that you are not depending on it.

Why the information decays so fast

Three things work together here, and each on its own would be enough.

The contest is continuous and asymmetric. Identifying tunnelled traffic is ongoing operational work carried out at scale, and it improves. A published recommendation tells the reader and everyone else at once, which is precisely the wrong dynamic for advice whose value depends on not being widely known.

Conditions vary by place, network, and hour. Reports conflict because they are all true of different circumstances. What worked on one network in one city last month is not evidence about a different network next week, and neither observer is lying.

Nobody publishing has an incentive to say so. Pages in this genre are usually monetised by the recommendation. A page that reported honestly that it cannot know whether its advice still holds would be a much worse page commercially, which is why you rarely see one.

The result is a genre of confident, dated, contradictory writing, all of it presented as current. Treat any specific claim you encounter as a historical observation.

What restrictive network conditions actually look like

Independent of any particular country, restricted environments share recognisable characteristics, and understanding them is more durable than any service name.

Restriction happens at several layers at once. Name resolution can fail, connections can be dropped mid-handshake, specific destinations can be unreachable while the rest of the network works, and traffic that looks unusual can be interfered with rather than simply blocked. These produce different symptoms, which is why “the internet is broken” is rarely the right description. The diagnostic sequence in blocked by the network or the service applies here as it does anywhere.

Tunnels are themselves a category that can be treated specially. In an environment where ordinary traffic passes and tunnelled traffic does not, the problem is not your configuration and not your provider’s competence.

Intermittency is normal and misleading. Something that works in the morning and not in the evening, or on one network and not another, invites endless fiddling. The fiddling is usually wasted; the variable is not you.

Corporate connections behave differently from personal ones. Many businesses maintain their own arrangements for staff, which is one reason travellers’ accounts diverge so sharply. If you travel for work, your employer’s own provision is the first thing to ask about, and travelling with a work laptop covers the rest of that conversation.

Rules are a separate question, and not one to guess at

Whether and how VPN use is regulated is a matter of local law, and it differs by jurisdiction in ways that do not reduce to a table. This site does not state any country’s law as fact and does not give legal advice. The categories of regulation, and why they differ, are covered in why VPN rules differ by country.

For an actual trip, the sources that matter are your own government’s current travel guidance for the destination, the destination’s official information, and — if you are travelling for work — your employer’s policy, which may be stricter than the law and is the one you are accountable to. Consult those, close to your departure date, rather than any blog.

Plan so that the answer does not matter

Here is the shift that makes this genuinely manageable: stop treating a working tunnel as the plan, and treat it as a convenience that may not be there. Everything that follows is unaffected by which service you chose.

• Do not put anything essential behind it. If a tunnel is the only route to something you need, you have a single point of failure on an adversarial network.
• Sort out authentication before you go. Second-factor methods that depend on a message reaching you are the classic failure, and they fail for reasons unrelated to blocking. This is worth an hour of preparation, along the lines of why 2FA breaks when you travel.
• Take offline copies of what you will need. Documents, tickets, reservations, contacts, maps, and anything you would otherwise fetch from a service you might not reach.
• Know the local alternatives. Widely used regional services usually work fine and are frequently better suited to the place you are in. Being unable to reach a familiar service is inconvenient, not disabling.
• Set up and test everything at home. Installing software and creating accounts is much harder from inside a restricted network than before you arrive. The general version of this is the pre-departure connectivity checklist.
• Agree how people will reach you. Tell whoever needs to know which channel you expect to be usable and what the fallback is.

If you are choosing a provider anyway

Judge only what you can judge from where you are. Whether the client is stable, whether it works on your devices, whether the account can be created and paid for before you travel, whether support responds, and what happens commercially if the service turns out to be unusable for the duration of the trip. Prefer a commitment short enough that being wrong is cheap.

What you cannot judge from home is the thing you most want to know, and no page — including this one — can supply it.

Bottom line

Specific claims about restrictive networks are perishable, contested, and usually monetised, so the reasonable posture is to disbelieve all of them, including the encouraging ones. Read your government’s current travel guidance and your employer’s policy for the rules, prepare so that nothing essential depends on a tunnel existing, do all your setup and testing before departure, and keep any commitment short enough that being wrong costs you very little.