NA/EU servers: Go get better quality servers

[Design]

C:\Users\Wyse>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=56ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=56ms TTL=51

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 56ms, Average = 55ms

C:\Users\Wyse>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 55ms, Average = 55ms

C:\Users\Wyse>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=54ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51
Reply from 184.107.107.176: bytes=32 time=54ms TTL=51
Reply from 184.107.107.176: bytes=32 time=55ms TTL=51

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 55ms, Average = 54ms

[Design]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Wyse>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 9 ms 10 ms 10.107.80.1
3 14 ms 11 ms 11 ms crr01ftwotx-tge-0-3-0-8.ftwo.tx.charter.com [96.
34.112.12]
4 11 ms 15 ms 15 ms bbr01dllstx-bue-2.dlls.tx.charter.com [96.34.2.3
2]
5 31 ms 10 ms 11 ms dls-bb1-link.telia.net [213.248.78.237]
6 8 ms 11 ms 10 ms ix-8-0.tcore1.DT8-Dallas.as6453.net [66.110.56.8
1]
7 57 ms 74 ms 60 ms 64.86.78.5
8 57 ms 85 ms 56 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
9 89 ms 59 ms 63 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
10 57 ms 57 ms 57 ms 66.198.96.58
11 64 ms 57 ms 57 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
12 63 ms 59 ms 58 ms 72.55.128.44
13 54 ms 56 ms 55 ms 184.107.107.176

Trace complete.

[Raist]

184.107.107.176 is not the IP your game client is connecting to... it's not even a game server. That is a web server. Ping this address, and click on the URL if you don't believe me

www.eidos.com

That IP is managed by a completely different group than the game servers, and in all likelihood resides in a different physical location. It ultimately takes a different path once it gets in/near Montreal. There are DNS records for a dozen or more websites that point to that IP.

If you wish to go through with investigating the QoS with the game client's connection, need to find the IP your client is actually connecting to and collect data for that IP. So far, reports show the servers in Canada begin with 199.

[Boretalith]

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.