Google Worked at Beijing Airport—Then Hotel Wi-Fi Cut Me Off

Google Maps was still showing the blue route to my hotel when the airport taxi entered Beijing. Gmail had downloaded the booking confirmation, Google Translate had handled the driver’s first question, and my international eSIM appeared to have solved the whole China-internet problem before the trip had properly begun. Forty minutes later, I joined the hotel Wi-Fi to save mobile data and every Google app stopped at once. I blamed the Wi-Fi login page, disconnected, rejoined and restarted the phone. Nothing changed.

The timing turned a minor inconvenience into an immediate problem.

My train to Xi’an left early the next morning. The ticket details were in Gmail, the hotel address I needed to send to a guide was saved in Google Maps, and a client had left comments in a Google Doc that I had promised to answer before sleeping.

The eSIM could still reach those services when I turned Wi-Fi off.

My laptop could not use it without tethering, and the phone’s data allowance was already dropping faster than expected.

The question was no longer simply, “How do I open Google in China?”

It was: How do I keep Google working when I move from roaming data to hotel Wi-Fi—and from my phone to my laptop?

The airport connection had given me false confidence

China’s expanded visa-free policies have brought a sharp rise in foreign arrivals. In 2025, 30.08 million foreign visitors entered under visa-free arrangements, up 49.5 percent from the previous year. (National Bureau of Statistics of China) Many now arrive with international eSIMs and assume the hardest part of getting online has already been handled.

That assumption is understandable. Roaming data can behave very differently from a local connection.

My eSIM traffic was routed outside mainland China. Google Search, Gmail and Maps opened normally on the phone. The moment I joined the hotel Wi-Fi, the phone began using a mainland network path instead.

The Google apps did not all fail in the same obvious way.

Maps showed a cached area but would not search for the railway station. Gmail displayed messages it had already downloaded but would not refresh. Drive showed the document title and left the page beneath it blank.

At first, that looked like bad hotel Wi-Fi. Then I switched Wi-Fi off and watched all three recover over the eSIM.

That simple test changed the diagnosis.

The hotel internet worked. Google did not work through it.

Google is not one website

“Google is blocked in China” sounds simple until the missing service is carrying something you need immediately.

Google was not just a search box that evening.

It was Gmail holding my ticket confirmation. It was Maps holding the places I had saved before the trip. It was Drive containing work that needed to sync. It was Calendar carrying the next morning’s schedule.

Research into China’s filtering systems has confirmed the same inside-versus-outside split I was seeing: requests originating inside mainland China can be blocked even when the same services remain reachable through an overseas route. (GFW Report)

The eSIM had therefore solved only one part of the problem. It gave my phone a route around the local network while I was using mobile data.

It did not give the laptop access, preserve my data allowance or help once the phone joined hotel Wi-Fi.

That was where the VPN was supposed to take over.

The large VPN connected without solving anything

I had installed a well-known provider before departure because every sensible China travel checklist says to prepare a VPN in advance.

The choice seemed safe. The company had a long public history, many reviews and a large server network.

I opened it on the laptop, selected a nearby Asian location and waited.

The status changed to “Connected.”

Google Docs continued showing a white page.

I tried Japan, Singapore and the United States. Gmail occasionally reached the sign-in screen, then failed before completing authentication. Maps never finished loading.

The app itself looked healthy, which made the failure more convincing. There was no block notice and no red warning. It kept telling me the tunnel existed while the services behind it remained unusable.

I spent several minutes treating server countries as though one flag might contain the missing answer.

It did not.

China’s filtering systems can recognise VPN traffic by the way a connection behaves, not only by the address it contacts. (GFW Report and USENIX Security) Changing servers is therefore not always enough when each new route still presents a familiar VPN pattern.

I could not see the hotel provider’s internal filtering rules. I could see the result: the provider said “connected,” while Google remained out of reach.

By then, the server map had become another screen between me and the document.

The phone hotspot worked—but at the wrong cost

I returned to the eSIM because it was the one route that had not failed.

On the phone, I opened Gmail, copied the train details into Notes and took screenshots of the station name. Then I enabled the hotspot and connected the laptop.

Google Docs opened.

For about two minutes, that felt like the answer.

Then the document began loading images and comments. The laptop started background downloads. My remaining data dropped far enough that I switched the hotspot off before it consumed the allowance I needed for navigation during the rest of the trip.

That exposed the limit of the eSIM more clearly than any feature comparison could have.

It was excellent for getting my phone online after landing. It was a poor substitute for unrestricted hotel Wi-Fi across a phone and laptop.

Other travelers have described the same abrupt switch: overseas apps work over roaming data, then stop when the phone joins mainland hotel Wi-Fi. (Reddit) My screen had already proved the important part.

Saving mobile data meant finding a VPN that could make the hotel connection useful.

The backup asked about the problem, not the country

I had installed OnlydogVPN^↗ before the trip but left it unopened because the established provider felt like the safer first choice.

By then, I was no longer looking for another impressive server map. I wanted the hotel connection to carry Google traffic without turning the rest of the evening into protocol testing.

The smaller app began with situations rather than countries. I chose the preset intended for a restrictive network and tapped connect.

There was a pause long enough to make me expect another dead end.

Then Gmail refreshed.

Three new messages appeared, including one from the railway booking service. Google Docs loaded the client’s comments. I answered the first one, waited for the save indicator to change, closed the tab and reopened it.

The edit was still there.

I searched Google Maps for Beijing West Railway Station. The result appeared instead of the endless spinner I had been watching on hotel Wi-Fi.

The problems cleared in the order that mattered: the ticket details became available, the work document synced, and the route for the next morning loaded without consuming the rest of my eSIM.

Only after that did the technical difference matter. The service uses an HTTP/3-based connection with additional obfuscation, helping its traffic resemble ordinary modern web activity instead of a familiar VPN pattern.

That explanation needed one sentence.

The stronger evidence was on the screen: Google worked.

The laptop was only half the trip

I was ready to stop there when I noticed that my phone had quietly rejoined the hotel Wi-Fi.

Maps froze again.

Leaving the phone on mobile data would have restored the same divided setup: VPN on the laptop, eSIM on the phone and a limited data plan carrying navigation for the rest of the week.

The service offered a verification code for another device. I entered it on the phone without creating another conventional email-and-password account.

Maps refreshed over hotel Wi-Fi.

So did Gmail.

That was not the reason the first connection had succeeded. It simply solved the next problem without sending me through another login flow.

The following morning, the phone moved from the hotel Wi-Fi to mobile data while I walked toward the station. The connection recovered without making me repeat the setup.

That smaller result gave me a reason to keep the app installed. The first success opened Google on the laptop. The second removed the need to manage a separate network plan for each device.

Access is not the same as preparation

Restoring Google did not make it the only tool I needed in China.

Local map services can have better domestic place information. Offline copies of hotel addresses, ticket details and booking confirmations still matter. No connection method removes the value of preparing essential information before departure.

But those were separate decisions.

I was not trying to replace every Chinese travel app with Google. I needed access to information already stored inside my Google account.

That distinction changes what a traveler should prepare.

Someone using only a phone may be comfortable relying mainly on an international eSIM.

Someone carrying a laptop, conserving mobile data or expecting to use hotel and café Wi-Fi needs a connection that continues working after the phone leaves roaming data.

The useful test is not whether Google opens once at the airport.

It is whether Gmail, Maps and Drive remain reachable after the network and device change.

What finally mattered

The eSIM did its job well. It gave my phone international data immediately after landing.

The major VPN had the stronger reputation and the larger list of locations.

Neither gave me dependable Google access across the hotel Wi-Fi, laptop and phone.

The smaller service did.

By the time I went to sleep, the Google Doc was updated, the train details were stored offline and the station route was open on both devices. I no longer had to choose between spending mobile data and losing access whenever I joined Wi-Fi.

That was the comparison I had misunderstood before the trip.

Opening Google on one connection was useful. Keeping it open when the phone, laptop and network changed was what made the rest of the trip manageable.