Regarding Reports on Recent Connection Problems with the NA Data Center

[Callinon]

(By the way, tip for those posting results: a basic Trace in CMD isn't super helpful to see packet loss trend over a long period of time. Grab WinMTR and let it run for 15-60 minutes.)

You're right but it's what they asked for and SE has a habit of completely ignoring data if it isn't precisely what they asked for.

[MizunoNeko]

I'm seeing 20-25% packet loss over periods of 1 minute from 9:15 to 9:45 tonight. Couldn't do anything in game but run old irrelevant content.

[Theodulus]

Comcast user here. I get severe lag during peak hours, sometimes leading to a disconnect with error code 90006. This happens every day at peak hours.

[Sereneisis]

11:10 01/24/2018
  1     1 ms     2 ms     1 ms  [REDACTED]
  2    11 ms     9 ms     8 ms  [REDACTED]
  3    11 ms    11 ms    11 ms  [REDACTED] 
  4    11 ms    11 ms    10 ms  [REDACTED]
  5    11 ms    11 ms    10 ms  ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 
  6    12 ms    14 ms    18 ms  be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 
  7    12 ms    11 ms    10 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 
  8    14 ms    12 ms    10 ms  50.242.151.58 
  9    12 ms    11 ms    11 ms  ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 
 10    11 ms    44 ms    10 ms  ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 
 11    29 ms    31 ms    29 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 
 12   194 ms   195 ms   193 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 
 13   195 ms   186 ms   190 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 
 14   188 ms   193 ms   192 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 
 15   196 ms   197 ms   196 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 
 16   190 ms     *      198 ms  204.2.229.234 
 17   188 ms   191 ms   191 ms  204.2.229.9

[Nongelen]

Frequent lag spikes between 9-12PM (ping jumps from 90 to over 200) all week long Eastern Time
Comcast

[RayneBoemir]

Hello I am having problems as well. I came back after a long absence from the game and everything was fine, but a few days ago lag started hampering my ability to play the game, it is most noticeable when I am playing my BLM, and I am trying to cast Fire4 under Triple Cast; there are other times when it is noticeable, but this is the time when it is most apparent. I hit the key and nothing gets casted and I have to hit it again sometimes several times.

I am playing on PS4 I forwarded all the ports as suggested even though this has never been an issue before. I have also done all other recommendations including connecting the router/modem directly to the PS4 but the issue persists. I have ran a trace and I am seeing packet losses where the same players are having at NTT and also the address before the final one I am assuming this is the login server for FFXIV.

--- Nice Trace to 204.2.229.9 ---

1) 192.168.0.1 (192.168.0.1) 6.279 ms, 11/11 ps, 0.0% loss
2) * * *
3) bun1.tamp20-car2.bhn.net (72.31.208.106) 14.110 ms, 11/11 ps, 0.0% loss [AS 33363] United States
4) ten0-1-0-7-8.tamp20-car1.bhn.net (72.31.208.48) 15.068 ms, 10/10 ps, 0.0% loss [AS 33363] United States
5) hun0-2-0-9.tamp20-cbr1.bhn.net (72.31.3.118) 16.248 ms, 10/10 ps, 0.0% loss [AS 33363] United States
6) 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96) 21.096 ms, 10/10 ps, 0.0% loss [AS 7843] United States
7) 0.ae0.pr0.mia00.tbone.rr.com (66.109.1.89) 19.688 ms, 10/10 ps, 0.0% loss [AS 7843] United States
8) ix-ae-23-0.tcore1.mln-miami.as6453.net (63.243.152.105) 22.303 ms, 10/10 ps, 0.0% loss [AS 6453] United States
9) ae-6.a00.miamfl02.us.bb.gin.ntt.net (129.250.9.33) 20.378 ms, 10/10 ps, 0.0% loss [AS 2914] United States
10) ae-7.r04.miamfl02.us.bb.gin.ntt.net (129.250.2.202) 121.362 ms, 10/10 ps, 0.0% loss [AS 2914] United States
11) ae-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.110) 31.823 ms, 10/10 ps, 0.0% loss [AS 2914] United States
12) ae-4.r23.asbnva02.us.bb.gin.ntt.net (129.250.2.86) 42.608 ms, 10/10 ps, 0.0% loss [AS 2914] United States
13) ae-10.r22.snjsca04.us.bb.gin.ntt.net (129.250.6.237) 120.154 ms, 10/10 ps, 0.0% loss [AS 2914] United States
14) ae-40.r02.snjsca04.us.bb.gin.ntt.net (129.250.3.121) 124.543 ms, 10/10 ps, 0.0% loss [AS 2914] United States
15) ae-3.r00.scrmca02.us.bb.gin.ntt.net (129.250.7.11) 125.128 ms, 10/10 ps, 0.0% loss [AS 2914] United States
16) xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) 115.770 ms, 10/10 ps, 0.0% loss [AS 2914] United States
17) 204.2.229.234 (204.2.229.234) 127.365 ms, 7/9 ps, 22.2% loss [AS 2914] United States
18) 204.2.229.9 (204.2.229.9) 115.252 ms, 10/10 ps, 0.0% loss [AS 2914] United States

Also another one

--- Nice Trace to 204.2.229.9 ---

1) 192.168.0.1 (192.168.0.1) 4.165 ms, 33/33 ps, 0.0% loss
2) * * *
3) bun1.tamp20-car2.bhn.net (72.31.208.106) 13.891 ms, 33/33 ps, 0.0% loss [AS 33363] United States
4) ten0-1-0-7-8.tamp20-car1.bhn.net (72.31.208.48) 14.457 ms, 33/33 ps, 0.0% loss [AS 33363] United States
5) hun0-2-0-9.tamp20-cbr1.bhn.net (72.31.3.118) 15.099 ms, 32/32 ps, 0.0% loss [AS 33363] United States
6) 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96) 17.088 ms, 32/32 ps, 0.0% loss [AS 7843] United States
7) 0.ae0.pr0.mia00.tbone.rr.com (66.109.1.89) 20.296 ms, 32/32 ps, 0.0% loss [AS 7843] United States
8) ix-ae-23-0.tcore1.mln-miami.as6453.net (63.243.152.105) 20.099 ms, 32/32 ps, 0.0% loss [AS 6453] United States
9) ae-6.a00.miamfl02.us.bb.gin.ntt.net (129.250.9.33) 21.285 ms, 32/32 ps, 0.0% loss [AS 2914] United States
10) ae-7.r04.miamfl02.us.bb.gin.ntt.net (129.250.2.202) 115.685 ms, 32/32 ps, 0.0% loss [AS 2914] United States
11) ae-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.110) 33.943 ms, 31/32 ps, 3.1% loss [AS 2914] United States
12) ae-4.r23.asbnva02.us.bb.gin.ntt.net (129.250.2.86) 45.973 ms, 32/32 ps, 0.0% loss [AS 2914] United States
13) ae-10.r22.snjsca04.us.bb.gin.ntt.net (129.250.6.237) 116.012 ms, 31/32 ps, 3.1% loss [AS 2914] United States
14) ae-40.r02.snjsca04.us.bb.gin.ntt.net (129.250.3.121) 118.867 ms, 32/32 ps, 0.0% loss [AS 2914] United States
15) ae-3.r00.scrmca02.us.bb.gin.ntt.net (129.250.7.11) 120.650 ms, 32/32 ps, 0.0% loss [AS 2914] United States
16) xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) 115.285 ms, 32/32 ps, 0.0% loss [AS 2914] United States
17) 204.2.229.234 (204.2.229.234) 117.642 ms, 27/32 ps, 15.6% loss [AS 2914] United States
18) 204.2.229.9 (204.2.229.9) 114.067 ms, 32/32 ps, 0.0% loss [AS 2914] United States

Edit: Forgot to mention I have Charter in FL

[Ariellendera]

Hello Everyone,

Thank you for your continued patience with the ongoing connection and latency issues regarding the NA data centers. We are still investigating the reported issues and are actively working with our teams to get a resolution. Please continue to post trace routes and connection information as outlined in the previous post if you have not already, as we are still collecting information. We will update you as soon as we are able.

Thank you for posting on the Final fantasy XIV technical support forums

[Callinon]

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  RT-AC68U-5570 [192.168.1.1]
  2     9 ms     8 ms     8 ms  96.120.28.53
  3     9 ms     8 ms     9 ms  te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
  4     8 ms     9 ms     9 ms  68.85.183.142
  5    14 ms    11 ms    10 ms  be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
  6    20 ms    12 ms    12 ms  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
  7    12 ms    13 ms    14 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  8    10 ms     9 ms    11 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  9   186 ms   186 ms   186 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 10    12 ms    20 ms    10 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 11   186 ms     *      178 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 12   189 ms   188 ms   189 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 13   188 ms   186 ms   188 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 14   190 ms   187 ms   186 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 15   180 ms   184 ms   180 ms  204.2.229.234
 16   174 ms   187 ms   187 ms  204.2.229.97

Trace complete.

So we keep posting this stuff, and it all looks roughly the same. You've been "investigating" this problem for literal months at this point. Is there an end in sight? Will NTT do anything to alleviate the problem? Because it's NTT. You understand that right? Months of investigation must have yielded the same (if not superior) results as a couple dozen forum posters posting their connection data for you. It's prime time, every night, without fail. Ping times in the 200-400 range and spiking as high as 900. I'm not across an ocean or on the damn moon or something. I'm in a major metropolitan area with modern infrastructure and my connection is going to another place that would be described with the same terms. I don't encounter a connection problem until I reach NTT's infrastructure which is, quite obviously, not up to the task of handling SE's traffic.

[Kusanagi7]

@Ariellendera i dont play on NA data centers i play on european data center and still get the lags are you also investigating the issue's there aswell.?

[Ekko]

https://share.pingplotter.com/YMC1sM9PhiZ.png

Same problem on Ragnarok.