So, EU servers where moved to the US again? They werent.

AlexDougherty · December 2014

magnusnet wrote: »

lordrichter wrote: »

No, they did not move it. It is still in Frankfurt. You need to find a better geolocation service.

Before, doing the same thing gave me a german IP. In any case, at the time I took that screenshot, my client was connecting to that address which is in the US which you would have known if you had done any search what so ever, before assuming it's wrong.

I wonder if anyone has pointed out that the password verifier seems to be part of the US server.

Because the other week when the us server was down, we EU players couldn't log in. It may be that your ping is just bouncing of the part that verifies your account name and password is correct.

Just a thought.

TehMagnus · January 2015

This thread is still actual, despite what trolls said, server is in fact located in NA. Care to comment ZOS?

burningcrow · January 2015

AlexDougherty wrote: »

magnusnet wrote: »

lordrichter wrote: »

No, they did not move it. It is still in Frankfurt. You need to find a better geolocation service.

Before, doing the same thing gave me a german IP. In any case, at the time I took that screenshot, my client was connecting to that address which is in the US which you would have known if you had done any search what so ever, before assuming it's wrong.

I wonder if anyone has pointed out that the password verifier seems to be part of the US server.

Because the other week when the us server was down, we EU players couldn't log in. It may be that your ping is just bouncing of the part that verifies your account name and password is correct.

Just a thought.

I was just gonna say it. I bet this is what it is.

Elsonso · January 2015

TehMagnus wrote: »

This thread is still actual, despite what trolls said, server is in fact located in NA. Care to comment ZOS?

Clever. Trying to get them to deny one rumor so as to implicitly confirm another.

In this case, there is direct evidence, current to today, that the server is in Germany, so I am not sure how that tactic will play out.

Jitterbug · January 2015

Gyudan wrote: »

Jitterbug wrote: »

Just a thought: Would it make sense to merge the servers and let us play together?

Merge servers into the US and EU will complain about lag.
Merge servers into the EU and US will complain about lag.
Lag.

sure, but if the EU server is in Texas anyway...

technohic · January 2015

Teargrants wrote: »

They hoped you'd be thrown off by the city name being Amsterdam.

I live in Ohio and never knew Amsterdam was so close. I need to do some window shopping.

TehMagnus · January 2015

lordrichter wrote: »

TehMagnus wrote: »

This thread is still actual, despite what trolls said, server is in fact located in NA. Care to comment ZOS?

Clever. Trying to get them to deny one rumor so as to implicitly confirm another.

In this case, there is direct evidence, current to today, that the server is in Germany, so I am not sure how that tactic will play out.

Please, do share this "evidence". Up untill now, all the posted and visible evidence points to the servers being in the US. I'm not asking for confirmation, I know the servers are in the US. Just want to know why and why we haven't been warned. And when are the servers moving back to the EU

.

As for the login being in the US, I'll post the data usage when I get home, all my game & data packets are going to the US IP.

Elsonso · January 2015

EU Megaserver

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 (AS202167 ZENIMAX-GERMANY ZeniMax Germany GmbH)
13 159.100.232.160 159.100.232.160 <-Megaserver

NA Megaserver

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1
4 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.28 gbg-core-1.hundredgige0-6-0-0.tele2.net
8 130.244.205.179 ams-core-2.bundle-ether1.tele2.net
9 130.244.38.233 ams13-peer-1.ae8-unit0.tele2.net
10 4.68.110.65 ge-7-44.car1.LosAngeles.Level3.net
11 4.69.145.75 ae-2-70.edge2.Dallas1.Level3.net
12 4.69.145.75 ae-2-70.edge2.Dallas1.Level3.net
13 4.71.220.10 ZENIMAX-MED.edge2.Dallas1.Level3.net

fromtesonlineb16_ESO · January 2015

TehMagnus wrote: »

You can also check this by running Xfire, an American flag will appear next to TESO when you're InGame.

Please educate yourself about geo-location using IP addresses and also how IP blocks are processed and registered by ICANN before continuing.

Hint: where an IP block owner registers that block to and where they deploy it are entirely unrelated.

TehMagnus · January 2015

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

13 159.100.232.160 159.100.232.160 <-Megaserver

This is North America IP address.

Thanks for proving my point.

Tankqull · January 2015

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

just for you:
http://myip.ms/info/whois/159.100.232.160

@ZOS any statement?

TehMagnus · January 2015

Tankqull wrote: »

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

just for you:
http://myip.ms/info/whois/159.100.232.160

And prior to the 6h+ bug in the patch, when I tried to locate the IP or when I used Xfire, i had a german location, not US.

Elsonso · January 2015

TehMagnus wrote: »

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

13 159.100.232.160 159.100.232.160 <-Megaserver

This is North America IP address.

Thanks for proving my point.

It is the EU megaserver.

But if this is the NA megaserver, it is in GERMANY.

TehMagnus · January 2015

fromtesonlineb16_ESO wrote: »

TehMagnus wrote: »

You can also check this by running Xfire, an American flag will appear next to TESO when you're InGame.

Please educate yourself about geo-location using IP addresses and also how IP blocks are processed and registered by ICANN before continuing.

Hint: where an IP block owner registers that block to and where they deploy it are entirely unrelated.

My IP block owner is owned by my employee and registered in Paris, French capital, but doing a geolocalisation on my IP will locate me in the town I'm in currently which is 400km from Paris

pppontus · January 2015

fromtesonlineb16_ESO wrote: »

TehMagnus wrote: »

You can also check this by running Xfire, an American flag will appear next to TESO when you're InGame.

Please educate yourself about geo-location using IP addresses and also how IP blocks are processed and registered by ICANN before continuing.

Hint: where an IP block owner registers that block to and where they deploy it are entirely unrelated.

This guy is actually correct in this case. Geolocation in these cases is based on the country/location that is supplied by the company registering a block of IP addresses, parts of these addresses can definitely be deployed in a completely different region (for example one of our ISPs here in Stockholm, Sweden is a UK based company so a geolocation of that IP which I am using here, will give you London, UK).

A better way of determining location is to check several addresses at the end of the traceroute, as if the second to last location is in EU it is with 99% certainty that you won't have a one-hop route straight to a server in the US.. that just doesn't happen unless you happen to own your own cable across the ocean which I guess it's safe to say that ZOS doesn't.

9 193.159.165.121 193.159.165.121 <- Deutsche Telekom AG, Germany
10 217.239.44.50 217.239.44.50 <- Deutsche Telekom AG, Germany
11 193.159.226.18 193.159.226.18 Deutsche Telekom AG, Germany
12 195.122.154.3 <- Level 3 Communications Ltd, UK (likely another case of a provider owning subnets used in a variety of countries)
13 159.100.232.160 159.100.232.160 <- ZOS Server (using their subnet which is registered to a US location, but actually it is very obviously in Germany)

This is a great tool to use if you wish to make accurate geolocations as well:

http://www.monitis.com/traceroute/index.jsp?url=159.100.232.160&testId=612630

Here you can quite clearly see that it is in Europe, just the latency (133ms in US vs. 26ms in EU) gives that away. Also the IP in question is reported as UK here which is simply because different Geolocation services have varying degrees of accuracy..

If anyone needs a reason to trust me on this, I work as a System/Network Admin with several sites all across the world and thus know quite a few things about international routing.

I hope Zenimax considers this rumor officially slaughtered, and grant me an in-game achievement and title. Jokes aside, it's an easy mistake to make.. but no, the EU server has not been moved. Whether that is good or bad, I have no opinion on.

Enjoy your evenings and hope you all sleep better knowing they didn't lie to us (about this).

ginoboehm · January 2015

TehMagnus wrote: »

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

13 159.100.232.160 159.100.232.160 <-Megaserver

This is North America IP address.

Thanks for proving my point. Just because it transits through multiple addresses including an address in Frankfurth (probably load balancer), the final destination is still in the US.

well the thing is ip-geolocating has its flaws. It is very well possible that the server is still in Europe and they are just reusing an ip address a server got assigned in the USA. so if you apply for a static ip address you get one from the country (the ip pool of the country) in which you applied for.
Let us test amazon.de (because I think to remember I read somewhere about their German servers)
cmd -> nslookup amazon.de 8.8.8.8 i get the ip address 178.236.7.219 which is located in Ireland which seems logical because amazon's europe headquarters are in Ireland. you can as a European company go to an american static ip provider and apply for an static ip address. you will get an ip adress from the american pool then. ip-geolocating works best for dynamic assigned ip addresses. I believe besides confusing some users this represents no problem, if it is really just an american ip assigend to a european server (i guess no dns lookup is needed).
What strikes me odd is that some of you say they used an ip address pointing to a European locations before. I have no logical explanation for this. You could assume they have some ip addresses from both pools and the loadbalancer just scrolls thru these different servers but I don't think loadbalancers work like this or at least as a software developer my knowledge about networks stop around this very basic level.

TehMagnus · January 2015

Well I will be going to bed being less stupid tonight then 8°) thanks @pppontus for the extensive explanation.

pppontus · January 2015

ginoboehm wrote: »

TehMagnus wrote: »

lordrichter wrote: »

1 176.221.87.3 3.87.221.176.pingdom.com
2 92.43.37.126 f126.broadband2.quicknet.se
3 10.5.12.1 10.5.12.1
4 212.247.178.9 212.247.178.9
5 130.244.39.46 vst-ncore-1.bundle-ether1.tele2.net
6 130.244.71.178 kst5-core-1.bundle-ether6.tele2.net
7 130.244.39.25 avk-core-1.hundredgige0-6-0-1.tele2.net
8 130.244.64.71 avk6-peer-1.ae0-unit0.tele2.net
9 193.159.165.121 193.159.165.121
10 217.239.44.50 217.239.44.50
11 193.159.226.18 193.159.226.18 (AS3320, DTAG Deutsche Telekom AG,DE)
12 195.122.154.3 <-Zenimax
13 159.100.232.160 159.100.232.160 <-Megaserver

13 159.100.232.160 159.100.232.160 <-Megaserver

This is North America IP address.

Thanks for proving my point. Just because it transits through multiple addresses including an address in Frankfurth (probably load balancer), the final destination is still in the US.

well the thing is ip-geolocating has its flaws. It is very well possible that the server is still in Europe and they are just reusing an ip address a server got assigned in the USA. so if you apply for a static ip address you get one from the country (the ip pool of the country) in which you applied for.
Let us test amazon.de (because I think to remember I read somewhere about their German servers)
cmd -> nslookup amazon.de 8.8.8.8 i get the ip address 178.236.7.219 which is located in Ireland which seems logical because amazon's europe headquarters are in Ireland. you can as a European company go to an american static ip provider and apply for an static ip address. you will get an ip adress from the american pool then. ip-geolocating works best for dynamic assigned ip addresses. I believe besides confusing some users this represents no problem, if it is really just an american ip assigend to a european server (i guess no dns lookup is needed).
What strikes me odd is that some of you say they used an ip address pointing to a European locations before. I have no logical explanation for this. You could assume they have some ip addresses from both pools and the loadbalancer just scrolls thru these different servers but I don't think loadbalancers work like this or at least as a software developer my knowledge about networks stop around this very basic level.

The IP address: 159.100.232.160 is as you say more than likely pointing to a load balancer or something like that, which would handle incoming traffic and send it to servers handling different shards etc.

It is not exactly uncommon to change IP addresses when doing major reconfiguration etc. It could be they set up a new cluster/loadbalancer or simply staged a reconfiguration and used a new IP while doing the work so that they could keep the old one alive for as long as possible using the old IP.

If I remember correctly they reported that they were going to do some rework of the network infrastructure a month or so after the migration, due to the many complaints about lag.

SFBryan18 · January 2015

Likely when they physically moved the server, they didn't change its ip, and that ip is registered as American even though it is in Germany.

Weberda · January 2015

In any event it was an informative thread for many of us and the OP is to be thanked for that. So many of the threads make me want to just shut off my computer.