Gaming latency and VPNs

Online games place very different demands on a network than video does: they need little bandwidth but are extremely sensitive to latency, jitter and packet loss. This article explains what those three metrics mean in a game, what a VPN can and cannot improve, and how the TP VPN Gaming route selects nodes.

What latency, jitter and packet loss mean in a game

Latency (ping) is the round-trip time between you and the game server. It sets the minimum time before the server acknowledges your action: at 100 ms, anything you do takes at least 100 ms to show on an opponent's screen. For shooters, fighting games and racing, 30 to 60 ms is usually considered good, and above 100 ms becomes noticeable.

Jitter is the variation of latency. A steady 80 ms is often better than a connection that swings between 40 and 160 ms: game engines interpolate and predict based on the expected delay, and erratic latency makes characters teleport or actions get rolled back.

Packet loss is packets disappearing in transit. Most games send state updates over UDP, where a lost packet is not retransmitted but superseded by the next one; a little loss shows up as brief stutter, sustained loss breaks hit registration and eventually disconnects you.

Of the three, jitter and loss often matter more than latency itself, which is why the Gaming route doubles the jitter penalty in its scoring.

What game traffic looks like

Small, frequent packets: tens to hundreds of state packets per second, each a few dozen bytes.
Mostly UDP: no handshake or retransmission, but no automatic error recovery either.
Very low bandwidth: usually under 100 MB per hour, so gaming almost never approaches the fair-use threshold.
Path quality beats bandwidth: a steady 10 Mbps line can feel better in a game than a 1 Gbps line with heavy jitter.

What a VPN can improve

The path from a home connection to an overseas game server is stitched together by several carriers, and congested international exits, roundabout routing and packet loss are common during the evening peak. A well-run VPN node helps in these ways:

Avoiding congested public paths. Your device takes a short path to the node, and the node forwards over a steadier line to the region of the game server.
Lower jitter and loss. Lines such as IEPL premium lines show markedly lower jitter and loss than the public internet.
A consistent path. The route inside the tunnel stays fixed instead of changing whenever a carrier reroutes.

What a VPN cannot improve: realistic expectations

It cannot shorten physical distance. Shanghai to Tokyo is about 2,000 km, which means at least 20 to 30 ms round trip in fibre; the US west coast is 100 ms or more. No node can go below that floor.
When the server is nearby, a VPN may make things worse. If the game server is in your own city, going through a node adds a hop. Test the latency both directly and through the node, and use whichever is lower.
It cannot fix your local network. Interference on 2.4 GHz Wi-Fi, an overloaded router or a phone throttling from heat all happen before the tunnel begins.
It cannot change the server's own processing delay. A game server at capacity is slow regardless of the network.

How the TP VPN Gaming route works

After choosing the Gaming category on the Nodes tab, nodes are filtered and ranked as follows:

A latency threshold. Only nodes whose latency meets the threshold enter the category; the rest are excluded outright.
A doubled jitter penalty. In the weighted score, latency variation is penalised twice as heavily, so steady nodes are preferred over momentarily fast ones.
UDP-priority forwarding. Nodes forward UDP traffic first, shortening queueing time and reducing the rollbacks and stutter caused by loss.
Asia-Pacific coverage. Nodes are located in Hong Kong, Taipei, Tokyo, Osaka, Seoul and Singapore, close to the region's game servers.

The Gaming category is available from the Standard plan. During the 3-day trial, Gaming is available when you selected Standard or a higher plan. The tunnel applies to all traffic on the device, so other apps travel through the same node and usually notice no difference.

Practical advice

Pick the node by the game server. Choose a city in the same region as the server: Tokyo or Osaka for Japanese servers, Singapore or Hong Kong for Asian servers.
Compare using the in-game latency display. Note latency and jitter for a direct connection, Smart pick and the Gaming route, and keep the steadiest.
Favourite the nodes you use. Favourites stay at the top of the list, ready to tap before a match.
Do not switch nodes mid-match. Switching causes a brief interruption; do it between games.
Prefer 5 GHz Wi-Fi or a wired connection. On a phone, avoid heavy play while charging so it does not throttle from heat.
Turn on Auto-connect on launch and set the default scenario to Gaming. The app then connects with that scenario as soon as it opens.

Frequently asked questions

Why did my latency not change after enabling the route? If the public path between you and the server is already good, the route's benefit shows mainly as stability during peak hours; the everyday latency figure may be similar.

Does it work for a console or PC sharing my phone's hotspot? The tunnel protects only the device running the app; traffic shared through a hotspot is outside it.

Why is a city missing from the Gaming category? The category lists only nodes that meet the latency threshold on your current network; a city whose nodes fall short is hidden. Switch to Smart pick to see every node.