Awful Ping and Latency in southeast NA?

[Havoczero]

Also experiencing this issue. Southeast NA, on Spectrum. Latency is making the game unplayable. Tracert is showing issues with NTT around Sacramento with a large jump in ping times. I think NTT just swapped the AT&T and Spectrum cables or something.



8 28 ms 26 ms 25 ms 035-148-195-133.res.spectrum.com [35.148.195.133]
9 26 ms 26 ms 27 ms 169.254.250.250
10 27 ms 28 ms 27 ms lag-63.crr01mnchtn.netops.charter.com [159.111.172.172]
11 39 ms 38 ms 43 ms lag-20.rcr01mnchtnem.netops.charter.com [96.34.13.234]
12 38 ms 40 ms 39 ms lag-10.rcr01sghlgaao.netops.charter.com [96.34.13.230]
13 40 ms 40 ms 40 ms lag-403.atlngamq46w-bcr00.netops.charter.com [96.34.15.138]
14 44 ms 39 ms 42 ms lag-303.pr2.atl20.netops.charter.com [66.109.9.105]
15 40 ms 40 ms 40 ms ae14.cr4-atl2.ip4.gtt.net [208.116.217.29]
16 44 ms 45 ms 40 ms ae20.cr2-atl2.ip4.gtt.net [89.149.130.146]
17 40 ms 47 ms 65 ms as2914-gw.cr2-atl2.ip4.gtt.net [199.229.229.202]
18 41 ms 64 ms 40 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
19 61 ms 64 ms 64 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
20 * 58 ms 57 ms ae-1.r20.dllstx14.us.bb.gin.ntt.net [129.250.3.54]
21 * 191 ms 204 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
22 207 ms 213 ms 203 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
23 206 ms 208 ms 209 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
24 213 ms 207 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
25 * * * Request timed out.
26 200 ms 200 ms 200 ms 204.2.29.85

[Khryseis_Astra]

Northeast also seeing this on Comcast… as everyone on AT&T started to see improvement, mine has gotten worse, starting Sunday morning. The lag/stuttering is near constant now, though has periods of tolerability during off-peak hours… from my trace route, it looks like my problems start in NTT/San Jose.

[Sols]

Adding my voice here, I haven't been able to play all day. My ISP is cox, had no issues until this morning. My ping has been between 150 and 200 every time i cmd, and the game itself is unplayable.

[shaiel]

Same here, it was really difficult to do content. My party couldn't complete duty in instance because of lag. Also on Spectrum internet, Primal datacenter if that matters.

[HawkeScream]

Another batch of us, Cox in FL. Me on PC, husband on PS5, and our friend a few streets over on PS4, all having the same issue.

Getting 100% packet loss pinging the FFXIV server =/

edit to add a tracert:

Tracing route to 204.2.29.73 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.0.1
2 12 ms 9 ms 9 ms 10.4.192.1
3 11 ms 8 ms 9 ms 100.122.94.96
4 9 ms 8 ms 8 ms 100.122.93.64
5 18 ms 18 ms 16 ms mtc3dsrj01-ge708.103.rd.ok.cox.net [68.1.2.29]
6 20 ms 17 ms 18 ms atl-b24-link.ip.twelve99.net [62.115.167.68]
7 21 ms 17 ms 19 ms ae-2.a03.atlnga05.us.bb.gin.ntt.net [129.250.9.21]
8 23 ms 43 ms 27 ms ae-2.r25.atlnga05.us.bb.gin.ntt.net [129.250.2.120]
9 46 ms 34 ms 42 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
10 38 ms 34 ms 34 ms ae-1.r20.dllstx14.us.bb.gin.ntt.net [129.250.3.54]
11 66 ms 65 ms 65 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 164 ms 163 ms 165 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 165 ms * * ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 173 ms 176 ms 168 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 168 ms 168 ms 166 ms 204.2.29.73

[Lck0ut]

For everyone here, a VPN will fix the issue for now. As said in the other forum thread, please report the issue to the Customer Service Reps at your ISP, and if they get enough complaints, they will figure out the problem and a fix.

[grinkdaboy]

works on my machine

[Catwho]

As others have posted their tracerts, I can confirm I was running into the same issue at the same node last night.

The server node at ae-2.r24.lsanca07.us.bb.gin.ntt.net is the one that is bottlenecking us. I believe this is in Los Angeles, just before NTT's traffic hands off to the Sacramento nodes.

This is not an issue with our local ISPs!

My latency was as low as 30 ms through the Dallas Texas node for NTT. The hand off to Los Angeles, however, added an extra 120 ms latency, so that the total latency was between 150-200 ms for the entire hop.

Add in about 5% (or 1 out of 20) of my test ping packets straight up dropping when I was running a continuous ping to that node, and it's bad.

When I was trying to do an Expert roulette, I saw people jumping in the dungeon every 2-3 seconds. I would freeze up periodically and when I unfroze, I was dead. I opted to skip raiding yesterday and focus on my farm.