Last Epoch Proxy: Traffic That Goes Through the Tunnel and Traffic That Does Not

The first step in understanding the relationship between Last Epoch and proxies is to separate two modes: an online character runs on the server side, while an offline character stays on your device. Both open from the same client but behave completely differently at the network layer; the effect of your proxy decision is visible only in the first.

The second distinction is that there is more than one service behind a single game. The distribution platform's client carries its own session, the game's account layer performs a separate verification, and the game session, once opened, moves into an uninterrupted exchange of state. Defining a proxy at one point does not cover all three.

The third concerns expectations. A proxy is not an acceleration tool but a decision about where traffic exits from: the visible address changes, a hop is added to the path, and total latency grows in most setups. The sections below explain where the scope ends and in which jobs it really pays off.

Which services come into play separately when Last Epoch starts?

When you launch the game, a single connection is not established. The distribution platform's client has already opened its own session and performs the update check with its own network stack. When the game opens, the account layer comes into play; here your character's online progress and your session entitlement are verified. Only after that do you enter the world and a continuous exchange of state begins between client and server.

The fact that these three stages take separate paths makes diagnosis easier. If your account page opens through the proxy exit in the browser but your address appears unchanged on the game side, it means the game client is opening its own socket without ever reading the operating system's proxy setting. The opposite is also common: when you set a system-wide rule, patch download traffic enters the tunnel too and a measured quota melts faster than expected.

Offline characters are outside this picture. Because they run locally they need almost nothing from the network layer. If you play without problems in offline mode but get stuck in online mode, the source of the problem is not graphics settings or the client but the account and session path. This single observation halves the area you need to search.

Before saying "it works" after setup, try three points separately: the distribution platform client logging in, the game's account verification, and entering the world with an online character. One of them working is no guarantee for the other two.

What do closed ports block on campus and office networks?

Most corporate and campus networks pass outbound traffic through a firewall and leave only well-known doors open; 80 and 443 for web traffic are almost always on that list. The doors used by game clients, however, usually are not. The symptom is familiar: store pages load, the launcher opens, but the online session simply will not connect and the connection quietly times out.

What does a proxy change in this picture? An HTTP proxy carries only TCP and opens a tunnel to encrypted destinations with the CONNECT method; because the proxy establishes the connection to the destination, the destination port does not need to be open on your network. The details of this mechanism are explained step by step in the the HTTP CONNECT method article. That said, the same firewall often also blocks egress to the proxy's own port and limits CONNECT requests to well-known destinations only.

The practical outcome can be summed up in one conditional sentence: on a closed network a proxy only helps if you can reach the proxy server and that server can connect to the destination port. If the flow to be carried is UDP-based the picture narrows further, because a CONNECT tunnel does not carry UDP and this limit cannot be lifted with a setting.

If you are working on a corporate or school network, the right step is not to try to work around the network policy but to ask the administrator: in many organisations game traffic is deliberately blocked, and that is a decision, not a fault. The access blocks on school and workplace networks article, which covers the topic as a whole, also shows when opening a request makes sense.

How far does SOCKS5's UDP ASSOCIATE command carry?

SOCKS5 defines the CONNECTcommand for TCP connections and the UDP ASSOCIATE command for UDP datagrams. The second is a separate path: the client first establishes a TCP control connection, the proxy reports a UDP relay address of its own, and datagrams flow over that relay. The moment this control connection drops, the relay closes too.

This structure on paper depends on three conditions at once. First, the proxy server actually implementing UDP ASSOCIATE support; many commercial exits offer only TCP and state so in their documentation. Second, the client being able to use this command; most game clients do not even have a field for entering a SOCKS5 server. Third, the intervening network allowing UDP relay traffic. If one of the three is missing, the UDP flow either never gets established or quietly goes outside the tunnel.

This is why in most games the proxy's scope is not real-time game traffic but login, store, patch download and launcher traffic. This should be read not as a shortcoming but as a definition of scope. The SOCKS5 UDP support article, which looks at the protocol's UDP side in more detail, also lists which client types use this command.

Per-application routing tools can hand some clients' sockets to a SOCKS5 exit; but the UDP side is again limited by the common intersection of the tool, the proxy server and the network. If you want to choose the protocol according to the type of work, the decision becomes clear when the usage distinction on the SOCKS5 proxy page is read together with the protocol selection guide 12980 What do traffic weight and the latency budget look like?

What do the traffic weight and latency budget look like?

A proxy places an extra hop on the path: the packet stops at the intermediary first and goes out to the destination from there; the return follows the same two-leg route. This architecture means that establishing a tunnel lengthens the total time in most setups. The only exception is the rare case where your default route is indirect and the proxy sits on a more direct backbone; that is not a rule but an exception that cannot be assumed without measurement.

In games that keep online progress, such as Last Epoch, the load is distributed in two separate ways. The first is volume: version updates and the initial installation produce a large download in one go and quickly consume the quota on exits billed by transferred data. The second is continuity: while the game is open there is a small but uninterrupted stream, and that stream is far more sensitive to latency than to volume.

The weights in the diagram are not measurements but representative values showing the relative share of these two dimensions. In your own setup the only correct method is to measure: before putting an exit to work, try it at several different times of day with ping test ; in shared pools, the peak-hour difference is the variable a one-off measurement hides.

One final note on managing expectations: a proxy is not a tool that improves game performance and it does not lower the ping value. The does a proxy lower game ping article, which explains why that claim is wrong through mechanism rather than numbers, is worth reading before you buy.