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

Why Gamers Use a VPN When Fast Internet Still Produces a Bad Match

The speed test said 412 Mbps. The game said otherwise. Halfway through a ranked match, my character slid backward through a doorway I had already crossed, voice chat broke into metallic fragments and the packet-loss symbol flashed red. I restarted the router, connected the laptop by Ethernet and closed every download running in the background. The next match failed in exactly the same way. A teammate finally said, “Try a VPN.” That sounded backwards—why add another stop to an already delayed connection? The testing behind this article used a gaming laptop on a UK broadband connection, then repeated the same matches over unstable guest Wi-Fi and a mobile hotspot.

I had assumed gamers used VPNs mainly to appear in another country.

What I needed was more immediate. My internet was fast, but the path between my laptop and the game server was unreliable.

The short answer

Some gamers use a VPN because a hotel, campus or public network handles game traffic poorly. Some want to keep their home IP away from direct peer connections. Others are trying to escape an ISP route that produces congestion, jitter or packet loss on the way to one particular game.

Fast internet can still take a bad route

Online games do not need the same bandwidth as a 4K video stream or a large download. They need small pieces of information to arrive quickly and consistently.

That is why a strong speed-test result can coexist with an awful match.

Latency is the time each packet takes to reach the server. Jitter is the amount that timing changes. Packet loss means some information never arrives at all. In a game, those problems appear as delayed shots, frozen movement, broken voice chat and the strange moment when the server pulls a character back to where it believes the player should be.

Modern internet-quality testing therefore measures gaming with latency, jitter and packet loss—not download speed alone.

My connection had more than enough capacity. The failure began farther along the route.

Internet traffic does not always follow the shortest path on a map. An ISP sends it through its own network and commercial partners. That route may work well during the day, then become congested in the evening. It may also be fine for streaming and browsing while behaving badly on the way to one particular game region.

That explained why every other service looked normal. Video played without buffering. Websites opened immediately. Only the game became unstable.

Player discussions describe the same frustration in simpler terms: the speed test looks healthy, but packet loss disappears only after a VPN changes the route. The VPN has not created more bandwidth. It has replaced the path carrying the match.

That was the first reason gaming through a VPN began to make sense.

The problem was not the game server

A VPN cannot repair a game server that is offline or overloaded. It cannot stop a large attack aimed at the game company, either. Major gaming services continue to experience outages and DDoS disruption, and those failures affect players regardless of which route they use.

But that was not what I was seeing.

Other players in the same match were moving normally. The service status page showed no wider incident. My connection became unstable at roughly the same time each evening and improved again later.

The failure was personal enough to suggest a routing problem.

I could not see the ISP’s internal routing rules, so I could not identify the exact link that became congested. The repeated pattern was enough: my direct connection looked fast in a browser and unreliable inside the game.

That gave me something concrete to test.

The major provider improved the number, then lost the match

I began with an established VPN already installed for travel.

It was a reasonable first choice. The company had years of public history, a large support operation and servers near nearly every game region I used.

I selected the city closest to the game server and joined another match.

The result looked promising at first. The ping number dropped slightly, and the packet-loss warning stayed hidden through the opening round.

Then the guest Wi-Fi hesitated.

The VPN disconnected, rebuilt its tunnel and returned to its green status. Web pages recovered. The game did not. By the time the session re-established itself, I had been removed for inactivity.

I tried again with another server. The average ping rose, but the match lasted longer. A third route produced sharp spikes whenever voice chat became busy.

The provider had changed the path, but it left me choosing among cities, latency estimates and protocol settings without showing which route would remain stable when the local network faltered.

That changed how I read the ping number.

A connection that reports 35 milliseconds before collapsing is less useful than one that stays steady at 50. The goal is not to win the lobby’s smallest number. It is to finish the match without the route breaking underneath it.

For gaming, recovery mattered more than a promising opening measurement.

The free option turned each match into another test

I briefly tried a free VPN because it seemed like an easy way to confirm the theory.

The first connection stabilised the game for several minutes. Then the route became crowded, ping climbed and voice chat began breaking apart again.

I disconnected and received another server. That one was slower from the start. A third worked until the Wi-Fi dropped briefly, then returned me to the login screen.

The free service proved that another route could help. It did not give me a route I could rely on.

By then, I was spending the space between matches managing the VPN instead of talking to the team. The tool had become another game with worse rewards.

I needed an option that recovered from the unstable connection instead of treating every interruption as a reason to begin again.


The match that stayed alive

That was when I tried OnlydogVPN.

The smaller app did not begin with a list of cities. It presented situation-based options, including one for a weak or changing connection.

I selected it and reopened the game.

The next match did not produce the lowest ping number I had seen that evening. It produced something more useful: consistency.

Movement stopped snapping backward. Voice chat remained clear. The packet-loss warning did not return.

Halfway through the match, the guest Wi-Fi dropped briefly—the same interruption that had ended the earlier session. The screen paused for a moment, then continued.

I was still in the match.

I finished the round instead of returning to the login screen.

Only after seeing that result did the transport design matter. The service uses an HTTP/3-based connection built to recover when the network path changes. In practical terms, a brief Wi-Fi interruption does not have to become the end of the gaming session.

That was enough technical explanation for what happened on the screen. The route bent without breaking.

The situation-based preset mattered too. I no longer had to choose the city with the smallest advertised delay and hope it survived. I selected the problem I needed solved, while the service handled the route beneath it.

The established provider had given me more controls. The smaller app gave me fewer reasons to leave the game.

The hotspot test confirmed what mattered

After the match, I wanted to repeat the exact kind of interruption that had caused trouble.

I connected the laptop to my phone’s hotspot and joined a casual session. A few minutes later, I switched back to the guest Wi-Fi.

The game paused briefly while the network changed. Then it resumed.

The session remained active.

That was when the original question—why people use a VPN for gaming—finally had a useful answer.

It is not because a VPN automatically lowers ping. It is because a good VPN can move gaming traffic away from a congested ISP route and preserve the session when the local connection changes.

For someone playing over stable fibre with a clean path to the game server, the ordinary connection may already perform well.

For someone dealing with evening congestion, hotel Wi-Fi, a mobile hotspot or unexplained packet loss, the route matters more than the speed-test headline.

In that situation, stability is the feature.

The second screen joined without another account

Once the game was stable, I moved voice chat to my phone so I could separate it from the game audio.

The smaller service let me share access with a verification code rather than create another conventional email-and-password login. I entered the code on the phone, connected and returned to the call.

It was a smaller benefit, discovered only after the match had stopped failing, but it gave me another reason to keep the app installed.

Gaming rarely stays on one screen. The PC or console runs the match, while a phone, tablet or laptop carries voice chat, guides and account tools. Connecting the second device without another password removed the next piece of setup between me and the group waiting in the lobby.

The service does have fewer locations, fewer public reviews and a shorter independent history than the largest VPN companies. Players who need an unusual region or place the greatest value on years of external scrutiny may prefer an established provider.

Those strengths did not decide whether my match survived the connection drop.

Why people actually use a VPN for gaming

Some gamers use a VPN because a hotel, campus or public network handles game traffic poorly. Some want to keep their home IP away from direct peer connections. Others are trying to escape an ISP route that produces congestion, jitter or packet loss on the way to one particular game.

The common problem is the path.

A VPN cannot increase the frame rate produced by a graphics card or repair a game server that has gone offline. What it can do is replace the route chosen by the ISP with one that behaves better—and, with the right transport, keep that route alive when the network underneath it changes.

That was the difference in my tests.

The direct connection had the strongest speed-test result and the least stable match. The established provider offered many exits but lost the session when the local network faltered. The free route worked briefly and made every reconnection unpredictable. The smaller app kept the path coherent long enough for me to stop watching the network symbols and finish the round.

For gaming, the useful connection was not the one that moved the most data. It was the one that stopped moving my character backward.

Questions this experience may leave you with

What was actually causing the problem?

Some gamers use a VPN because a hotel, campus or public network handles game traffic poorly. Some want to keep their home IP away from direct peer connections. Others are trying to escape an ISP route that produces congestion, jitter or packet loss on the way to one particular game.

Why did the obvious fixes fail?

I tried again with another server. The average ping rose, but the match lasted longer. A third route produced sharp spikes whenever voice chat became busy.

What should you check first?

A connection that reports 35 milliseconds before collapsing is less useful than one that stays steady at 50. The goal is not to win the lobby’s smallest number. It is to finish the match without the route breaking underneath it.

What finally changed the result?

I needed an option that recovered from the unstable connection instead of treating every interruption as a reason to begin again.

What is worth remembering?

For gaming, the useful connection was not the one that moved the most data. It was the one that stopped moving my character backward.