Lag spikes of 1 second every 1-3 minutes.

[QueenRoe]

Coming in here to say I started having issues on Thursday last week. Exactly as described here. I have found it's 100% packet loss causing it coming from SE's side as speedtests have yielded 0 Packet Loss with and without a VPN.

Are you using a VPN? No
Are you using wired or wireless communication? Wireless
What Platform are you using? (Steam/Windows/Mac/PS4 etc.) Windows
Does this issue occur with one or multiple characters? Multiple
At what point do you get disconnected and/or are unable to connect? Never disconnected. Times are random on when the lag happens making it hard to pinpoint. Sometimes immediately, sometimes minutes into an instance.
How often does the issue occur? Since last week and has continued since. Happens constantly with a few minute breaks in between the next lag spike.

Internet Service Provider: Spectrum
Region/State: NA/Tennessee

All steps taken to resolve the issue: Restarted PC, reinstalled and updated drivers, restarted router, ran a VPN, closed all other programs while running XIV, rolled back on GPU driver, submitted a packet loss report to SE, and all other steps mentioned above

[DDRDiesel]

Looks like I'm back with another network issue. This time, rather than difficulties logging in, it's been a consistent problem with rubberbanding, high ping, and dropped packets.

These results are for the NA server. I'm playing from the East Coast on Optimum.

Ping statistics for 204.2.29.78:
Packets: Sent = 969, Received = 891, Lost = 78 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 150ms, Average = 125ms

While 8% doesn't seem like a lot, they happen in blocks and the effect is most noticeable in-game while running content like dungeons or FATEs. The enemies stutter in their movement or sometimes abilities won't trigger immediately like they're supposed to.

Below is a result of tracert, with the first four hops omitted for privacy concerns:
5 5 ms 5 ms 6 ms 451be068.cst.lightpath.net [65.19.99.104]
6 6 ms 5 ms 4 ms 64.15.1.151
7 6 ms 5 ms 7 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 6 ms 5 ms 5 ms ewr-bb2-link.ip.twelve99.net [62.115.143.12]
9 * * * Request timed out.
10 11 ms 5 ms 8 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 6 ms 6 ms 7 ms ae-16.r23.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 25 ms 24 ms 25 ms ae-10.r24.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 24 ms 23 ms 23 ms ae-1.r25.chcgil09.us.bb.gin.ntt.net [129.250.5.135]
14 120 ms 120 ms 120 ms ae-7.r26.snjsca04.us.bb.gin.ntt.net [129.250.4.137]
15 124 ms 124 ms 125 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 124 ms 125 ms 124 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 124 ms 123 ms 125 ms 204.2.29.241
18 124 ms 124 ms 124 ms 204.2.29.78

As you can see, the high ping starts when it gets to hop 14, node titled ae-7.r26.snjsca04.us.bb.gin.ntt.net [129.250.4.137]. This could indicate a problem on that node specifically or the one before it. These results are consistent and do not change.

Playing on Windows 64-bit DX11 client. Wired connection with speed tests confirming over 300Mbps download speed. No other pings to any other IP addresses show dropped packets or high ping results.

I have tried network hardware resets, PC reset, and various network troubleshooting on my PC including DNS flush, ipconfig release/renew, netsh winsock reset, updating network drivers and uninstalling/reinstalling the network card.

This is not a local issue, this appears to be on the route to the server or an issue in the datacenter itself

[Momiji_I]

Trying again...

There seems to be quite a lot of packet loss in the twelve99.net network. Here are two separate tracert command rounds to the Chaos DC (high ping is normal since I live in OCE). Tracert to Materia DC does not have this series of packet loss events.

An "okay" run:

7 134 ms 136 ms 134 ms mercurynz-ic-388837.ip.twelve99-cust.net [62.115.45.43]
8 133 ms 135 ms 137 ms sjo-b23-link.ip.twelve99.net [62.115.45.42]
9 * * * Request timed out.
10 165 ms 165 ms 166 ms den-bb1-link.ip.twelve99.net [62.115.139.105]
11 * * 288 ms chi-bb1-link.ip.twelve99.net [62.115.115.77]
12 219 ms 210 ms 202 ms nyk-bb5-link.ip.twelve99.net [62.115.139.32]
13 * 276 ms 274 ms ldn-bb1-link.ip.twelve99.net [62.115.139.245]
14 * * * Request timed out.
15 285 ms 287 ms 283 ms ffm-bb1-link.ip.twelve99.net [62.115.123.12]
16 296 ms * 298 ms ffm-b11-link.ip.twelve99.net [62.115.124.117]
17 292 ms 286 ms 288 ms squareenix-ic-369631.ip.twelve99-cust.net [80.239.195.85]
18 296 ms 296 ms 299 ms 80.239.145.241
19 284 ms 290 ms 288 ms 80.239.145.6

A worse run:

7 136 ms 134 ms 135 ms mercurynz-ic-388837.ip.twelve99-cust.net [62.115.45.43]
8 134 ms 135 ms 135 ms sjo-b23-link.ip.twelve99.net [62.115.45.42]
9 * * 138 ms sjo-bb1-link.ip.twelve99.net [62.115.139.16]
10 163 ms 162 ms 160 ms den-bb1-link.ip.twelve99.net [62.115.139.105]
11 * * * Request timed out.
12 199 ms * * nyk-bb5-link.ip.twelve99.net [62.115.139.32]
13 273 ms * 272 ms ldn-bb1-link.ip.twelve99.net [62.115.139.245]
14 * * 278 ms prs-bb1-link.ip.twelve99.net [62.115.135.25]
15 288 ms 283 ms 284 ms ffm-bb1-link.ip.twelve99.net [62.115.123.12]
16 297 ms * * ffm-b11-link.ip.twelve99.net [62.115.124.117]
17 287 ms 282 ms 284 ms squareenix-ic-369631.ip.twelve99-cust.net [80.239.195.85]
18 295 ms 295 ms 296 ms 80.239.145.241
19 285 ms 282 ms 284 ms 80.239.145.6