VPN Connected but No Internet? Test Recovery Before Changing Servers

The airline app gave me six minutes to accept a replacement flight.

I tapped Confirm. A white spinner turned twice, stopped and produced the message I had been seeing all morning:

No internet connection.

The VPN icon was still visible at the top of my iPhone. The app said Connected. Airport Wi-Fi showed three bars. Beside me, the departure board changed another gate number without waiting for my phone to catch up.

I blamed the terminal network first. Thousands of passengers were checking boarding passes, uploading videos and searching for delayed bags. Congested airport Wi-Fi seemed like the obvious explanation.

I turned Wi-Fi off and let my travel eSIM take over. The status bar changed to 5G.

The airline app still said I had no internet.

Next I enabled airplane mode, counted to ten and switched it off again. Messages arrived immediately, proving that the phone itself was online. The airline app remained frozen until I disabled the VPN.

Then the page loaded at once.

That narrowed the problem down, but it did not solve it. I did not want to send passport and payment information through whichever airport network happened to be strongest. I wanted the VPN to work, not merely disappear.

The Airport Network Was Not Standing Still

This kind of failure is easy to encounter during a busy travel period.

The 2026 World Cup brought millions of spectators into venues across Canada, Mexico and the United States. During the same summer surge, the US Transportation Security Administration expected almost 18.7 million passengers over the Fourth of July travel period alone. (TSA travel data) Travelers were constantly moving between stadium networks, hotel Wi-Fi, airport hotspots, roaming services and temporary eSIMs.

A phone can pass between those connections almost invisibly. The Wi-Fi symbol disappears, cellular data takes over and most apps continue working.

A VPN has to follow the change. It must recognize that the original network has disappeared, reach its server through the new route and restore the tunnel before the phone is left with a connection icon but no usable internet.

Apple’s networking documentation describes a temporary reconnection state when a VPN adjusts to a network change. (Apple developer documentation) That explained the contradiction on my screen: the phone had internet access, and the VPN still appeared active, but traffic was no longer moving through the tunnel.

With the airline timer still counting down, I treated it as a server problem.

That was the wrong comparison.

Why Changing Servers Only Helped Briefly

The VPN I normally used was an established service with a long public record, extensive support pages and a large server network. Trusting it was reasonable, so I opened the app and moved from its automatic location to a nearby server.

The connection returned. The airline page refreshed.

For a moment, I thought the problem was over.

Then I started walking toward the new gate. My phone picked up another airport access point, and the page stopped halfway through loading. The VPN continued to display a successful connection, but the confirmation button no longer responded.

I changed servers again.

It worked until the Wi-Fi weakened near a moving walkway and the phone switched back to cellular. Then the same failure returned.

The new server was not fixing the underlying problem. Selecting it simply forced the VPN to build another tunnel. Each manual reconnect worked until the network changed again.

Other travelers have described the same practical pattern: a VPN stops passing traffic during the move between Wi-Fi and mobile data, then begins working after a manual reconnect. (Public iPhone user discussion about VPN traffic stoppin) The useful point was not which provider they used. It was that an apparently connected tunnel could still require constant repair.

I could not inspect the airport network or either app’s internal routing decisions. What I could see was consistent: the established service worked while the connection stayed still and failed when the phone changed networks.

At home, a larger server list might have mattered. At the airport, it only gave me more places to reconnect manually.

The Backup I Tried Before the Offer Expired

I had installed OnlyDogs VPN before the trip. I had not made it my default because the service has a shorter public history, fewer locations and much less independent feedback than the provider I already trusted.

With three minutes left on the airline offer, those limitations remained real. They were simply not the problem in front of me.

The smaller app organized its connection options around situations rather than beginning with a country map. I selected the preset intended for a weak or changing network and connected.

The airline app refreshed.

I tapped the replacement flight, accepted the fare difference and reached the final confirmation screen. The payment completed. A new boarding pass appeared in my wallet before the offer expired.

I saved a screenshot out of habit.

Then I kept walking.

That was the more useful test. Near the end of the concourse, the phone moved from terminal Wi-Fi to cellular data. The status bar changed, but the airline app remained usable. When another airport access point became available near the gate, the connection continued without sending me back to the VPN app.

The immediate task was already complete: I had the replacement seat. The walk to the gate showed why this attempt felt different. Instead of making me rebuild the connection every time the phone found a new route, the app recovered while I moved.

Why the Connection Recovered

The service uses an HTTP/3-based transport with recovery designed for weak and changing networks.

HTTP/3 runs over QUIC, which can preserve a connection as a device moves between network paths. Rather than treating every change of Wi-Fi access point or switch to cellular data as a completely new session, the connection can continue through the route now available to the phone. (IETF specification)

That was enough technical explanation for what I had just observed.

The established app repeatedly left the tunnel attached to a connection I had already walked away from. The smaller app followed the phone onto the next one.

There was no dramatic benchmark result. The page simply kept working.

For someone trying to save a flight, that was the measurement that mattered.

“Connected” Is a Status, Not a Result

A VPN can show Connected while the internet remains unavailable for several reasons. An airport or hotel may require its login page to be completed before the VPN starts. A kill switch may block traffic after the tunnel fails. DNS settings may become stuck. A particular server may be temporarily unreachable.

But when the failure appears after leaving a building, walking through an airport or moving between Wi-Fi and cellular data, recovery is worth testing before cycling through server countries.

A manual disconnect and reconnect can reveal the pattern. When traffic immediately returns but disappears again at the next network change, the problem is unlikely to be a shortage of working server locations. The VPN is failing to maintain a usable path as the device moves.

The established provider remained the more proven company. It offered more locations, a larger support operation and far more public reviews. The smaller service is newer, and its App Store listing does not yet provide the same depth of long-term user evidence. (OnlyDogs App Store listing)

That limitation matters during a broad comparison.

It mattered less while the airline’s timer was running.

The established app was usable when the network stayed still, but repeatedly stranded the phone as the airport connection changed. The smaller app recovered, kept the airline page alive and allowed the booking to finish.

The replacement seat was not saved by the VPN with more servers. It was saved by the one that noticed the airport had moved underneath it.