Guild Wars 2

• Region: EU

The ip displayed from the chat command /ip sometimes differes from the ip displayed in the loadingscreen (with the argument -maploadinfo).

Today is the first time this has happend for me.

The ip from the loading screen is part of a EU AWS (https://en.wikipedia.org/wiki/Amazon_Web_Services) IP Range (example: https://ipinfo.io/18.194.35.193), while the ip from /ip on the same map is in the private 10.0.0.0/8 range. Previous IPs were usually in the NCSoft ip range of 206.127.159.0/24.

I suspect the /ip command gives out the internal ip used on the aws instance, while the loading screen ip is the correct external ip.
Is this intended behavior or will the ip continue to differ in these cases ?

Hmm.. but are you still on the same instance
Aka same people. I sometimes use commanders as a landmark

xyoz.6710:

Is this intended behavior or will the ip continue to differ in these cases ?

Is showing Amazon’s internal IP intended? Probably not, but it doesn’t really matter unless you were planning to ping it.

They started to use Amazon’s cloud computing a few months ago in NA, originally for some of the HoT maps, and now in various areas. It could be just a pass-through or it could actually be hosting the instances, which is kind of a big deal. This is likely an experiment, so something so trivial may not be fixed unless they plan on transitioning over.

Amaimon.7823:

Hmm.. but are you still on the same instance
Aka same people. I sometimes use commanders as a landmark

From the average player’s perspective, you don’t need to care about this. When a LFG listing lists what IP they’re on, they’re going to use what’s shown in /ip. It doesn’t matter that the real IP is different. Just note that whenever you see the 10.* IP address, you’re playing through Amazon’s servers.