Higher Ping to Washington DC Servers

I recently noticed that my ping to the Washington DC servers has increased from ~8-14ms average to great than 24ms average.

I did some investigating to make sure the issue wasn't on my end and the issue seems to be from one specific hop that appears be at the data center hosting the DC servers.

Below is a tracert showing what I am seeing. Hop 9/10 is the one that seems to be struggling. I've also had a couple friend check and they are seeing the same issue.

I ran pingplotter against this address as well and can see similar results but have some more information that might help. The address at hop 9 (50.97.17.32) showed a packet loss of >27% where no other hops had any issues.

I figured I would bring up this issue now, so hopefully it can be investigated before the league launch. The extra latency doesn't make things unplayable, but it is noticeable.

Please let me know if there's anything else I can provide to hopefully fix this issue. Although I think this is outside of my ability to fix and will require GGG to reach out to their hosting technical support.

> 1 <1 ms <1 ms <1 ms 192.168.1.1
> 2 <1 ms 1 ms 1 ms 192.168.10.254
> 3 2 ms 3 ms 1 ms adsl-172-10-88-1.lightspeed.iplsin.sbcglobal.net [172.10.88.1]
> 4 2 ms 3 ms 2 ms 71.152.199.124
> 5 * * * Request timed out.
> 6 10 ms 7 ms 7 ms 32.130.17.75
> 7 7 ms 8 ms 8 ms gar2.clboh.ip.att.net [12.122.133.197]
> 8 6 ms 10 ms 9 ms 12.118.39.190
> 9 8 ms 8 ms 64 ms ae5.cbs02.eq01.chi01.networklayer.com [50.97.17.32]
> 10 27 ms 28 ms 27 ms ae1.cbs02.cs01.wdc05.networklayer.com [169.45.19.110]
> 11 26 ms 27 ms 26 ms ae3.dar03.wdc04.networklayer.com [169.45.18.239]
> 12 28 ms 28 ms 26 ms 87.76.3fa9.ip4.static.sl-reverse.com [169.63.118.135]
> 13 26 ms 26 ms 28 ms po1004.fcr03a.wdc04.networklayer.com [169.55.118.207]
> 14 28 ms 26 ms 25 ms b7.61.37a9.ip4.static.sl-reverse.com [169.55.97.183]

A WinMTR which was ran while you played with the problem for a minimum 300 seconds, it's the only thing they ask for.

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

Thank you lagwin1980 for the link/explanation.

I followed the links provided and downloaded the WinMTR tool and ran a check against the same IP address. It appears this tool is just a longer running tracert.

My results are below. Same issues/results as posted before. I would also like to mention that I did check a few different IP addresses I found from my Client.txt file and found they all end up hitting a similar problem/same final few hops. (At least for the DC server.)

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 529 | 529 | 0 | 0 | 0 | 0 |
| 192.168.10.254 - 0 | 529 | 529 | 0 | 0 | 2 | 0 |
|adsl-172-10-88-1.lightspeed.iplsin.sbcglobal.net - 0 | 529 | 529 | 1 | 2 | 5 | 3 |
| 71.152.199.124 - 0 | 529 | 529 | 1 | 2 | 8 | 2 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| 32.130.17.75 - 0 | 529 | 529 | 6 | 11 | 24 | 9 |
| gar2.clboh.ip.att.net - 0 | 529 | 529 | 6 | 10 | 124 | 8 |
| 12.118.39.190 - 0 | 529 | 529 | 6 | 8 | 41 | 7 |
| ae5.cbs02.eq01.chi01.networklayer.com - 26 | 266 | 199 | 7 | 10 | 67 | 9 |
| ae1.cbs02.cs01.wdc05.networklayer.com - 0 | 529 | 529 | 26 | 27 | 38 | 28 |
| ae3.dar03.wdc04.networklayer.com - 0 | 528 | 528 | 25 | 27 | 68 | 27 |
| 87.76.3fa9.ip4.static.sl-reverse.com - 0 | 529 | 529 | 25 | 28 | 79 | 29 |
| po1004.fcr03a.wdc04.networklayer.com - 0 | 529 | 529 | 25 | 26 | 29 | 26 |
| b7.61.37a9.ip4.static.sl-reverse.com - 0 | 529 | 529 | 25 | 25 | 29 | 27 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider