Regarding Reports on Recent Connection Problems with the NA Data Center

[Gilaverde]

Connection problems have affected my live stream tonight on Twitch. I have been inundated with 90Ks and 3Ks tonight. You guys need to lift, Square. If you need to deliver a hotfix and put the servers on maintenance do it now and do it quick.

This has been happening for the last 4 weeks.

I cannot run duty runs in fear of disconnect, getting removed from runs. Cannot do dailies in fear of disconnect while attempting to complete. Cannot do any FC runs because of fear they will not have patience for my disconnects happening.
I'm trying crafting now but now I fear of crafting and disconnect while attempting to complete a craft. Even loading this page / site takes long to load.

I fear disconnects while playing FFXIV.

[Kyp]

This has been happening for the last 4 weeks.

I cannot run duty runs in fear of disconnect, getting removed from runs. Cannot do dailies in fear of disconnect while attempting to complete. Cannot do any FC runs because of fear they will not have patience for my disconnects happening.
I'm trying crafting now but now I fear of crafting and disconnect while attempting to complete a craft. Even loading this page / site takes long to load.

I fear disconnects while playing FFXIV.

The fear is real, I just moved to a play where Cox has monopoly, so I have no other options. I 90ked while loading into an instance, and now my character is stuck logged in the game, I 90k trying to load into him.

[Gilaverde]

The fear is real, I just moved to a play where Cox has monopoly, so I have no other options. I 90ked while loading into an instance, and now my character is stuck logged in the game, I 90k trying to load into him.

Its not Cox IMO. SE made some changes back in Nov 2017 and refuses now to change it back. Its never been this bad. After the 4.1 update, the disconnects started.

Edit: after 4.15 update did the problems start.

[XenoCranel]

I've been experiencing connection issues, lag spikes that would delay game play for 1-10 seconds. 90ked once. Issue seems to only be present with ff14. Located in California. Also, Cox. The only internet monopoly in my area.

[MidnightWonko]

Cox ISP, this has been ongoing for WEEKS, if not MONTHS!

[Riko_Futatabi]

Its not Cox IMO. SE made some changes back in Nov 2017 and refuses now to change it back. Its never been this bad. After the 4.1 update, the disconnects started.

Edit: after 4.15 update did the problems start.

I'm not surprised if you are right. I'm not with Cox ISP though, I'm with Sky and ever since the 4.06a patch in September 2017 I have had a terrible connection and no troubleshooting has helped. I've tried absolutely everything SE and my ISP has suggested...it's never changed. 4 months of this awful connection, getting ready to give up and play something else, this game isn't worth paying for in this state.

[Chortle]

The Southwest states are the unfortunate ones it seems. We all are being routed through a hop that gets overloaded during our peak play times of 6pm - 11pm (when everyone is off work). Packet loss and disconnects ensue. It's nice to know that SE is looking into the issue, but for an online game we continue to pay for via subscriptions, this does not bode well.

I love Final Fantasy, and I love this game. I hope this gets resolved quickly.

[Callinon]

More d/cs tonight. One accompanied by what looked like a server hiccup (but no corresponding latency spike) and one just for no particular reason at all (no latency, no server delays). Both of these were 90002s. Fortunately they happened before and after I main tanked an alliance roulette... that's a fun way to cause random problems.

And when I've set up 2 FF14s running on my PC, one using the keyboard, the other using a controller, either my account or my friends account would be DCed, but not the other.
(Remember, same computer, just 2 different accounts. And which one gets DCed is random.)

That's interesting. I remember reading once that FFXIV is SUPER twitchy about any kind of CPU misfiring (in some weird effort to prevent movement hacks I guess.... the flying RMT BLM bots would suggest it doesn't work). I could see running two clients side by side like that causing some issues if one of them missed its timing a couple times even if it didn't necessarily affect the other one.

[blackplaguee]

Been having the same issues the last week or so. Spikes of 600-1000 in instance but not in the world. Just got blm to 70 but can't keep Enochian up or get out of mechanics because of lag. I just drop party. I been running test with my ISP and my PC trace route etc. I keep coming back to FFxiv as the problem.

[Callinon]

MOAR DATA

C:\Users\Jon>pathping 204.2.229.97

Tracing route to 204.2.229.97 over a maximum of 30 hops

  0  Lapis [192.168.1.54]
  1  RT-AC68U-5570 [192.168.1.1]
  2  96.120.28.53
  3  te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
  4  68.85.183.142
  5  be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
  6  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
  7  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  8  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  9  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 10  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 11  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 12     *        *     ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 13  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 14  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 15  204.2.229.242
 16  204.2.229.97

Computing statistics for 400 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Lapis [192.168.1.54]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  RT-AC68U-5570 [192.168.1.1]
                                0/ 100 =  0%   |
  2    9ms     0/ 100 =  0%     0/ 100 =  0%  96.120.28.53
                                0/ 100 =  0%   |
  3   10ms     0/ 100 =  0%     0/ 100 =  0%  te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  68.85.183.142
                                0/ 100 =  0%   |
  5   12ms     0/ 100 =  0%     0/ 100 =  0%  be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
                                0/ 100 =  0%   |
  6   13ms     0/ 100 =  0%     0/ 100 =  0%  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
                                0/ 100 =  0%   |
  8   14ms     0/ 100 =  0%     0/ 100 =  0%  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
                                0/ 100 =  0%   |
  9   11ms     0/ 100 =  0%     0/ 100 =  0%  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
                                0/ 100 =  0%   |
 10   14ms     0/ 100 =  0%     0/ 100 =  0%  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
                                0/ 100 =  0%   |
 11  114ms     6/ 100 =  6%     6/ 100 =  6%  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
                                0/ 100 =  0%   |
 12   63ms     0/ 100 =  0%     0/ 100 =  0%  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
                                0/ 100 =  0%   |
 13  166ms     7/ 100 =  7%     7/ 100 =  7%  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
                                0/ 100 =  0%   |
 14   67ms     0/ 100 =  0%     0/ 100 =  0%  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
                                0/ 100 =  0%   |
 15   67ms     0/ 100 =  0%     0/ 100 =  0%  204.2.229.242
                                0/ 100 =  0%   |
 16   84ms     0/ 100 =  0%     0/ 100 =  0%  204.2.229.97

Trace complete.

So tonight I just opted not to deal with it. I'll go play something else rather than play an unplayable game. Notice how once again it's NTT that's the issue? Two nodes with very high ping times and dropping packets. SE, please, have a talk with your ISP. Get this figured out. Because it isn't going away.