Unbearable server lag since yesterday

[MegaMage]

Hello,

I am on Lamia server. Since yesterday evening there has been a consistent unbearable delay in game. It makes the game completely unplayable as everything in game comes to a complete stop which then fast forwards to catch up. It happens every few seconds.

I have read online that this may be due to Comcast <> SE's servers.

Can anyone confirm this?
Anyone have any guidance on what I might do to curtail this issue?

I have re-issued myself a new IP, restarted modem & router, etc. and nothing has any effect. I have Gigabit internet, connected through wired ethernet. I experience no issues with lag in any other game, streaming service, website, etc.

[Coletergeist]

I'm currently reinstalling the game because I thought that'd help (prob wont); I've been having this issue pretty bad lately as well but have also restarted the modem, changed some graphic settings, etc. I use Comcast as well, so perhaps that may be the problem? Not sure, just thought the feedback would help.

I guess there's others saying they are also having this same issue.

[Livilda]

Exactly the same issue, on Balmung, tonight and last night. Also on Comcast, connecting from Nashville, Tennessee.

[RzTSionX]

Also having the same issue which started last night. Also on a Comcast connection.

[Bon-Senpai]

it has been hitting me badly also since last night in Excalibur, a lot of my fc members are also experiencing it to, comcast yes.

[PapiCake]

I also started having issues last night while on Cactuar. I tried running a dungeon today and it was non-stop spikes. Also on Comcast.

No issues with other games.

[Caesius]

Been hitting a couple of lag spikes lately after running for months and months with no problems; last time I regularly experienced lag was in the fall I think.

Lag is unbearable tonight. On Comcast.

[Jarrell]

I am on Brynhildr (Crystal server group). I've been experiencing the same bad lag as of approx 18:00 PDT today. Players warping around in dungeons, aoe you've moved out of landing on you, etc.

I ran a number of tracerts over the last hour to the gameservers (located IP from Windows Resource Monitor for the FF14 application). Based on my findings, it looks like either an issue with the NTT Sacramento network or server bank CA2 specifically (google it if you want to know more). I'm assuming the FF14 servers are located here based on what the tracert was showing me. However, given the fact that everyone with this issue is on Comcast (myself included), there could be an issue with network routing tables putting too much data on the wrong pipelines between these networks.

Tracerts as follows (initial hops removed for anonymity purposes):

---

tracert www.google.com (to check connection itself)

Tracing route to www.google.com [172.217.11.164]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms x
2 8 ms 12 ms 8 ms x
3 9 ms 9 ms 9 ms po-302-1216-rur02.snyder.az.pima.comcast.net [68.86.201.73]
4 8 ms 7 ms 10 ms be-6-ar02.pimaco.az.pima.comcast.net [162.151.153.157]
5 22 ms 19 ms 28 ms be-36912-cs01.losangeles.ca.ibone.comcast.net [96.110.45.129]
6 19 ms 23 ms 20 ms be-2111-pe11.losangeles.ca.ibone.comcast.net [96.110.33.2]
7 18 ms 26 ms 18 ms 50.242.151.74
8 22 ms 22 ms 23 ms 64.233.174.209
9 22 ms 23 ms 21 ms 108.170.225.69
10 20 ms 19 ms 21 ms lax28s15-in-f4.1e100.net [172.217.11.164]

Trace complete.

Notes: No issues on trace to google from what I can see.

---

tracert 204.2.229.113 (Brynhildr server IP)

Tracing route to 204.2.229.113 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms x
2 9 ms 7 ms 7 ms x
3 7 ms 8 ms 8 ms po-302-1215-rur01.snyder.az.pima.comcast.net [68.86.201.65]
4 9 ms 10 ms 8 ms po-2-rur02.snyder.az.pima.comcast.net [68.87.172.114]
5 8 ms 10 ms 10 ms be-6-ar02.pimaco.az.pima.comcast.net [162.151.153.157]
6 24 ms 19 ms 20 ms be-36922-cs02.losangeles.ca.ibone.comcast.net [96.110.45.133]
7 20 ms 19 ms 19 ms be-2201-pe01.losangeles.ca.ibone.comcast.net [96.110.44.102]
8 22 ms 20 ms 21 ms 50.242.151.62
9 34 ms 28 ms 29 ms ae-11.r25.lsanca07.us.bb.gin.ntt.net [129.250.2.187]
10 29 ms 28 ms 28 ms ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
11 64 ms 65 ms 64 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 63 ms 63 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 61 ms * 63 ms 204.2.229.234
14 62 ms 62 ms 62 ms 204.2.229.113

Trace complete.

---

tracert 204.2.229.113

Tracing route to 204.2.229.113 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms x
2 9 ms 9 ms 9 ms x
3 7 ms 8 ms 7 ms po-302-1215-rur01.snyder.az.pima.comcast.net [68.86.201.65]
4 9 ms 9 ms 9 ms po-2-rur02.snyder.az.pima.comcast.net [68.87.172.114]
5 8 ms 9 ms 11 ms be-6-ar02.pimaco.az.pima.comcast.net [162.151.153.157]
6 21 ms 20 ms 20 ms be-36922-cs02.losangeles.ca.ibone.comcast.net [96.110.45.133]
7 20 ms 23 ms 22 ms be-2201-pe01.losangeles.ca.ibone.comcast.net [96.110.44.102]
8 21 ms 19 ms 21 ms 50.242.151.62
9 * * * Request timed out. (this one is the first hop on the NTT network)
10 29 ms 29 ms 28 ms ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
11 65 ms 64 ms 63 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 65 ms 65 ms 63 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 64 ms 66 ms 204.2.229.234
14 62 ms * 61 ms 204.2.229.113

Trace complete.

---

tracert 204.2.229.113

Tracing route to 204.2.229.113 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms x
2 7 ms 7 ms 7 ms x
3 15 ms 8 ms 8 ms po-302-1215-rur01.snyder.az.pima.comcast.net [68.86.201.65]
4 8 ms 9 ms 9 ms po-2-rur02.snyder.az.pima.comcast.net [68.87.172.114]
5 9 ms 9 ms 7 ms be-6-ar02.pimaco.az.pima.comcast.net [162.151.153.157]
6 27 ms 20 ms 21 ms be-36922-cs02.losangeles.ca.ibone.comcast.net [96.110.45.133]
7 22 ms 28 ms 21 ms be-2201-pe01.losangeles.ca.ibone.comcast.net [96.110.44.102]
8 20 ms 19 ms 19 ms 50.242.151.62
9 * 30 ms 30 ms ae-11.r25.lsanca07.us.bb.gin.ntt.net [129.250.2.187]
10 33 ms 28 ms 27 ms ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
11 67 ms 64 ms 67 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 65 ms 65 ms 65 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 65 ms 64 ms 64 ms 204.2.229.234
14 64 ms 68 ms 64 ms 204.2.229.113

Trace complete.

Hopefully this helps someone.

TLDR: Issue is either Comcast routing tables, NTT network, or NTT server bank CA2 (server hosting for FF14). Hard to tell beyond that, I am not a network admin.

[Eumen]

This sadly isn't an issue specifically with FF14 but one that they can possibly reach out to the correct people to fix. It's where comcast and NTT's network link up - So nothing you can do on the local side at your home and nothing comcast can specifically do because if you call for support, you get the call center folks who only follow script and send out a field tech to solve a problem that isn't there.

SE, this is specifically a problem starting between comcast and NTT I believe at their IP address of 129.250.5.25 - or one of the following after that. So far after running a few continuous pings and tracerts it's been one of the following locations:

37 ms 37 ms 39 ms ae-7.r25.dllstx09.us.bb.gin.ntt.net [129.250.5.25]
50 ms 51 ms 50 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
50 ms 50 ms 50 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
* 87 ms 85 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
* 86 ms 88 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]

I say one of them because early on the night it was specifically the first of those. but as the night went on I found it seemed to move up the chain. And then later on around I want to say midnight to 1 AM EST it will likely resolve like it did the night before. This happened in early/mid 2020 as well.

Edit, post above me said it as well. They posted it as I was typing

[Carmina8710]

Husband & I live in Mobile, Al, we are on the Diabolos server, & we are Comcast/Xfinity users as well.

I've been playing most of today with no lag then around 9:30-10pm mobs/players were freezing then blinking ahead randomly. We both recently made some changes to our graphic setups (refresh rates on our monitors to be precise) so I tried reverting those changes, no dice. Tried resetting our router, also no dice.