Reporting Issues Resulting from the North American Data Center Relocation

[MliorFreyjr]

Type of Issue/Feedback: Consistent 90002's when doing instanced content, 90001 on the rare instance, and 3102 for upwards of 5-10 minutes. Any instanced content is rendered impossible to do.
Name of your Internet Service Provider (ISP): Comcast/XFinity
State/Country: Washington, USA
Date/Time: Since just before the 4.0 launch with the move of the servers to NTT. Typically on during the early hours of the morning of 1am-4am PST due to work.
World Name: Adamantoise.
Frequency: It has made it enough to where I'm unable to do instanced content on a near half hour basis. Log provided below of one night of gaming before I became frustrated and quit.

7/7/17: 11:36pm-11:42pm - Interruption w/o Reset or drop from modem. 90k2
7/8/17: 12:50am-12:52am - Interruption w/o Reset or drop from modem. 90k2
7/8/17: 1:08am-1:10am - Interruption w/o Reset or drop from modem. 90k2
7/8/17: 1:21am-1:26am - Interruption w/o Reset or drop from modem. 90k2
7/8/17: 1:30am-1:34am - Interruption w/o Reset or drop from modem. 90k2

Tracert for the server as listed below;

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 13 ms 15 ms 13 ms 96.120.60.97
3 15 ms 13 ms 13 ms xe-3-3-0-sur04.longview.wa.bverton.comcast.net [162.151.214.185]
4 14 ms 14 ms 13 ms ae-58-ar01.troutdale.or.bverton.comcast.net [68.87.216.193]
5 20 ms 18 ms 16 ms be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217]
6 30 ms 24 ms 28 ms hu-0-14-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.84.46]
7 20 ms 18 ms 18 ms ae-19.r04.sttlwa01.us.bb.gin.ntt.net [129.250.66.57]
8 16 ms 18 ms 18 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
9 30 ms 31 ms 31 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
10 38 ms 38 ms 48 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
11 35 ms 37 ms 38 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
12 36 ms 38 ms 38 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
13 * * 38 ms 204.2.229.234
14 36 ms 38 ms 38 ms 204.2.229.9

Trace complete.

Hop 13 often times has all three with *'s, but this was the only one I'm able to actually see a number on. It's inconsistent though... The * moves between all 3 requests.

Thanks for at least looking at this.. May just go ahead and pause the subscription until it's resolved because doing overworld content only is less than ideal and I'm burned out on doing only that now.

Edit:

So uh...I think I may have stumbled on something. Anyone else running into these issues, go into your adapter settings and disable IPv6, apply changes and reboot your computer. Once you do so, try to do instanced content.

I've either become incredibly lucky with it being functional again, or my network engineering paid off...

[Kyouki]

I noticed new lag spikes so i thought i should have another look at my connection. It was "ok" while being routed via amsterdam -> sacramento with ntt.net and only 16 hops. I am now routed via. amsterdam -> ashburn (VA) -> san jose -> sacramento using the ntt.net and back to 19 hops. 4 out of 6 ntt.net hops have packet loss. 204.2.229.234 still loses up to 20%, now 204.2.229.87 loses some packets too.

This is so annoying and i start to wonder why we even post here. Without ever getting any response. Even a "hey guys we are still looking into it and we are trying to make things better" would be enough to calm down a bit...

[drebbe]

Its pretty obvious they don't care about this issue, it doesn't take over two months to contact ntt.net and ask them to fix packet loss issues.

[Hareth]

Type of Issue/Feedback: (What type of issue are you encountering? Be as detailed as possible!) I am getting frequent lag and disconnects from the server. And now my route changed again and i'm getting constant high ms and loss of packets
Name of your Internet Service Provider (ISP): Edatel Telecomunicações
State/Country: Rio de Janeiro/Brazil
Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.) After NA data center relocation
World Name: Behemoth
Frequency: (How often does the issue occur?) Several times everyday

Traceroute records (optional)

Rastreando a rota para 204.2.229.105 com no máximo 30 saltos

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 3 ms 3 ms 10.27.243.78
3 * 9 ms 9 ms 187.95.46.41
4 12 ms 12 ms 12 ms 1.0.54.179.isp.timbrasil.com.br [179.54.0.1]
5 16 ms 15 ms 14 ms 10.220.16.21
6 14 ms 13 ms 14 ms 10.223.229.165
7 13 ms 14 ms 15 ms 10.223.238.38
8 13 ms 12 ms 13 ms et2-0-0.riodejaneiro5.rio.seabone.net [213.144.160.105]
9 * 24 ms 24 ms ae6.sanpaolo8.spa.seabone.net [195.22.219.3]
10 18 ms 18 ms 18 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.65]
11 133 ms 131 ms 130 ms ae-4.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.227]
12 200 ms 198 ms 198 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
13 198 ms 198 ms 198 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
14 * * * Esgotado o tempo limite do pedido.
15 271 ms 274 ms 271 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
16 271 ms 271 ms 271 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
17 * 270 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * * 269 ms 204.2.229.234
19 271 ms 270 ms * 204.2.229.105
20 270 ms 270 ms 271 ms 204.2.229.105

Rastreamento concluído.

[drebbe]

Okay so for those of you that can use linux and setup OpenVPN Linode's west VPS is about 5ms away from the SE's datacenter and doesn't route through majority of ntt.net's crappy hops.


from the VPS:

# ping 204.2.229.10
PING 204.2.229.10 (204.2.229.10) 56(84) bytes of data.
64 bytes from 204.2.229.10: icmp_seq=1 ttl=58 time=5.41 ms
64 bytes from 204.2.229.10: icmp_seq=2 ttl=58 time=5.42 ms
64 bytes from 204.2.229.10: icmp_seq=3 ttl=58 time=5.48 ms
64 bytes from 204.2.229.10: icmp_seq=4 ttl=58 time=5.38 ms
64 bytes from 204.2.229.10: icmp_seq=5 ttl=58 time=5.45 ms


with the VPN enabled:

C:\Users\drebbe>pathping 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

0 Blade [10.8.0.2]
1 10.8.0.1
2 23.92.24.3
3 173.230.159.12
4 192.80.16.1
5 ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
6 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
7 * 204.2.229.234
8 204.2.229.10

Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Blade [10.8.0.2]
0/ 100 = 0% |
1 67ms 0/ 100 = 0% 0/ 100 = 0% 10.8.0.1
0/ 100 = 0% |
2 67ms 0/ 100 = 0% 0/ 100 = 0% 23.92.24.3
0/ 100 = 0% |
3 67ms 0/ 100 = 0% 0/ 100 = 0% 173.230.159.12
0/ 100 = 0% |
4 69ms 0/ 100 = 0% 0/ 100 = 0% 192.80.16.1
0/ 100 = 0% |
5 72ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
0/ 100 = 0% |
6 73ms 0/ 100 = 0% 0/ 100 = 0% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
0/ 100 = 0% |
7 72ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.234
0/ 100 = 0% |
8 72ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.10

Trace complete.


and a ping through the VPN:

C:\Users\drebbe>ping 204.2.229.10

Pinging 204.2.229.10 with 32 bytes of data:
Reply from 204.2.229.10: bytes=32 time=73ms TTL=57
Reply from 204.2.229.10: bytes=32 time=77ms TTL=57
Reply from 204.2.229.10: bytes=32 time=72ms TTL=57
Reply from 204.2.229.10: bytes=32 time=72ms TTL=57

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


This reduces latency by 30-50ms and eliminates packet loss.

[ShaelK]

-I am getting disconnected constantly from play, Error 90002 every time. The other player at my home has no such issue, and has not been disconnected at the same time as me
-ISP is Cox
-California
-It's been especially severe over the last few days
-Ultros
-It happens at least every hour, sometimes as often as every 20 minutes
-TraceRT:

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 24 ms 25 ms 27 ms 10.76.224.1
2 33 ms 24 ms 30 ms ip68-4-14-46.oc.oc.cox.net [68.4.14.46]
3 25 ms 33 ms 39 ms ip68-4-11-58.oc.oc.cox.net [68.4.11.58]
4 36 ms 27 ms 31 ms 68.1.1.167
5 329 ms 180 ms 28 ms ae-7.r00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
6 51 ms 57 ms 65 ms ae-6.r22.lsanca07.us.bb.gin.ntt.net [129.250.6.46]
7 32 ms 27 ms * ae-1.r23.lsanca07.us.bb.gin.ntt.net [129.250.2.207]
8 30 ms 39 ms 63 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
9 46 ms 46 ms 51 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
10 41 ms 41 ms 123 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
11 46 ms 52 ms 50 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
12 46 ms * 47 ms 204.2.229.234
13 47 ms 30 ms 27 ms 204.2.229.10

Trace complete.

I had a Chat Support session with "Erick," and all he told me to do is call my ISP and set up Port Forwarding. What a joke.

[Tristanum]

Type of Issue/Feedback: (What type of issue are you encountering? Be as detailed as possible!) I am getting insane lag and disconnects (900002) from the server.
Name of your Internet Service Provider (ISP): Virtua
State/Country: SP/Brazil
Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.) After 4.01 Patch
World Name: Behemoth
Frequency: (How often does the issue occur?) At any roullete, dungeon, world map, quests and etc

C:\WINDOWS\system32>tracert 204.2.229.105

Tracing route to 204.2.229.105 over a maximum of 30 hops

1 1 ms 2 ms 2 ms 192.168.0.1
2 37 ms 29 ms 27 ms bacc3801.virtua.com.br [186.204.56.1]
3 14 ms 10 ms 13 ms c9062341.virtua.com.br [201.6.35.65]
4 11 ms 10 ms 11 ms c9062871.virtua.com.br [201.6.40.113]
5 12 ms 12 ms 13 ms c9062841.virtua.com.br [201.6.40.65]
6 12 ms 15 ms 13 ms embratel-T0-1-0-1-uacc01.spo.embratel.net.br [201.56.239.21]
7 20 ms 21 ms 21 ms ebt-H0-9-0-0-tcore01.spoph.embratel.net.br [200.244.216.125]
8 123 ms 127 ms 127 ms ebt-BP1082-intl02.nyk.embratel.net.br [200.230.220.30]
9 123 ms 125 ms 126 ms ce-0-10-0-2.r08.nycmny01.us.bb.gin.ntt.net [129.250.202.185]
10 126 ms 129 ms 129 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
11 189 ms 187 ms 186 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
12 200 ms 198 ms 195 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
13 214 ms 215 ms 216 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
14 211 ms 209 ms 212 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
15 205 ms 208 ms 207 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
16 209 ms 212 ms 212 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
17 212 ms 211 ms 218 ms 204.2.229.234
18 215 ms 216 ms 218 ms 204.2.229.105

[drebbe]

and more lag from ntt.net

C:\Users\drebbe>pathping 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

0 Blade [10.8.0.2]
1 10.8.0.1
2 23.92.24.3
3 173.230.159.12
4 192.80.16.1
5 ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
6 * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
7 * * 204.2.229.234
8 * 204.2.229.10

Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Blade [10.8.0.2]
0/ 100 = 0% |
1 66ms 0/ 100 = 0% 0/ 100 = 0% 10.8.0.1
0/ 100 = 0% |
2 67ms 0/ 100 = 0% 0/ 100 = 0% 23.92.24.3
0/ 100 = 0% |
3 66ms 0/ 100 = 0% 0/ 100 = 0% 173.230.159.12
0/ 100 = 0% |
4 68ms 0/ 100 = 0% 0/ 100 = 0% 192.80.16.1
20/ 100 = 20% |
5 106ms 25/ 100 = 25% 5/ 100 = 5% ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
0/ 100 = 0% |
6 107ms 26/ 100 = 26% 6/ 100 = 6% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
0/ 100 = 0% |
7 105ms 20/ 100 = 20% 0/ 100 = 0% 204.2.229.234
8/ 100 = 8% |
8 106ms 28/ 100 = 28% 0/ 100 = 0% 204.2.229.10

[Kyouki]

We have been more than patient Square Enix. It is only getting worse with every week that passes by.

Now my connection is up to 350+ms with a packet loss up to 50%.

DO SOMETHING!

1 <1 ms <1 ms <1 ms EUPHORIA [192.168.1.1]
2 * * * Zeitüberschreitung der Anforderung.
3 9 ms 8 ms 8 ms ip5886ba66.dynamic.kabel-deutschland.de [88.134.186.102]
4 12 ms 11 ms 18 ms ip5886bb00.dynamic.kabel-deutschland.de [88.134.187.0]
5 14 ms 13 ms 19 ms ip5886ebf8.static.kabel-deutschland.de [88.134.235.248]
6 17 ms 16 ms 15 ms ip5886ebd7.static.kabel-deutschland.de [88.134.235.215]
7 14 ms 13 ms 26 ms ae8-100-xcr1.hac.cw.net [195.10.62.5]
8 18 ms 19 ms 20 ms ae5-xcr1.ham.cw.net [195.2.24.181]
9 26 ms 18 ms 19 ms ae4-xcr2.amd.cw.net [195.2.9.38]
10 19 ms 19 ms 26 ms ae1-xcr1.att.cw.net [195.2.30.202]
11 23 ms 25 ms 25 ms as2914-gw-att.cw.net [195.2.2.58]
12 30 ms 27 ms 25 ms ae-7.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.158]
13 103 ms 102 ms 98 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 * 160 ms * ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 * * 665 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 * * * Zeitüberschreitung der Anforderung.
17 * 362 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 358 ms * * 204.2.229.234
19 358 ms * * 204.2.229.87
20 * * * Zeitüberschreitung der Anforderung.
21 355 ms 355 ms 361 ms 204.2.229.87

[Phaedris]

Getting high latency as well

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 24 ms 17 ms 18 ms 108-77-172-1.lightspeed.jcvlfl.sbcglobal.net [10
8.77.172.1]
3 35 ms 19 ms 20 ms 99.166.205.22
4 21 ms 18 ms 18 ms 99.132.13.26
5 18 ms 19 ms 19 ms 99.132.13.95
6 20 ms 19 ms 19 ms 12.83.101.9
7 34 ms 34 ms 36 ms 12.122.117.121
8 33 ms 34 ms 50 ms 192.205.36.158
9 * 738 ms * ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.
57]
10 33 ms 34 ms 34 ms ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.2
11]
11 49 ms 49 ms 56 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.1
16]
12 89 ms 89 ms 89 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.1
54]
13 305 ms 319 ms 327 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.
119]
14 761 ms 744 ms 754 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
3]
15 770 ms 752 ms 715 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
16 * * 699 ms 204.2.229.234
17 729 ms * 727 ms 204.2.229.10

Trace complete.