FIELD NOTES
A personal record of travel, networks and small failures
TRAVEL NOTE

The Local SIM Gave Me a Chinese Number—and Took Gmail Away

The revised presentation was already in my inbox when Gmail stopped refreshing. I was standing beside a charging station at Beijing South railway station, twenty-three minutes from boarding, trying to approve the final version before my client in London sent it to print. WeChat worked. Alipay worked. The railway app showed my platform. Only Gmail, Slack and Google Drive behaved as though the phone had no internet. I blamed the new China Unicom SIM, switched airplane mode on and off, then reset the mobile-data settings. The signal returned at full strength. My email did not.

My client sent a WeChat message because she knew I had landed in China.

“Can you approve page 18?”

I could read the question.

The file attached to the email remained unreachable.

That was the contradiction I had not prepared for. The local SIM had made the trip easier in almost every visible way, then cut me off from the services I needed for work.

The short answer

The smaller app gave me fewer decisions. Its restrictive-network preset connected through the local SIM, restored the blocked work services and then moved the same setup to the laptop with a code.

The local number solved a real travel problem

I was in Beijing under China’s expanded 240-hour visa-free transit program. Eligible travelers can enter through designated ports and remain for up to ten days before continuing to a third destination. (Gov)

Ten days was long enough to need more than emergency roaming.

My travel eSIM had worked after landing, but it came with a limited data allowance and no mainland Chinese phone number. That became inconvenient quickly.

The apartment host wanted a local callback number.

A restaurant queue required an SMS confirmation.

A courier delivering exhibition samples would not accept the foreign number in my profile.

So I visited an official carrier store with my passport and bought a local SIM. Foreign visitors can obtain service from China Mobile, China Telecom or China Unicom using accepted identity documents. (Gov)

The clerk activated the line in minutes.

The local number worked immediately.

So did the local apps.

I assumed the difficult part of the trip was over.

Instead, the new SIM had solved one half of the problem and exposed the other.

The SIM changed more than my phone number

Before switching, the travel eSIM had kept Gmail, WhatsApp and Google Maps reachable. After the local SIM became the data line, those services stopped responding.

The phone had not changed.

The apps had not changed.

The route to the internet had.

Travel eSIMs often send data through infrastructure outside mainland China. A local SIM uses the domestic carrier network, where international services may be filtered. (Reddit)

That was exactly my situation.

I had chosen the local SIM because I wanted the phone to work naturally inside China. Now I needed that same SIM to reach my work outside it.

Switching back to the travel eSIM would restore Gmail, but it would also sideline the number my host, courier and local bookings were already using.

The useful solution had to preserve both.

The established provider connected everywhere except where I stood

I had installed a major VPN before leaving home.

It was the obvious choice: years of public history, polished applications and a large network of servers across Asia.

At the station, I opened it and selected the automatic connection.

The status changed to Connecting.

Then back to Disconnected.

I tried Japan.

The tunnel appeared for three seconds before collapsing.

Singapore connected, but no traffic moved.

Hong Kong opened one Google result and then stalled.

The application recommended changing protocols.

I tried WireGuard.

Then OpenVPN.

Then automatic mode again.

Each attempt gave me a different icon and the same empty inbox.

The client sent another WeChat message.

“Train soon?”

“Twenty minutes.”

“Can you review it on the train?”

The train would not help if the VPN could not connect through the SIM.

At that point, the provider’s large network stopped looking like insurance. Every server sat behind the same failed first step.

I did not need more destinations.

I needed one tunnel that could open on the connection in my hand.

Station Wi-Fi changed the network, not the outcome

Beijing South had public Wi-Fi, so I connected to it.

The login page asked for a phone number.

For once, the local SIM solved the immediate problem. The verification message arrived, and the station network opened.

Gmail still did not.

I started the major VPN again.

Japan failed.

Singapore stayed connected long enough to load the Gmail logo, then returned to the sign-in screen.

The station Wi-Fi had changed the access network without changing the result.

It also introduced a shared connection I trusted less than the carrier data.

That made the situation clearer.

The local SIM was stable and personal but restricted.

The station Wi-Fi was shared and equally restricted.

The established VPN failed on both.

I had twelve minutes left.

The travel eSIM worked, but at the wrong cost

I switched mobile data back to the travel eSIM.

Gmail refreshed.

The presentation appeared.

For a moment, the problem seemed solved.

Then I opened the 86-megabyte attachment.

The download slowed almost immediately. My remaining allowance was smaller than I remembered, and the eSIM app warned that the plan was close to exhaustion.

I could approve the presentation from the preview, but the client also needed me to upload a corrected image from my phone.

That file would consume most of what remained.

The eSIM had restored access by avoiding the local route. It had not solved the trip I was actually taking.

I still needed the Chinese number.

I still needed data for maps, messages and bookings during the next four days.

Using the last of the travel plan on one work file would leave me buying another package from the train.

The fallback proved that my accounts were fine.

It also clarified the requirement.

I needed international access through the local SIM I had already paid for.

The smaller backup began with what had stopped working

I switched data back to China Unicom and closed the established provider.

Then I opened the smaller backup I had installed before the flight.

There was no map.

The first screen asked about the network situation.

I selected the preset for a restrictive mobile connection.

The app connected.

I returned to Gmail.

The inbox populated.

The presentation downloaded.

Slack filled with the messages that had been waiting since I left the apartment.

I opened page 18, checked the revised pricing table and replied:

“Approved. Use this version.”

The message sent.

Then I uploaded the corrected image to the shared Drive folder.

The progress circle moved without stopping.

My client reacted with a check mark.

The task that had followed me across two data plans, a public Wi-Fi login and several VPN servers was finished with nine minutes left before boarding.

I did not need to know which country the app had selected.

I needed page 18 to reach London.

It had.


The working connection explained enough

China’s filtering systems can interfere with foreign services and identify circumvention traffic from recognizable connection patterns. (Citizenlab) (Usenix)

The smaller app used an HTTP/3-based transport with additional obfuscation instead of presenting the carrier with another familiar VPN connection.

I could not observe China Unicom’s internal filtering rules or identify the exact signal that caused the established provider’s attempts to fail.

The visible result on the same phone was enough:

the local SIM reached Chinese services but not my work accounts;

the established provider could not maintain a useful tunnel;

the travel eSIM restored access but consumed a separate, limited plan;

the smaller app opened Gmail, Slack and Drive while the Chinese SIM remained active.

That was the first option that preserved both sides of the trip.

The local number continued receiving calls and verification messages.

The international services became usable again.

The laptop joined after the urgent work was done

At the gate, my client asked whether I could join a five-minute call after boarding.

The phone had already approved the file, but I wanted the presentation open on my laptop during the discussion.

I connected the laptop to the phone’s hotspot and opened the smaller app.

Instead of typing an email address and password in the middle of the station, I used the verification code shown on the phone.

The laptop joined the same setup.

Gmail opened.

The shared Drive folder appeared.

The presentation loaded before boarding began.

The code had not solved the main problem; the phone had already completed the approval. It removed the next inconvenience without making me rebuild the connection on another device.

When the gate agent scanned my passport, the laptop was already in my bag with the file cached.

I boarded without changing SIMs again.

The local SIM had never been the mistake

For the first hour, I treated the China Unicom card as the cause of the failure.

That was too simple.

The local SIM had done exactly what I bought it to do.

It gave me a mainland number.

It received local verification codes.

It kept the host, courier and transport apps connected.

The mistake was expecting it to behave like the international eSIM it replaced.

The two products solved different halves of the trip. The travel eSIM provided an external route but no local number. The Chinese SIM provided the number and domestic connectivity but placed the phone inside the local network environment.

A VPN for a local SIM therefore has a harder job than changing the country displayed by an IP checker.

It must connect through the carrier that creates the restriction.

Without that first connection, the size of the server map does not matter.

Fewer locations mattered less than one working path

The smaller service has fewer server locations, fewer independent reviews and a shorter public history than the established provider. That is its clearest limitation.

Before boarding the flight to China, I would have treated the larger provider’s scale as insurance.

At Beijing South, that scale became a sequence of failed choices.

Japan.

Singapore.

Hong Kong.

WireGuard.

OpenVPN.

Automatic mode.

None reached the file.

The smaller app gave me fewer decisions. Its restrictive-network preset connected through the local SIM, restored the blocked work services and then moved the same setup to the laptop with a code.

The established provider offered more places to go after the tunnel opened.

The smaller app solved the harder problem: opening the tunnel on the SIM I needed to keep using.

For a local SIM in China, the useful VPN was not the one with the largest map beyond the firewall.

It was the one that let the Chinese number stay local while the work could still leave the country.

Questions this experience may leave you with

What was actually causing the problem?

The smaller app gave me fewer decisions. Its restrictive-network preset connected through the local SIM, restored the blocked work services and then moved the same setup to the laptop with a code.

Why did the obvious fixes fail?

Switching back to the travel eSIM would restore Gmail, but it would also sideline the number my host, courier and local bookings were already using.

What should you check first?

Before switching, the travel eSIM had kept Gmail, WhatsApp and Google Maps reachable. After the local SIM became the data line, those services stopped responding.

What finally changed the result?

The two products solved different halves of the trip. The travel eSIM provided an external route but no local number. The Chinese SIM provided the number and domestic connectivity but placed the phone inside the local network environment.

What is worth remembering?

It was the one that let the Chinese number stay local while the work could still leave the country.