Server Locations

I know if I run the winmtr to the san jose one I get nothing but 18-22ms, that is normal. I'm trying to figure out why they are moving us to the new york, and back lol.

I got that ip address here from the resource monitor in win10.



From what I can tell, it looks like im going to san jose, then to new york city, then back to san jose lol. WHAT haha.
Last edited by ZeuZLoD#0684 on Oct 31, 2019, 8:16:04 PM
I thought I was clear in my first post where I showed my WinMTR trace from my home in SW Florida to the Dallas PoE realm but I guess not.

1. Go to the WinMTR page
2. Highlight and copy the California PoE realm address (sjc.speedtest.pathofexile.com)
3. Run WinMTR
4. paste the sjc address into WinMTR and run it 100 times.
5. make a screen dump, crop it, and post the results.

Here's my WinMTR test (the Internet does know the way to San Jose):


The last entry in WinMTR should be "speedtest.sjc01.softlayer.com". I have no idea why you are using an internal network 172.96.116.74 address. That is WRONG. If you insist on using an ip address, sjc.speedtest.pathofexile.com resolves to 50.23.64.58.

My test shows higher latency of > 100 ms which is normal as I'm going farther out on the Internet (Miami to San Jose). It also shows that Networklayer is still routing my link through the shitty dal04 node (Nr=11). The Los Angeles nodes (Nr=12 and 13 that have lax in the name) aren't too good either.

It all boils down to the fact that PoE runs from Softlayer game hosting data centers and Softlayer is linked to Networklayer Internet fiber backbone and it's the god damn shitty Networklayer that completely wrecks PoE quality of play (SIGH!).

"You've got to grind, grind, grind at that grindstone..."
Necessity may be the mother of invention, but poor QoP in PoE is the father of frustration.

The perfect solution to fix Trade Chat:
www.pathofexile.com/forum/view-thread/2247070
Last edited by Arrowneous#3097 on Nov 1, 2019, 7:02:36 AM
There are a number of different types of servers with different jobs. You contact a different server to create an instance than you do to access your stash, another to log into the game, and another to play the game. There's probably even more than that... something to do with challenges.
Dude I already know (and have stated) that the ping is what it should be to that lol. I'm simply wondering why its putting me in 100ms (nyc from what I can tell) for my maps and hideout. Here is the ss you are seeking (not sure why though lol).



That ip that I got was from what the game showed me from the resource monitor, not something I just made up and ran the winmtr. The results from that are what you saw in that SS and not from anything I did lol.

Its clear as day though when im thrown into the 100ms hideout that its putting me in some new york city (i think so anyways) location. It used to be 20 across the board with hideouts and maps. I'm curious as to why the sudden change.

Speaking to a few other people which are seeing the same thing speculate that they are simply cutting back on server capacity for the sjc server so it throws me into main ones which I think are on the east cast judging from the ping. It makes a lot more sense now since i've been put in the sjc only a couple of times in the past week but majority of the time its 100ms across the board.
Last edited by ZeuZLoD#0684 on Nov 1, 2019, 7:25:39 AM
"
Arrowneous wrote:
Where did you get that ip address? Is that the California PoE Realm? All I do is go to the WinMTR page and copy the appropriate long PoE realm address and paste it into WinMTR and run it for at least 100 iterations.

Edit: That ip address starts with 172 which is reserved as a private local address (same as 192.168.x.x) so that can't be a valid PoE realm address. Go back to the WinMTR page and copy the address of the appropriate PoE realm you normally play on and run it again.


Your statement about IP is NOT correct.
Here is the list about what IPv4 IP's that it reserved as being private -->

Private IP-address.:

Private internal addresses are not routed on the Internet and no traffic cannot be sent to them from the Internet, they only supposed to work within the local network.
Private addresses include IP addresses from the following subnets:

Range from 10.0.0.0 to 10.255.255.255 — a 10.0.0.0 network with a 255.0.0.0 or an /8 (8-bit) mask

Range from 172.16.0.0 to 172.31.255.255 — a 172.16.0.0 network with a 255.240.0.0 (or a 12-bit) mask

A 192.168.0.0 to 192.168.255.255 range, which is a 192.168.0.0 network masked by 255.255.0.0 or /16

So the server IP 172.92.117.10 is a valid public IP.

Report Forum Post

Report Account:

Report Type

Additional Info