Regarding Reports on Recent Connection Problems with the NA Data Center

[Inbachi]

The fact that this is still an issue and that SE still refuse to address it is beyond acceptable. We, the users, have gone above and beyond to spell out exactly what the issue is and SE apparently refuses to take action. The circular non-answers from the mods here have done nothing for months; we've all read/heard/experienced how terrible the customer support is for this game and this whole issue is yet another testament to that.

We need to start leaving 1 star reviews anywhere and everywhere we can. Don't re-sub and be sure to let people know the reason why. Tell others not to sub, let them know not to waste their money on a company that doesn't care about their player base. Start threads on Reddit/Steam/Facebook/etc. Apparently the only way this is actually going to be fixed is to raise a huge stink. It's absolutely ridiculous that it's come to this.

[Aggomarr]

Reading this thread has just discouraged me greatly. I have been having sever connection issues about 2 or 3 weeks after I started subbing, and it's very aggravating. Getting booted from the game every 30 mins - 1 hour is incredibly annoying and frustrating. I can't even hope to try and get the PotD achievements due to getting the 90002 and 90001 error constantly, losing all of my progress and being forced to start over because of the "no Party KO" restriction beyond 100. This is incredibly demoralizing when I have spent 30-40 mins to get immediately kicked off just a few more hits before the boss goes down. There isn't even a warning either. No lag, no hiccups, no rubber banding. Everything is going as smoothly as it is the entire time, and then suddenly, bam. Kicked off. It's not as bad in parties, because sometimes, it lets me rejoin the group I was in, other times it completely kicks me out back to Quarrymill and I lose everything. Seeing that this issue has been going on this long and still no concrete solution just makes me disappointed in SE. I have played many free-to-play MMOs that have more stable servers than this as a subbed game. How sad.

If you can't fix your server problems, at least let our dungeon instances remain open for 5~ mins or so after we've been disconnected. As a soloist, this problem is extremely crippling when it takes me several tries to complete a dungeon or instance because 90001 and 90002 completely forfeiting all of my progress.

[Riko_Futatabi]

I still get error 90006 even when trying a different route with a VPN. The route has no packet loss, but I'm noticing I still get these sharp spikes of ping going up to 3000ms that's causing my lag and disconnects.

In fact the only packet loss I'm noticing now is on SE lobby server.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            10.254.244.1 -    0 |  128 |  128 |    0 |    0 |    0 |    0 |
|                            10.253.160.1 -    0 |  128 |  128 |  146 |  151 |  189 |  156 |
|                          10.255.243.186 -    0 |  128 |  128 |  146 |  151 |  191 |  164 |
|                         107.170.248.254 -    0 |  128 |  128 |  146 |  153 |  195 |  147 |
|                         138.197.248.210 -    0 |  128 |  128 |  146 |  153 |  198 |  150 |
|ae-13.sayonara-sam.r06.plalca01.us.bb.gin.ntt.net -    0 |  128 |  128 |  148 |  153 |  193 |  160 |
|ae-15.sayonara-sam.r02.snjsca04.us.bb.gin.ntt.net -    0 |  128 |  128 |  151 |  156 |  200 |  154 |
|ae-3.sayonara-sam.r00.scrmca02.us.bb.gin.ntt.net -    0 |  128 |  128 |  152 |  158 |  190 |  155 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    0 |  128 |  128 |  152 |  159 |  306 |  157 |
|                           204.2.229.234 -    5 |  110 |  105 |  151 |  156 |  175 |  158 |
|                            204.2.229.10 -    0 |  128 |  128 |  151 |  158 |  191 |  159 |
|________________________________________________|______|______|______|______|______|______|

Your lobby server is ranging from 5%~20% packet loss. As of 19:00 GMT / 11:00 PST on Saturday.

[ZodiarkE]

All I am getting from the patch file update failure due to as follows after I corrected the corruption data: [11006][20819][20831][-2147352571] <----I looked this up and its nothing but a run around of issues relating the isp, router, everything most of us already tried and failed, I still believe this has a lot to do with the update patch note itself, sony has issues with their firmware update 5.50 and what I see is going on is that the firmware caused a corruption to the ps4 save data which goes into a loop of safe mode where it cannot update at all, due to this caused several issues to happen: corrupted data to the game which conflicted to the save data on the application or save data for the ffxiv, alas what I believe further caused it to get worse is that the error I got kept on going, I just hope there will be a firmware update for the ps4 and hope that patch note for the launcher comes so that way it can fix both issues and hopefully most of us can get back on ffxiv before our own houses get demolished, otherwise I will be very upset if I lose both houses =(

[Riko_Futatabi]

Again, after 19:00 GMT / 11:00 PST (Sunday this time) the packet loss on the lobby server seems to increase significantly. Just thought I'd let you know~

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            10.254.103.1 -    0 |  126 |  126 |    0 |    0 |    0 |    0 |
|                            10.247.112.1 -    0 |  126 |  126 |  154 |  160 |  187 |  155 |
|                          10.255.243.206 -    0 |  126 |  126 |  154 |  161 |  188 |  170 |
|                           138.68.40.253 -    0 |  126 |  126 |  155 |  162 |  185 |  175 |
|                         138.197.249.150 -    0 |  126 |  126 |  155 |  161 |  187 |  165 |
|                         138.197.249.166 -    0 |  126 |  126 |  157 |  166 |  226 |  164 |
|ae-13.sayonara-sam.r05.plalca01.us.bb.gin.ntt.net -    0 |  126 |  126 |  157 |  165 |  187 |  168 |
|ae-15.sayonara-sam.r01.snjsca04.us.bb.gin.ntt.net -    0 |  126 |  126 |  162 |  170 |  190 |  165 |
|ae-4.sayonara-sam.r00.scrmca02.us.bb.gin.ntt.net -    0 |  126 |  126 |  162 |  170 |  191 |  167 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    0 |  126 |  126 |  162 |  169 |  196 |  178 |
|                           204.2.229.234 -   17 |   77 |   64 |    0 |  168 |  183 |  163 |
|                            204.2.229.10 -    0 |  126 |  126 |  163 |  169 |  188 |  163 |
|________________________________________________|______|______|______|______|______|______|

[Riko_Futatabi]

I've tried many different routes to the Primal Data Center. Some had packet loss along the way, some were immaculate, like this one. However, the only constant packet loss throughout all the different routes I tried is 204.2.229.234. Yes, the lobby server.

Probably the longest I've monitored a route, just to make sure. This was around 21:30 GMT / 13:30 PST on Sunday.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            10.254.103.1 -    0 | 1001 | 1001 |    0 |    0 |    1 |    0 |
|                            10.247.112.1 -    0 | 1001 | 1001 |  154 |  158 |  184 |  156 |
|                          10.255.243.206 -    0 | 1001 | 1001 |  153 |  158 |  183 |  154 |
|                           138.68.40.253 -    0 | 1001 | 1001 |  154 |  159 |  195 |  159 |
|                         138.197.249.150 -    0 | 1001 | 1001 |  154 |  158 |  176 |  160 |
|                         138.197.249.166 -    0 | 1001 | 1001 |  156 |  161 |  210 |  159 |
|    ae-13.r05.plalca01.us.bb.gin.ntt.net -    0 | 1001 | 1001 |  157 |  161 |  179 |  165 |
|    ae-15.r01.snjsca04.us.bb.gin.ntt.net -    0 | 1001 | 1001 |  162 |  166 |  188 |  163 |
|     ae-4.r00.scrmca02.us.bb.gin.ntt.net -    0 | 1001 | 1001 |  162 |  166 |  185 |  163 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    0 | 1001 | 1001 |  161 |  165 |  201 |  165 |
|                           204.2.229.234 -   19 |  575 |  467 |  162 |  166 |  189 |  169 |
|                            204.2.229.10 -    0 | 1001 | 1001 |  162 |  166 |  405 |  168 |
|________________________________________________|______|______|______|______|______|______|

It's clear to me that the lobby server can't handle all this traffic at peak times. Not sure what you can do about it to be honest. ¯\_(ツ)_/¯

[Mesarthim]

The only solution I've found this problem is to spend more (of my) money and get a proper VPN to route around NTT's terrible service while they continue to not admit there's a problem. Even then there's a slight chance that the VPN is still subject to the severe packet loss as one day it was less laggy after I turned it off. I monitor my connection all day that I am on my PC for and every day NTT lags out at random intervals for random durations (random 100-130 latency added + packet loss).

It's only a matter of time until Square's next non-helpful answer. Though them keeping silent will probably just end with the same result.

I shouldn't need a VPN to route around their problems yet I'm basically forced to at some points each day.

[Plastic_Fork]

My roommate and I have been having this same issue ongoing for weeks/months now where we live. Usually happens around 7pm CST or 8pm CST and lasts anywhere from 30 minutes to an hour or two. This past week, it's been multiple times a day instead of just the same time every night. Our connection to the Primal datacenter (Exodus server) is great until the hops hit San Jose, CA. It's the same location in our path every time that the latency starts to really shoot up every night for random periods of time. Makes any kind of raiding or the new Eureka zone impossible to play with my latency 200ms+ when this happens.

ISP: Comcast
Speed: 125mbit down / 30mbit up
Platform: PC

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2    11 ms    10 ms    25 ms  96.120.53.45
  3    12 ms    10 ms    11 ms  68.86.151.25
  4    12 ms    10 ms    11 ms  162.151.9.86
  5    17 ms    16 ms    16 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  6    22 ms    23 ms    25 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  7    22 ms    24 ms    22 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  8    24 ms    28 ms    23 ms  50.242.151.58
  9    24 ms    24 ms    23 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
 10    22 ms    22 ms    23 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 11    41 ms    44 ms    39 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 12   199 ms   203 ms   207 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 13   201 ms     *      207 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 14   202 ms   204 ms   201 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 15   199 ms   197 ms   200 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16     *      208 ms     *     204.2.229.234
 17   205 ms   209 ms   202 ms  204.2.229.96

Trace complete.

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1     1 ms     1 ms    <1 ms  192.168.0.1
  2    10 ms     9 ms     9 ms  96.120.53.45
  3    11 ms    12 ms    11 ms  68.86.151.25
  4    10 ms    26 ms    13 ms  162.151.9.86
  5    15 ms    16 ms    15 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  6    23 ms    24 ms    22 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  7    22 ms    22 ms    23 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  8    23 ms    43 ms    28 ms  50.242.151.58
  9    27 ms    23 ms    31 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
 10    23 ms    24 ms    22 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 11    47 ms    44 ms    40 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 12   192 ms   200 ms   201 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 13     *        *      214 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 14   206 ms     *      205 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 15     *        *      200 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16     *      203 ms   203 ms  204.2.229.234
 17     *      204 ms   202 ms  204.2.229.96

Trace complete.

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    10 ms     9 ms    11 ms  96.120.53.45
  3    11 ms    12 ms    12 ms  68.86.151.25
  4    12 ms    12 ms    11 ms  162.151.9.86
  5    31 ms    23 ms    21 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  6    25 ms    32 ms    23 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  7    22 ms    22 ms    21 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  8    21 ms    29 ms    22 ms  50.242.151.58
  9    41 ms    29 ms    30 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
 10    37 ms    41 ms    28 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 11    49 ms    46 ms    44 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 12     *        *        *     Request timed out.
 13   206 ms   202 ms   196 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 14   204 ms   205 ms   206 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 15   209 ms     *      203 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16   208 ms     *      205 ms  204.2.229.234
 17   211 ms   204 ms   202 ms  204.2.229.96

Trace complete.

[gumas]

I stop playing this game 4 months ago because i got fed up with 90002 error (sudden dc for no reason), tody i subs again to check hows the condition and what do you know...

1 hour into the game and i got booted with 90002 error... and so i unsubs again lol

I will keep cheering for you guys because i already give up at this point, i try everything and all i got is a dull message from moderator who keep repeating himself.

[Callinon]

I stop playing this game 4 months ago because i got fed up with 90002 error (sudden dc for no reason), tody i subs again to check hows the condition and what do you know...

1 hour into the game and i got booted with 90002 error... and so i unsubs again lol

I will keep cheering for you guys because i already give up at this point, i try everything and all i got is a dull message from moderator who keep repeating himself.

Keep a free trial account around to test for that. That's what I did, I spent about 6 months in 90002 hell too. Then one day I checked it with my trial account and everything was ok.

Well and then the evening lag that makes the game unplayable happened, but that's at least a different problem.