high ms

Hi since a couple days i have stable 150 ms on sao pablo, usually it's around 35-40ms and my internet works fine in anything else i ran winmtr and this is the result, hope it helps to fix my problem

https://pastebin.com/gaGtQwkU
Last bumped on Jan 16, 2026, 9:12:51 PM
bump, help please =)
bump! im having the same issue, login server 39ms but in-game 140 - 150ms
"
bump! im having the same issue, login server 39ms but in-game 140 - 150ms

Do this and follow the instructions exactly.
WinMTR

This is what GGG recommends:
Ensure to do this when the lag, high ping, packet loss, or connection issues are happening.

https://www.pathofexile.com/forum/view-thread/1377789

After running this test per the instructions please link the URL of the pastebin back here

The instructions are the same for PoE2, just locate the file in the appropriate installation folder.
https://pastebin.com/cdp9u4xv
"
https://pastebin.com/cdp9u4xv

I don't see your final destination IP address in the trace..
But, going off the 84.16.9.21 address near the bottom (Sao Paulo) I'll assume the final is a server location IP from your client log file.

The trace is straight forward and the problem is between your ISP and the final destination. In fact it appears to be within the same network.

The only recourse you have here is to ideally get the final destination IP address you tested for this WinMTR and send the trace(s) to your ISP.. the final IP is not super important but it helps.

The telling factor here is the ~120ms latency increase after your ISP.

What happens if you cross reference a WinMTR to a reputable DNS server in SA while this issue is happening in PoE?
Ideally the DNS trace lands on Sao Paulo also.
8.8.8.8 (Google)
1.1.1.1 (Cloudflare)
Last edited by Eleven777#0993 on Jan 16, 2026, 5:16:07 PM
"
"
https://pastebin.com/cdp9u4xv

I don't see your final destination IP address in the trace..
But, going off the 84.16.9.21 address near the bottom (Sao Paulo) I'll assume the final is a server location IP from your client log file.

The trace is straight forward and the problem is between your ISP and the final destination. In fact it appears to be within the same network.

The only recourse you have here is to ideally get the final destination IP address you tested for this WinMTR and send the trace(s) to your ISP.. the final IP is not super important but it helps.

The telling factor here is the ~120ms latency increase after your ISP.

What happens if you cross reference a WinMTR to a reputable DNS server in SA while this issue is happening in PoE?
Ideally the DNS trace lands on Sao Paulo also.
8.8.8.8 (Google)
1.1.1.1 (Cloudflare)


hahaha yea lol, like my ISP(Telecentro) cares about this, last year this issue lasted like 3 or 4 months and is the only game i was having this problem, the issue fixed after the 0.4 update til last wednesday (for me is clear that GGG did something and that something broke again).
"
hahaha yea lol, like my ISP(Telecentro) cares about this, last year this issue lasted like 3 or 4 months and is the only game i was having this problem, the issue fixed after the 0.4 update til last wednesday (for me is clear that GGG did something and that something broke again).


When you did have the issue last time, did you run a WinMTR to compare?

When you do NOT experience this issue have you run a WinMTR to compare?

Have you tried a free VPN in the past or present to test the connection and routing?

Did you even look at the information that was provided to you?

Do you know how to interpret where the ping spike is starting in your graph?

Do you think GGG wants you to have a bad experience with high latency?

You may think my post is funny, but it's ultimately under your own control to get it looked into.

There are lots of posts about Sao Paulo, Singapore, JP, Los Angeles, Euro servers, Washington DC... but most of them are isolated due to routing and pathing issues and they are proven time and time again... just like yours that they're routing or ISP related. Very rare cases are the direct servers at fault.
what about my post? it's ISP routing problem too?
"
what about my post? it's ISP routing problem too?

200-32-127-97.static.impsat.net.ar

This line is where your high ping starts

Report Forum Post

Report Account:

Report Type

Additional Info