Google Worked in Shanghai. In Zhengzhou, the Same VPN Stopped Helping

The Google Drive folder disappeared 26 minutes before I was due to present. Not the files—the entire folder view. Gmail showed yesterday’s messages, Calendar displayed the meeting, and the Meet link opened to a white screen that never finished loading. The same laptop and VPN had worked in Shanghai the night before, so I blamed the Zhengzhou hotel Wi-Fi. I disconnected, joined again and watched the VPN return to its reassuring green state. Drive remained blank.

The presentation was for a supplier meeting scheduled at 9 a.m. London time and 4 p.m. in Zhengzhou. The final deck contained two videos, a revised pricing table and comments my colleague had added after I boarded the train from Shanghai.

I had deliberately left it in Drive rather than downloading an offline copy. The VPN had been reliable in Shanghai. Gmail, Docs and Meet had all opened from the first hotel, so I assumed the difficult part of the trip was already solved.

That confidence lasted until I changed cities.

I restarted Chrome. I signed out of Google and immediately regretted it when the login page stalled too. Then I switched the laptop from hotel Wi-Fi to my local mobile hotspot.

The VPN connected again.

Google did not.

China had become easier to enter than my workday

Short-notice trips like mine have become much more common. China’s expanded visa-free policy allows ordinary passport holders from dozens of countries to enter for business, tourism and other eligible visits without arranging a visa in advance. Foreign arrivals and visa-free entries continued rising sharply in 2026.

That has created a particular kind of traveler: someone who can arrange a China visit quickly but arrives with a work system built almost entirely around Google.

My schedule was in Calendar. The client history was in Gmail. The presentation was in Drive. Meet was not merely a video-call app; it was the door to the meeting.

Those services are not normally reachable on a mainland connection. Current travel guidance still warns that Google, Gmail, YouTube, WhatsApp and other foreign platforms remain unavailable even on many international hotel networks.

I knew this before traveling. I had installed a major VPN at home and tested it after landing.

What I had not expected was that success in one Chinese city would tell me so little about the next.

The train journey changed more than my location

Zhengzhou is in Henan province. Researchers have documented a separate regional filtering system operating there alongside China’s national Great Firewall.

Their measurements found that Henan’s provincial system blocked millions of domains and could behave more aggressively and less consistently than the national layer.

That put the previous evening in a different light.

My VPN had worked in Shanghai. It did not follow that the same server and connection mode would pass through Henan’s network unchanged.

The train had moved me roughly a thousand kilometers. It had also placed my connection behind another layer of filtering.

The blank Drive page no longer looked like a bad hotel router. More importantly, repeatedly reconnecting to the same kind of route was unlikely to solve it.

The trusted provider gave me a long list of short failures

I had chosen the major VPN for sensible reasons. It had years of public history, a large support operation and servers across more countries than I would ever need. I had also signed in before traveling, so there was no blocked registration page between me and the connection.

The app recommended a nearby server.

I connected.

Google’s login page appeared, accepted my email address and froze before the password field.

I selected Japan. Gmail opened, but Drive did not.

Singapore allowed the Drive interface to load without any files. A United States server reached the Meet waiting room, then disconnected during the camera check.

I changed the connection mode and repeated the sequence.

Each attempt failed at a different point, but none completed the task.

The provider’s scale was real. On an ordinary network, I would have valued the ability to compare countries, cities and specialized modes. In that hotel room, the server list became a troubleshooting menu.

Japan or Singapore? Automatic mode or another protocol? Lowest load or shortest distance?

Every choice required me to reconnect, reopen Drive and wait long enough to discover whether the route was working or merely beginning to work.

With 17 minutes left, I had tested five routes and downloaded nothing.

The app was giving me infrastructure.

I needed a presentation.

“Connected” was only the first step

I could not see the internal filtering rule interrupting each route. What I could see was consistent: the VPN established a connection, but Google stalled during login, file loading or Meet’s camera check.

Chinese filtering is not limited to a static list of blocked websites. Researchers have documented systems that inspect connection characteristics and classify encrypted traffic, including modern QUIC connections.

The practical meaning was simple.

A healthy VPN server abroad did not guarantee a usable path from the hotel room to that server. Nor did a green icon prove that Google traffic would survive the journey.

The provider had hundreds of possible exits. My problem was getting through the entrance.

Once I understood that, another country flag no longer felt like a new solution.

Roaming reopened Google—and started another countdown

I turned off the local hotspot and enabled my international roaming line.

Gmail refreshed.

The contrast was immediate. Roaming data can be routed through a subscriber’s home mobile network rather than entering the public internet directly from China. That is why Google may work through international roaming or some travel eSIMs, then disappear when the same device joins hotel Wi-Fi.

I connected the laptop to the roaming hotspot and opened Drive. The folder appeared.

For a minute, I thought the emergency was over.

Then the two embedded videos began downloading.

My roaming plan had less than a gigabyte of high-speed data left. The presentation assets would consume most of it, and the Meet call would need more. The phone was also heating up while serving as the laptop’s only connection.

Roaming could retrieve a document or reset a password. It was not the route I wanted carrying an hour-long presentation.

I used it to make sure the backup VPN was still installed, then returned the laptop to the hotel network.

The smaller app started with the problem

I had installed OnlydogVPN^↗ before the trip but had not used it in Shanghai.

The reason was straightforward. It had fewer locations than the established provider, a shorter public history and fewer independent reviews. Before either service had been tested, the older and larger one looked like the conservative choice.

Now it had already consumed nine attempts across two networks.

The smaller app did not begin by asking me to choose Japan, Singapore or the United States. Its presets were organized around situations. I selected the option for a restrictive network.

Basic use did not require another email-and-password account, so it did not send me back to the Gmail inbox I was trying to reach.

I connected and reopened Drive.

The folder populated.

The pricing deck appeared first, followed by the two video assets. I opened the presentation, moved to the final slide and saw my colleague’s comments in the margin.

Then I clicked the Meet link.

The camera preview loaded. The microphone meter moved when I spoke. I entered the meeting with six minutes remaining.

The client joined early.

I shared the presentation, played the first video and watched it finish without falling back to a loading screen.

That was the moment the comparison ended for me.

The major provider had shown more server locations. The smaller app had completed the workflow those locations were supposed to support.

The explanation was shorter than the result

The service uses an HTTP/3-based transport with additional traffic obfuscation.

The protocol name was not what mattered. The useful difference was that the route was designed to avoid the familiar connection patterns restrictive networks can identify and interrupt.

I did not need a technical paper while the meeting clock was running.

I needed four observable results:

Gmail synchronized.

Drive downloaded the deck.

Meet completed its checks.

The video played.

The explanation mattered because it matched what had happened on the screen—not because it added another protocol to compare.

The route survived the hotel’s next decision

Halfway through the presentation, the hotel Wi-Fi demanded authentication again.

The shared screen froze on the manufacturing timeline. A browser window opened behind Meet and displayed the hotel portal, asking for my room number and surname.

Previously, changing networks had meant disconnecting the VPN and beginning another server search.

This time, I enabled the local mobile hotspot and moved the laptop onto it.

The meeting paused briefly. Then the shared screen resumed on the same slide.

The client asked whether the November milestone could move forward by two weeks. He had not seen me change connections.

That recovery was smaller than reaching Google in the first place, but it solved the next problem without starting the whole process again. A route that works only until the hotel refreshes its Wi-Fi session still leaves the traveler managing the VPN instead of the meeting.

By the end of the call, the situation-based preset made more sense than the country map.

I did not care which city the exit server claimed to occupy. I cared that the route remained usable when the network underneath it changed.

Google had not changed overnight

When I left Shanghai, I assumed I had solved Google access for the rest of the trip.

That was the wrong conclusion.

Google had not changed between the two cities. My account had not changed. The laptop and hotel chain were the same.

The network conditions had changed, and the VPN setup that crossed one of them did not cross the other.

The established provider still had the stronger public history and broader geographic network. Those advantages would matter to someone choosing by location coverage or years of independent scrutiny.

They did not recover my presentation in Zhengzhou.

What mattered that afternoon was a route adapted to the filtering where I actually was, with few enough setup steps to use before the meeting began.

China’s visa-free expansion had made the journey easier to arrange. It had not made a Google-based workday consistent from city to city.

My Google account traveled from Shanghai to Zhengzhou without difficulty. The connection capable of reaching it did not.