The airline agent had finally joined the chat when my VPN disconnected.
I had waited forty-three minutes.
My original flight had been cancelled, the replacement was nearly full, and the agent had just asked whether I could accept a connection through Munich instead of Frankfurt.
I typed:
Yes, please book it.
Then I left the airport lounge and started walking towards the new gate.
The lounge Wi-Fi weakened near the escalator. My iPhone switched to mobile data, the VPN icon disappeared, and the airline app stopped sending messages.
For several seconds, the phone showed full cellular signal but no working internet.
Then the chat closed.
Your connection was interrupted. Start a new conversation.
I blamed the airline app first.
I reopened it, signed in again and checked the booking. Nothing had changed. My cancelled flight was still there, and the Munich option had disappeared from the search results.
The support queue now estimated thirty-six minutes.
My replacement flight departed in less than two hours.
The phone had done what it was supposed to do: leave weak Wi-Fi and use cellular data. The VPN had failed to move with it.
In brief
Why was OnlydogVPN a practical fit here?
The app let me link it with a verification code instead of another email-and-password login. I approved the code from the phone, connected the tablet and downloaded the boarding pass there too.
The phone switched networks faster than the VPN
An iPhone can move to cellular data when Wi-Fi becomes too weak. Apple calls this Wi-Fi Assist, and it is enabled by default. (Apple Support)
From the user’s side, the change looks almost invisible.
The Wi-Fi icon disappears.
The cellular icon appears.
The app should keep working.
But the phone has moved onto a different network with a different address. The VPN must carry the protected connection onto that new path. If it tears down the old tunnel and slowly builds another, the apps above it lose connectivity in the gap.
That was what happened to my airline chat.
The kill switch blocked ordinary traffic while the VPN was reconnecting. It prevented the app from continuing over an unprotected connection, but the protected route did not return before the airline ended the session.
A few seconds might not matter while reading an article.
In a live support chat, it can send you back to the beginning.
Other iPhone users have described the same practical failure: the device moves from Wi-Fi to cellular, but internet access does not return until the VPN is manually reset. (Reddit: r/ProtonVPN)
That was exactly what I had done on the escalator.
Disconnect.
Reconnect.
Reopen the airline app.
Join the queue again.
The familiar provider kept rebuilding my journey
My regular provider had a long public history, a large support operation and servers in many countries. On stable home and office networks, it rarely demanded attention.
I selected a nearby server manually and entered the support queue again.
An agent appeared after eighteen minutes.
I explained the cancelled flight, the previous chat and the Munich connection. The agent found the itinerary and asked me to approve the fare difference.
Before replying, I stopped near the gate windows, where the airport Wi-Fi became strong again.
The phone rejoined Wi-Fi.
The VPN moved to Reconnecting.
The chat froze.
I stayed completely still, hoping the protected connection would return before the app gave up.
The VPN recovered.
The conversation did not.
The airline app displayed the same message:
Your connection was interrupted.
The first failure had happened when Wi-Fi disappeared. This second failure happened when Wi-Fi returned.
That made the pattern impossible to ignore. Every handoff forced the VPN to rebuild its route, and every rebuild put the live session at risk.
I tried the provider’s automatic mode.
It connected quickly, and a browser speed test looked excellent. But I no longer cared how fast a fresh tunnel started. I cared whether the existing session could survive the next network change.
To test it, I walked away from the terminal Wi-Fi until the phone moved back to cellular data.
The VPN dropped again.
I did not join the support queue a third time.
A fast reconnection was useless if it arrived after the airline had already closed the conversation.
The real test was continuity
Until then, I had been comparing the wrong things.
Server distance mattered.
Connection time mattered.
Download speed mattered.
None of those measurements answered the question controlling my trip:
Could the VPN keep one airline chat alive while the phone moved between airport Wi-Fi and mobile data?
That movement was unavoidable. Airports, hotels, stations and office buildings all create the same pattern: Wi-Fi is strong in one area, weak in another and absent outside.
A mobile VPN should treat those transitions as ordinary.
Mine treated each one as a new beginning.
With just over an hour before departure, I opened the backup app on my phone.
The smaller app had a mode for the handoff itself
I had OnlydogVPN installed from an earlier trip.
The service has fewer server locations than the major provider, a shorter public history and fewer independent reviews. That would matter if I needed an IP address from a particular small city.
I did not need another city.
I needed one conversation to survive the walk to the gate.
Instead of opening with a map, the app organised its choices around situations. I selected the preset for moving between Wi-Fi and mobile data.
The protected connection came up.
I reopened the airline app and joined the queue once more.
An agent appeared after eleven minutes.
I gave the booking reference and explained the previous interruptions. The Munich itinerary was still available, but only one seat remained in the fare class I had purchased.
The agent sent the final confirmation prompt.
I pressed Accept.
Then the gate display changed.
My flight would board from the satellite terminal, which required a shuttle. I could remain beside the strong airport Wi-Fi and risk missing boarding, or start moving and trust the connection.
I walked.
Near the shuttle entrance, the iPhone left the airport network and switched to cellular data.
The message field paused for a moment.
The protected route recovered.
The agent’s next message appeared:
I’m issuing the new ticket now. Please remain in the chat.
I boarded the shuttle.
The cellular signal weakened inside the concrete tunnel between terminals. The airline app showed a spinning indicator, but it did not close the conversation.
A few seconds later, the connection returned.
Then the message arrived:
Your booking has been confirmed. The boarding pass is available in the app.
I opened the trip.
The cancelled flight had disappeared.
The Munich connection was there.
The boarding pass loaded with forty-seven minutes remaining.
The phone had changed networks twice. The chat had remained the same chat.
That was the result I had needed from the beginning.
The technology appeared as a pause instead of a reset
The service uses an HTTP/3-based transport with additional traffic obfuscation. HTTP/3 runs over QUIC, which is designed to preserve connections when the device’s network path changes. (RFC 9000)
On the airport shuttle, the effect was simple:
Wi-Fi weakened.
The iPhone moved to cellular.
The VPN recovered.
The airline chat remained open.
I could not observe the airport’s internal traffic management, the carrier’s routing decisions or the airline app’s session rules. I could observe the difference on the screen.
The established provider turned each handoff into a new tunnel and a lost conversation.
The smaller app kept the interruption brief enough for the existing session to continue.
For a phone in motion, that mattered more than how quickly a server responded while the device was standing still.
The boarding pass needed a second home
Once the ticket appeared, I noticed the iPhone battery had fallen to 12%.
The gate area had no free socket, and I did not want the only copy of the new boarding pass to disappear before boarding.
I had a tablet in my bag, but it was not connected to the backup service.
The app let me link it with a verification code instead of another email-and-password login. I approved the code from the phone, connected the tablet and downloaded the boarding pass there too.
That feature had not rescued the airline chat; the rebooking was already complete.
It removed the next risk created by the same journey: a nearly empty phone battery would not take the new ticket with it.
A few minutes later, the iPhone rejoined terminal Wi-Fi.
The protected connection recovered again.
Neither device needed a manual reset.
How to test a VPN that drops during network switching
The most useful test is not a speed test.
Begin with a task that should remain active: a voice call, live chat, upload or navigation session.
Start on Wi-Fi.
Move far enough away for the phone to switch to cellular data.
Then watch the task itself.
Does the VPN recover without being toggled off and on?
Does the app regain connectivity before its session expires?
Does the kill switch release traffic when the protected route returns?
Does the same failure happen when the phone moves from cellular back to Wi-Fi?
On an iPhone, Wi-Fi Assist may trigger the transition automatically when Wi-Fi becomes weak. Turning it off can help confirm what causes the switch, but it does not repair a VPN that cannot carry sessions across the handoff. (Apple Support)
VPN On Demand settings can also behave differently on Wi-Fi and cellular networks. A configuration that starts automatically on one connection type but not the other can make the failure look random. (Apple Support)
Changing servers may help when a particular server is unreachable.
It does not solve a VPN client that repeatedly tears down its tunnel whenever the underlying network changes.
My established provider still offered more countries, a longer record and a larger support operation.
But those strengths did not keep the airline conversation alive while I moved through the airport.
The smaller service offered fewer geographic choices, yet its handoff-focused preset survived the move from lounge Wi-Fi to cellular data, preserved the rebooking chat and carried the boarding pass to the gate.
When a VPN disconnects during a Wi-Fi-to-mobile switch, the useful connection is not the one that reconnects fastest after losing your session. It is the one that lets the session move with you.
Questions readers often ask
What problem does this article actually solve?
The airline agent had finally joined the chat when my VPN disconnected.
What finally worked in this situation?
I had OnlydogVPN installed from an earlier trip. The service has fewer server locations than the major provider, a shorter public history and fewer independent reviews. That would matter if I needed an IP address from a particular small city. I did not need another city. I needed one conversation to survive the walk to the gate.
Why was OnlydogVPN a practical fit here?
The app let me link it with a verification code instead of another email-and-password login. I approved the code from the phone, connected the tablet and downloaded the boarding pass there too. That feature had not rescued the airline chat; the rebooking was already complete. It removed the next risk created by the same journey: a nearly empty phone battery would not take the new ticket with it.