Square, your NA/EU data centre has serious issues...

[blackbluesky]

It does seem like Cogent may be SE's servers ISP. In which case this will definitely be worked out soon. We shouldn't be surprised really, MMORPGs haven't been handling their own CDS's for some time now.

[Raist]

Appleh4x isn't even testing the proper IP:

Ok, so did the traceroute just now after being unable to login as usual in the daytime, still shows nothing. Game issue.
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 35 ms 28 ms 38 ms 67.191.164.1
3 10 ms 11 ms 9 ms xe-10-0-0-32767-sur01.w1monroe.ga.atlanta.comcast.net [68.85.172.141]
4 12 ms 11 ms 11 ms 68.86.107.105
5 31 ms 31 ms 33 ms he-5-12-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.93.125]
6 33 ms 35 ms 31 ms pos-0-4-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.138]
7 47 ms 44 ms 45 ms ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net [209.58.44.1]
8 47 ms 47 ms 47 ms if-25-2.tcore1.AEQ-Ashburn.as6453.net [64.86.113.2]
9 * 46 ms 47 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
10 * * 78 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.138]
11 46 ms 50 ms 47 ms if-4-4.tcore2.NYY-NewYork.as6453.net [66.198.111.18]
12 51 ms 51 ms 51 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
13 57 ms 47 ms 54 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
14 48 ms 47 ms 50 ms 64.86.31.42
15 49 ms 47 ms 47 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
16 47 ms 47 ms 47 ms 72.55.128.44
17 48 ms 49 ms 47 ms 184.107.107.176

Trace complete.

So.. have to take that into consideration also.

By the way... that is a WEBSERVER, not the GAMESERVER that FFXIV is struggling to communicate with while you are playing.

It's not only the wrong subnet, but the wrong company managing the IP, as well as the wrong physical location.
http://myip.ms/info/whois/184.107.107.176
http://myip.ms/browse/sites/1/ipID/1...84.107.107.176
(list of sites with dns records for that IP)

[Raist]

This is odd:

8 38 ms 41 ms 37 ms eidos-vpn.gigabitethernet3-39.ar4.lon3.gblx.net [64.213.77.134] - This is an authentication check hop on the Square side, but why through a VPN?
9 * * * Request timed out. - I wonder if it times out because the check failed or the SSH crashed midway

13 118 ms 118 ms 122 ms te0-1-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.26.141]
14 125 ms 125 ms 125 ms 38.122.42.34
15 * * * Request timed out. - This is on the Square side. Maybe a route table error?
16 113 ms 113 ms 113 ms 192.34.76.2
17 110 ms 110 ms 110 ms 199.91.189.234
18 113 ms 113 ms 110 ms 199.91.189.28

The EU hops are much more direct and the drops there may be influenced by passing through the VPN for authentication. Are you using a VPN? Is there anyway you can get away from that? That's definitely host side. Save that trace and send it to Square with a ticket.

The NA hops you have a ton of. The longer the route, the less stable the connection becomes. Notice that your latency doubles between hop 12 and hop 13 (Same city, just different hub) That's influencing the drop on hop 15. It may not be the catalyst, but it's definitely not helping.

Should be noted that the 209 IP is NOT a game server---that is the EU website for Square-Enix. IDK where those IP's came from, but they are NOT the right ones to use. All three of those being pushed as the "data centers" are actually web servers--one of them is the old www.eidos.com IP and has A records for their games assigned to it.

Need to focus on the 199 IP's---those are the game servers.

[Appleh4x]

Appleh4x isn't even testing the proper IP:



So.. have to take that into consideration also.

By the way... that is a WEBSERVER, not the GAMESERVER that FFXIV is struggling to communicate with while you are playing.

It's not only the wrong subnet, but the wrong company managing the IP, as well as the wrong physical location.
http://myip.ms/info/whois/184.107.107.176
http://myip.ms/browse/sites/1/ipID/1...84.107.107.176
(list of sites with dns records for that IP)

It's an address at the same location as the game server, so it goes through the same hops.

[Marishi-Ten]

Should be noted that the 209 IP is NOT a game server---that is the EU website for Square-Enix. IDK where those IP's came from, but they are NOT the right ones to use. All three of those being pushed as the "data centers" are actually web servers--one of them is the old www.eidos.com IP and has A records for their games assigned to it.

Need to focus on the 199 IP's---those are the game servers.

Ah, I didn't catch that. My bad! That would explain the vpn passthrough and the check fail.

[Appleh4x]

Marishi your counter argument to my direct response from SE themselves is that they are lying about having congested servers? They would keep their mouths shut before directly lying to someone.

[blackbluesky]

It's an address at the same location as the game server, so it goes through the same hops.

Not necessarily.

[Shizue]

I'd recommend using a tool like winMTR to track issues like packet loss and latency over time. A single tracert is not as useful.

Packet loss confirmed via winMTR

[Raist]

It's an address at the same location as the game server, so it goes through the same hops.

Nope... wrong again. Research them. The one you are using is an i-Web IP. The registered address is roughly 16 blocks away from the one registered to my game server's IP. You will likely see them take slightly different paths once you get into Canada (if not sooner).

Edit:

Tracing route to 199.91.189.74 over a maximum of 30 hops

<initial hops removed>
4 27 ms 34 ms 24 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
5 31 ms 30 ms 63 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
6 29 ms 30 ms 27 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 80 ms 79 ms 81 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 81 ms 80 ms 77 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.165]
9 85 ms 93 ms 100 ms te0-3-0-2.ccr21.dca01.atlas.cogentco.com [154.54.2.46]
10 99 ms 94 ms 95 ms te0-7-0-14.mpd21.jfk02.atlas.cogentco.com [154.54.41.22]
11 131 ms 113 ms 114 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
12 70 ms 69 ms 68 ms 38.122.42.34
13 69 ms 77 ms 69 ms 10.2.2.1
14 70 ms 82 ms 68 ms 192.34.76.2
15 71 ms 71 ms 71 ms 199.91.189.234
16 69 ms 69 ms 68 ms 199.91.189.74

Trace complete.

Tracing route to www.eidos.com [184.107.107.176]
over a maximum of 30 hops:

<initial hops removed>
4 25 ms 34 ms 43 ms ge-3-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.62]
5 28 ms 30 ms 31 ms bu-ether44.atlngamq46w-bcr00.tbone.rr.com [107.14.19.46]
6 39 ms 33 ms 28 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 80 ms 81 ms 77 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 79 ms 78 ms 91 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
9 89 ms 91 ms 94 ms te0-1-0-6.ccr21.dca01.atlas.cogentco.com [154.54.24.153]
10 97 ms 96 ms 105 ms te0-2-0-2.ccr21.jfk02.atlas.cogentco.com [154.54.26.186]
11 115 ms 123 ms 113 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
12 68 ms 69 ms 69 ms 38.122.42.122
13 72 ms 69 ms 69 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
14 69 ms 69 ms 69 ms 72.55.128.44
15 90 ms 71 ms 69 ms 184.107.107.176

Trace complete.

The website's trace took off into i-Web's space at hop 13, while the game server went to a reserved IANA IP (private).
http://myip.ms/info/whois/67.205.127.214
http://myip.ms/info/whois/10.2.2.1

[Appleh4x]

BTW the range of IPs currently suffering lower QOS has changed in the last two days which is why so many more forum topics are being made about it. My QOS is fine now, not to say that after the next maintenance it won't go back to 90k and lag.