So, EU Mega Server is not in Frankfurt but in the USA

code65536

A little learning is a dangerous thing; drink deep, or taste not the Pierian spring: There shallow draughts intoxicate the brain, and drinking largely sobers us again.

@Mathius_Mordred This is a case of someone knowing just enough that they think they know what they're saying. But they don't know enough to know that they're wrong.

First, do you know where that location data comes from? There is no magical mechanism that lets you know where a server is located. The IP location lookup you used relies on information in a database. That information is supplied by whoever manages each block of IP addresses. The person supplying that information could say "North Pole" if they wanted. That doesn't mean that it's actually located at the North Pole.

Second, why would someone supply the "wrong" location for a block of IP addresses? Well, that's because IP addresses are not necessarily tied to any physical location. The data goes wherever the routers send it. Take, for example, my mobile phone. I get an IPv4 address from my carrier, and if I ask about the location of that address, it says that it's in Seattle. Even though I'm on the other side of the country. Because they had simply entered the location of their company headquarters in the database. Why would the mobile carrier do that? Maybe because it's easier to say, "all these addresses belong to us, and we are HQ'ed in Seattle" than to say, "this little block here we're currently using for customers in New York, and that block is being used in Miami, and that other block is New York too...". THIS IS ACTUALLY FAIRLY COMMON. The information in this database does not affect how the network runs--it's purely an administrative bookkeeping thing, and a lot of companies see no point in going into fine details like that when it serves absolutely no purpose.

It's pretty clear that the physical address seen in the whois database is just the Bethesda HQ.

Third, so how do you find where a server is located? The database that you queried is clearly the wrong approach. The right approach is to follow the packets themselves. You need to trace the route.

Tracing route to 159.100.232.100 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  172.16.64.1
  2     2 ms     1 ms     2 ms  10.26.1.219
  3     2 ms    12 ms    14 ms  23-255-225-139.mci.googlefiber.net [23.255.225.139]
  4     2 ms     2 ms     2 ms  192-119-18-184.mci.googlefiber.net [192.119.18.184]
  5     *        *        *     Request timed out.
  6    19 ms     8 ms     8 ms  23-255-225-180.mci.googlefiber.net [23.255.225.180]
  7     8 ms     8 ms     8 ms  ix-ae-60-0.tcore2.aeq-ashburn.as6453.net [216.6.87.88]
  8     9 ms     9 ms     9 ms  216.6.87.6
  9    99 ms   106 ms    99 ms  217.239.51.42
 10    99 ms    98 ms    98 ms  80.156.160.98
 11    99 ms    99 ms    99 ms  195.122.154.3
 12    99 ms    98 ms    99 ms  159.100.232.100

Look at hops #9, #10, and #11, right when the ping jumps up indicating a possible crossing of a large body of water and the last three stops right before hitting the destination. 217.239.51.42 and 80.156.160.98 are both registered to Deutsche Telekom, and 195.122.154.3 is registered to ZeniMax Germany GmbH. Sure looks like Germany to me, ja?

Finally, just common sense. I'm in the US. I see higher ping connecting to EU than to NA, even though I'm pretty close to Maryland.

TL;DR: STOP SPREADING FALSE INFORMATION If you're going to make threads like this, I suggest that you actually learn about the subject matter first.

anitajoneb17_ESO

Alcast wrote: »

anitajoneb17_ESO wrote: »

Katahdin wrote: »

Alcast already answered this

The login server is in the U.S.
The actual EU game server is in Germany

While this actually makes sense, I'd love some more detailed explanations (yes I'm curious). Currently it shows that ALL my traffic from me to ESO goes to the US. I mean, ALL my data (including pure playing data, not login) doesn't go through the US login server, does it ?

Is that only during prime time or all day? What tools do you use to see this?

Well, I looked this up only yesterday - which was sunday, which I guess is EU prime time...
I used the built-in win10 monitoring tool as well as a 3rd party connection viewing tool and they both showed the same IP addresses (the 159.100.232.xx ). Which I checked online via various websites provided by a Google Search (whatsmyip, whois, oinline "tracert" tools, etc... that sort of things).

I guess the explanation was provided by @code65536 ... simple administrative database that has little to nothing to do with the actual locations of said IP...

ZOS_SarahHecker

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

rotaugen454

ZOS_SarahHecker wrote: »

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

And next come the “I don’t believe them” crowd...

code65536

rotaugen454 wrote: »

ZOS_SarahHecker wrote: »

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

And next come the “I don’t believe them” crowd...

All the evidence points to Frankfurt. This thread was founded on an amateurishly faulty understanding of how the Internet works.

anitajoneb17_ESO

code65536 wrote: »

rotaugen454 wrote: »

ZOS_SarahHecker wrote: »

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

And next come the “I don’t believe them” crowd...

All the evidence points to Frankfurt. This thread was founded on an amateurishly faulty understanding of how the Internet works.

And you did a great job at explaining. I learned stuff. Thank you :-)

Mathius_Mordred

code65536 wrote: »

A little learning is a dangerous thing; drink deep, or taste not the Pierian spring: There shallow draughts intoxicate the brain, and drinking largely sobers us again.

@Mathius_Mordred This is a case of someone knowing just enough that they think they know what they're saying. But they don't know enough to know that they're wrong.

First, do you know where that location data comes from? There is no magical mechanism that lets you know where a server is located. The IP location lookup you used relies on information in a database. That information is supplied by whoever manages each block of IP addresses. The person supplying that information could say "North Pole" if they wanted. That doesn't mean that it's actually located at the North Pole.

Second, why would someone supply the "wrong" location for a block of IP addresses? Well, that's because IP addresses are not necessarily tied to any physical location. The data goes wherever the routers send it. Take, for example, my mobile phone. I get an IPv4 address from my carrier, and if I ask about the location of that address, it says that it's in Seattle. Even though I'm on the other side of the country. Because they had simply entered the location of their company headquarters in the database. Why would the mobile carrier do that? Maybe because it's easier to say, "all these addresses belong to us, and we are HQ'ed in Seattle" than to say, "this little block here we're currently using for customers in New York, and that block is being used in Miami, and that other block is New York too...". THIS IS ACTUALLY FAIRLY COMMON. The information in this database does not affect how the network runs--it's purely an administrative bookkeeping thing, and a lot of companies see no point in going into fine details like that when it serves absolutely no purpose.

It's pretty clear that the physical address seen in the whois database is just the Bethesda HQ.

Third, so how do you find where a server is located? The database that you queried is clearly the wrong approach. The right approach is the follow the packets themselves. You need to trace the route.

Tracing route to 159.100.232.100 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  172.16.64.1
  2     2 ms     1 ms     2 ms  10.26.1.219
  3     2 ms    12 ms    14 ms  23-255-225-139.mci.googlefiber.net [23.255.225.139]
  4     2 ms     2 ms     2 ms  192-119-18-184.mci.googlefiber.net [192.119.18.184]
  5     *        *        *     Request timed out.
  6    19 ms     8 ms     8 ms  23-255-225-180.mci.googlefiber.net [23.255.225.180]
  7     8 ms     8 ms     8 ms  ix-ae-60-0.tcore2.aeq-ashburn.as6453.net [216.6.87.88]
  8     9 ms     9 ms     9 ms  216.6.87.6
  9    99 ms   106 ms    99 ms  217.239.51.42
 10    99 ms    98 ms    98 ms  80.156.160.98
 11    99 ms    99 ms    99 ms  195.122.154.3
 12    99 ms    98 ms    99 ms  159.100.232.100

Look at hops #9, #10, and #11, right when the ping jumps up indicating a possible crossing of a large body of water and the last three stops right before hitting the destination. 217.239.51.42 and 80.156.160.98 are both registered to Deutsche Telekom, and 195.122.154.3 is registered to ZeniMax Germany GmbH. Sure looks like Germany to me, ja?

Finally, just common sense. I'm in the US. I see higher ping connecting to EU than to NA, even though I'm pretty close to Maryland.

TL;DR: STOP SPREADING FALSE INFORMATION If you're going to make threads like this, I suggest that you actually learn about the subject matter first.

First of all, who the hell are you to tell me what to do, especially when you seem to know nothing about the subject at all.
Secondly, I was asking about this apparent IP location which my ESO64.exe is actually connected to, I was spreading false information I am asking if this is the case?
Thirdly, in your example, you conveniently totally disregarded the last hop in your Tracrt which is: 159.100.232.100

If you look that up you will see it is here:

Details for 159.100.232.100
IP: 159.100.232.100
Decimal: 2674190436
Hostname: 159.100.232.100
ASN: 202167
ISP: ZeniMax Online Studios
Organization: ZeniMax Online Studios
Services: None detected
Type: Corporate
Assignment: Likely Static IP
Blacklist:
Continent: North America
Country: United States us flag
Latitude: 37.751 (37° 45′ 3.60″ N)
Longitude: -97.822 (97° 49′ 19.20″ W)

Fourthly, there are users here who have stated just above your post that they get a better ping connected to the EU servers than the US servers and they live in the US, so you'll excuse me if I don't take your common sense as gospel.

What is obvious here is that my trace and your trace is routed via Germany to Maryland, and so the question remains, why? Why is my game executable communicating with Maryland as shown in the OP and not with Frankfurt. If we, in the EU are being routed via Frankfurt over to the US and back then it's clear this will add time to the package exchange and may be detrimental to overall performance.

Mathius_Mordred

ZOS_SarahHecker wrote: »

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

Thank you for replying, then can you please explain why our ESO64.exe are connected to Maryland?

Xarc

OP, Just tell me why when i'm loging on US megaserv my ping hurts my eyes ?

anitajoneb17_ESO

Mathius_Mordred wrote: »

ZOS_SarahHecker wrote: »

Just to confirm, we have not moved our EU megaservers and they are still located in Frankfurt.

Thank you for replying, then can you please explain why our ESO64.exe are connected to Maryland?

@code65536 already explained it.
The 159.100.232.100 IP is NOT physically in Maryland. It belongs to ZENIMAX, which is correctly registered as having its headquarters in Maryland. That's what the info you provided tells us.

So now where is this IP geographically, physically located ? To guess it, we need to follow its route. That's where the info provided by @code65536 comes in handy.
This route shows that the previous before last node (195.122.154.3 ) belongs to ZENIMAX Germany and the one before that to Deutsche Telekom. Which indicates that the server you're physically connected to (the 159.100.232.100 IP) is geographically located... in Germany.

ryzen_gamer_gal

Well, i'd like to know why i get better performance generally from EU server than i do from NA. i live in the dc area... and i assumed the better performance was from being close to the eu servers. now i wonder what could actually be the reason... Of course i have no idea what the ping here is for me or how to check it.

anitajoneb17_ESO

ryzen_gamer_gal wrote: »

Well, i'd like to know why i get better performance generally from EU server than i do from NA. i live in the dc area... and i assumed the better performance was from being close to the eu servers. now i wonder what could actually be the reason... Of course i have no idea what the ping here is for me or how to check it.

It may depend on your particular situation, location or ISP. We all use different routes.
It's also, I believe, a fact that the overall internet infrastructure is better in Europe than in the US (governemnt investment, higher density of population, etc. )

Darlon

Mathius_Mordred wrote: »

code65536 wrote: »

A little learning is a dangerous thing; drink deep, or taste not the Pierian spring: There shallow draughts intoxicate the brain, and drinking largely sobers us again.

@Mathius_Mordred This is a case of someone knowing just enough that they think they know what they're saying. But they don't know enough to know that they're wrong.

First, do you know where that location data comes from? There is no magical mechanism that lets you know where a server is located. The IP location lookup you used relies on information in a database. That information is supplied by whoever manages each block of IP addresses. The person supplying that information could say "North Pole" if they wanted. That doesn't mean that it's actually located at the North Pole.

Second, why would someone supply the "wrong" location for a block of IP addresses? Well, that's because IP addresses are not necessarily tied to any physical location. The data goes wherever the routers send it. Take, for example, my mobile phone. I get an IPv4 address from my carrier, and if I ask about the location of that address, it says that it's in Seattle. Even though I'm on the other side of the country. Because they had simply entered the location of their company headquarters in the database. Why would the mobile carrier do that? Maybe because it's easier to say, "all these addresses belong to us, and we are HQ'ed in Seattle" than to say, "this little block here we're currently using for customers in New York, and that block is being used in Miami, and that other block is New York too...". THIS IS ACTUALLY FAIRLY COMMON. The information in this database does not affect how the network runs--it's purely an administrative bookkeeping thing, and a lot of companies see no point in going into fine details like that when it serves absolutely no purpose.

It's pretty clear that the physical address seen in the whois database is just the Bethesda HQ.

Third, so how do you find where a server is located? The database that you queried is clearly the wrong approach. The right approach is the follow the packets themselves. You need to trace the route.

Tracing route to 159.100.232.100 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  172.16.64.1
  2     2 ms     1 ms     2 ms  10.26.1.219
  3     2 ms    12 ms    14 ms  23-255-225-139.mci.googlefiber.net [23.255.225.139]
  4     2 ms     2 ms     2 ms  192-119-18-184.mci.googlefiber.net [192.119.18.184]
  5     *        *        *     Request timed out.
  6    19 ms     8 ms     8 ms  23-255-225-180.mci.googlefiber.net [23.255.225.180]
  7     8 ms     8 ms     8 ms  ix-ae-60-0.tcore2.aeq-ashburn.as6453.net [216.6.87.88]
  8     9 ms     9 ms     9 ms  216.6.87.6
  9    99 ms   106 ms    99 ms  217.239.51.42
 10    99 ms    98 ms    98 ms  80.156.160.98
 11    99 ms    99 ms    99 ms  195.122.154.3
 12    99 ms    98 ms    99 ms  159.100.232.100

Look at hops #9, #10, and #11, right when the ping jumps up indicating a possible crossing of a large body of water and the last three stops right before hitting the destination. 217.239.51.42 and 80.156.160.98 are both registered to Deutsche Telekom, and 195.122.154.3 is registered to ZeniMax Germany GmbH. Sure looks like Germany to me, ja?

Finally, just common sense. I'm in the US. I see higher ping connecting to EU than to NA, even though I'm pretty close to Maryland.

TL;DR: STOP SPREADING FALSE INFORMATION If you're going to make threads like this, I suggest that you actually learn about the subject matter first.

First of all, who the hell are you to tell me what to do, especially when you seem to know nothing about the subject at all.
Secondly, I was asking about this apparent IP location which my ESO64.exe is actually connected to, I was spreading false information I am asking if this is the case?
Thirdly, in your example, you conveniently totally disregarded the last hop in your Tracrt which is: 159.100.232.100

If you look that up you will see it is here:

Details for 159.100.232.100
IP: 159.100.232.100
Decimal: 2674190436
Hostname: 159.100.232.100
ASN: 202167
ISP: ZeniMax Online Studios
Organization: ZeniMax Online Studios
Services: None detected
Type: Corporate
Assignment: Likely Static IP
Blacklist:
Continent: North America
Country: United States us flag
Latitude: 37.751 (37° 45′ 3.60″ N)
Longitude: -97.822 (97° 49′ 19.20″ W)

Fourthly, there are users here who have stated just above your post that they get a better ping connected to the EU servers than the US servers and they live in the US, so you'll excuse me if I don't take your common sense as gospel.

What is obvious here is that my trace and your trace is routed via Germany to Maryland, and so the question remains, why? Why is my game executable communicating with Maryland as shown in the OP and not with Frankfurt. If we, in the EU are being routed via Frankfurt over to the US and back then it's clear this will add time to the package exchange and may be detrimental to overall performance.

Stop using data from an administrative database instead of using actual trace data....

code65536

Mathius_Mordred wrote: »

First of all, who the hell are you to tell me what to do, especially when you seem to know nothing about the subject at all.

I am telling you that you are misinformed and that you do not understand where this information that you are citing actually comes form.

Mathius_Mordred wrote: »

Secondly, I was asking about this apparent IP location which my ESO64.exe is actually connected to, I was spreading false information I am asking if this is the case?

You did not present it as a question. But rather as an accusatory statement.

Mathius_Mordred wrote: »

Thirdly, in your example, you conveniently totally disregarded the last hop in your Tracrt which is: 159.100.232.100

So what you are suggesting to me is that this packet traveled across the Atlantic (+100ms ping), was routed through Deutsche Telekom's network in Germany, and then suddenly and inexplicably, it hopped back to the US without any intermediate routing steps and no further increases in ping. Your logic here is impeccable.

Second, you then post the same nonsense information about the address being located in NA. It's as if you didn't read at all what I wrote about that source of information. The only thing that you can take from that is that the final address belongs to ZeniMax. Stop. Proceed no further. Any address attached to that is purely administrative. All that we can say about the final four entries of the route trace is that it went through two routers registered to Deutsche Telekom AG, then to one registered to ZeniMax Germany GmbH, and then to one registered to ZeniMax Online Studios. That's it.

Mathius_Mordred wrote: »

Fourthly, there are users here who have stated just above your post that they get a better ping connected to the EU servers than the US servers and they live in the US, so you'll excuse me if I don't take your common sense as gospel.

You're not necessarily taking a beeline path to a location. For example, data to the NA server first gets passed to an Akamai anti-DDOS scrubbing center. So maybe your connection to the NA server might go from your ISP to another ISP to Akamai and then to a third ISP and then to ZOS--depending on the route taken, you data might zig-zag around the country before reaching the NA server. And if you happen to get a straightforward path to the EU server, then you could get similar or even lower ping despite the longer distance.

Mathius_Mordred wrote: »

Why is my game executable communicating with Maryland as shown

For the umpteenth time, IT IS NOT IN MARYLAND.

Mathius_Mordred

code65536 wrote: »

Mathius_Mordred wrote: »

First of all, who the hell are you to tell me what to do, especially when you seem to know nothing about the subject at all.

I am telling you that you are misinformed and that you do not understand where this information that you are citing actually comes form.

Mathius_Mordred wrote: »

Secondly, I was asking about this apparent IP location which my ESO64.exe is actually connected to, I was spreading false information I am asking if this is the case?

You did not present it as a question. But rather as an accusatory statement.

Mathius_Mordred wrote: »

Thirdly, in your example, you conveniently totally disregarded the last hop in your Tracrt which is: 159.100.232.100

So what you are suggesting to me is that this packet traveled across the Atlantic (+100ms ping), was routed through Deutsche Telekom's network in Germany, and then suddenly and inexplicably, it hopped back to the US without any intermediate routing steps and no further increases in ping. Your logic here is impeccable.

Second, you then post the same nonsense information about the address being located in NA. It's as if you didn't read at all what I wrote about that source of information. The only thing that you can take from that is that the final address belongs to ZeniMax. Stop. Proceed no further. Any address attached to that is purely administrative. All that we can say about the final four entries of the route trace is that it went through two routers registered to Deutsche Telekom AG, then to one registered to ZeniMax Germany GmbH, and then to one registered to ZeniMax Online Studios. That's it.

Mathius_Mordred wrote: »

Fourthly, there are users here who have stated just above your post that they get a better ping connected to the EU servers than the US servers and they live in the US, so you'll excuse me if I don't take your common sense as gospel.

You're not necessarily taking a beeline path to a location. For example, data to the NA server first gets passed to an Akamai anti-DDOS scrubbing center. So maybe your connection to the NA server might go from your ISP to another ISP to Akamai and then to a third ISP and then to ZOS--depending on the route taken, you data might zig-zag around the country before reaching the NA server. And if you happen to get a straightforward path to the EU server, then you could get similar or even lower ping despite the longer distance.

Mathius_Mordred wrote: »

Why is my game executable communicating with Maryland as shown

For the umpteenth time, IT IS NOT IN MARYLAND.

Ok, that's a better explanation. I was hoping that I had stumbled upon a reason some people get poor performance, seems not. So to answer that question it's over to ZOS.

WyndStryke

It's so frustrating how identical threads to this keep appearing despite having been correctly answered multiple times over the last few years. Don't people read or search?

ZOS_JesC

Greetings, since this thread has started to venture into baiting comments and personal insults, we've decided to close it.