Reporting Issues Resulting from the North American Data Center Relocation

[Kushal]

Type of Issue/Feedback: Constantly disconnect from the game after a couple minutes of play. (90002 error code)
Name of your Internet Service Provider (ISP): VIVO (Telefônica Brasil)
State/Country: Paraná / Brasil
Date/Time: Started July 05, 2017- Entire time
World Name: Behemoth
Frequency: Entire time
(Impossible to do Sastasha)

[Heith]

Type of Issue/Feedback: Constantly disconnect from the game after a couple minutes of play. (90002 error code)
Name of your Internet Service Provider (ISP): Vodafone/ Telefónica
State/Country: Granada / Spain
Date/Time: Started July 04, 2017- Entire time
World Name: Balmung
Frequency: Entire time

[Arkhana]

Type of Issue/Feedback : Getting error 90002
Name of your Internet Service Provider (ISP): Free
State/Country : France
Date/Time : The issue started happening on July 4th in the evening (GMT)
World Name : Sargatanas
Frequency: Everytime I teleport somewhere, everytime I arrive at the top of the first elevator in Omega solo instance, and every minute in the World.

This is unplayable at the moment. I expect a commercial gesture for the days people haven't been able to play but knowing Square Enix it probably won't happen...

[Mature]

World : Ultros
Error : 90002
Country : UK
ISP: SKY UK
Frequency : since implementation of Omega
Time : usually around 19:30 BST

[Catas]

Type of Issue/Feedback: Massive Lag Spikes
Name of your Internet Service Provider (ISP): Spectrum (Time Warner)
State/Country: New York/United States
Date/Time: This started a few weeks ago
World Name: Excalibur
Frequency: Every 30-60 seconds
Traceroute records: Tracert Record

This game is becoming unplayable. Specifically in Duty Finder.

[JaoP96]

Type of Issue/Feedback: big latency issues/disconnects/not able to login
Name of your Internet Service Provider (ISP): ForNet Telecom
State/Country: Paraná / Brazil
Date/Time: Since July 3th/ Can happen at any given time but more often after 6PM-UTC
World Name: Exodus
Frequency: Most of the time.

[eschaton]

Any updates on this? Even a VPN seems to get laggy/dodgy at main peak times, not as bad as without one (dc's), but still. And it's really only with this game, since after the NA DC move. It's really weird! And everyone moving to California isn't a option right? No really any new information on this would be great.

[vensus]

Haven't been having 90k errors for about a week now but still seems to be random packet loss issues at hand, doesn't seem to matter what time of the day it's just randomly and lasts anywhere from 15-40mins before looking stable for an hour or so before it acts up a bit. It's looking like it's issues with the hops later down the route on nnt's host

[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...