Path of Exile and Proxies: Which Traffic Goes Through the Tunnel and Which Doesn't?

Don't confuse packet loss with latency

Latency is the time it takes a packet to go and come back; loss is the packet never arriving at all. The two can degrade independently. A high-latency but loss-free line feels consistently slow. A low-latency but lossy line usually works normally, then suddenly produces rubber-banding or a short freeze. The "stuttering" people complain about while playing an ARPG is usually the latter.

A single-shot ping is not enough for measurement. Take a long, continuous measurement; there are three numbers to look at: response time, the proportion of requests left unanswered, and the variation between consecutive measurements. High values appearing in the middle of tools that list intermediate nodes are frequently misread: routers process control packets addressed to themselves at low priority, so a spike in the middle is not on its own proof of a problem. What matters is the behaviour at the endpoint.

If a proxy is in play, the path splits in two and the diagnosis must split in two as well. First measure only the leg between you and the proxy. If loss starts there, the problem is either in your local line or in the proxy's access network; changing the exit country will not help. If loss appears only when going through the proxy to the destination, the second leg is at fault and the solution here is to try a different exit.

• Keep the measurement running for at least a few minutes; short tests hide loss.
• On a wireless connection, part of the loss you measure comes from local radio conditions.
• If a download is running at the same time the measurement is invalid; clear the line and repeat.
• Test the proxy leg and the destination leg separately and note the result.
• Compare the results at two different times of day.

To quickly see whether an exit is alive and what its response time is, proxy checker tool can be used; for a broader account of measurement methodology proxy latency article.

Where does SOCKS5's UDP door close in practice?

An HTTP proxy opens a path to encrypted destinations with the CONNECT method; by definition the path it opens is locked to TCP. Because the bulk of real-time game traffic uses UDP, a classic HTTP proxy cannot carry that traffic under any circumstances. On the SOCKS5 side, a command called UDP ASSOCIATE is defined, and in theory UDP can be carried.

The difference between theory and practice is that it requires support from both sides. First, the proxy server must actually implement this command; many commercial exits open TCP only and return a "not supported" response to the command. Then the client must know how to use that path. Most game clients have no proxy setting, so they do not use SOCKS5 of their own accord.

The conclusion is this: the real scope of a proxy on the Path of Exile side is login, the account page, the trade site, the launcher and patch downloads. Putting the session where your character sits through the tunnel requires a routing layer outside the client; that layer adds both extra latency and a new source of failure, and if the provider does not support UDP it produces no result anyway.

Follow this order when choosing a protocol: if the traffic you will carry is web, an HTTP proxy is enough; if you are going to use a tool other than a browser, check which field the tool offers. For a detailed comparison, SOCKS5 UDP support and SOCKS5 proxy pages, and for tunnelling mechanics the HTTP CONNECT method article.

A server gateway list is not the same thing as a proxy setting

The client lists the server gateways you can connect to and shows, for each, the latency it measured itself. That measurement is made over the client's own connection. A proxy defined in the browser has no effect on the list; the client measures from your usual line and ranks according to that line.

If you have set up system-wide routing the picture changes: this time the measurement is made over the tunnel and the list may look different depending on the exit country. This does not mean "a better gateway was found"; only the starting point of the measurement has changed. Once you start playing, what matters is the path the packet actually takes, and if that path still goes through the proxy, the low value on the list will mislead you.

Keep the decision rule simple: gateway selection is the game's job, the proxy decision is the job of the web and account side. Tying the two to a single setting is the most common source of unsolvable problems. If you see higher values than expected in the gateway list, first check whether a system-level route has been left on.

If you are connecting from a school or workplace network the picture gets one layer more complicated: on these networks some ports may be closed entirely, and the symptom is not "high latency" but "no connection at all". This distinction and how to diagnose it access blocks on school and workplace networks is covered separately in the article.

What is covered depending on where you write the configuration?

There are four places, and their scopes differ. A browser profile or extension affects only that profile; it does not disrupt your other work but does not touch the launcher either. The operating system setting covers every application that reads the proxy. A rule at router level affects every device in the house. Per-application routing puts only the process you select into the tunnel and has the fewest side effects.

In the context of Path of Exile, this choice is made according to the job. If you only want to verify the trade site from another country, a separate browser profile is the right answer. If the launcher cannot reach the update servers on a corporate network, you need the system setting. Routing the entire home network usually produces an undesirable result, because it will cover the game session as well.

The same provider may offer HTTP and SOCKS5 service on two separate ports or on a single port; entering values without reading from the panel which line belongs to which protocol is where setup errors begin. Don't skip verification after setup: my IP address the page tells you which exit you appear from, and a separate check for tools outside the browser tells you whether the rule is actually being applied.

From symptom to cause: the diagnostic order

The table below matches the symptoms most frequently encountered while using a proxy with their likely causes. Keep to the order: do not move to authentication before verifying scope, or to network quality before ruling out authentication.

407 is almost always related to authentication. It has two sources: either the client is not sending the credentials at all, or the provider recognises you by IP authorisation and your home line's address has been renewed. The second recurs regularly for users with dynamic IPs, and the fix is to update the authorised address from the panel.

A certificate warning does not carry the same weight as the other symptoms on this list; it is not a configuration snag but a question of trust. A properly established HTTPS tunnel does not interfere with the TLS session; if you see a warning, it means your traffic is being decrypted and re-encrypted somewhere. Because your account page's session information also passes through that point, clicking through the warning means handing your session over in readable form to a party you do not know.

Realistic expectations, exit type and compliance

Not every scenario requires a proxy. If you are playing normally from your own country with your own account, adding a layer in between gains you nothing; you only add latency, cost and a new source of failure. The cases where a proxy is meaningful are narrow and clear: leaving a corporate network through a fixed exit, verifying how trade and announcement pages look in a different region, and solving access to patch servers on a restricted network.

The exit type decision is made together with the job as well. Because stability and bandwidth come to the fore in download- and web-heavy work, ISP proxy or datacenter exits give balanced results. For verification work that needs to stay close to a typical home connection, a residential exit is preferred. Mobile exits, being billed by data, quickly generate cost on large downloads.

Finally, the compliance side: changing your exit does not change your account's rules. Account sharing, automated play tools and methods that interfere with the game's security layer are outside the scope of this page and are not recommended. Here a proxy is a visibility and access tool; the only thing that changes is where the other side considers your connection to have come from.