Extreme lag and rubberbanding.

[Genuvien]

I play on PC. I live in Ohio, USA.

Data Center: Primal > Famfrit

However this issue is not restricted to Primal > Famfrit. I have tested other Data Centers and they also have this issue.

I run a physical cable connection to my router, no wifi, no other devices use my internet.

There are no other programs or applications running while FFXIV is running.

I am able to play all my other games with no latency issues. These titles include World of Warcraft, Path of Exile, Counter-Strike Global Offensive, Warframe, The Remnant, Starcraft 2.

This did not use to be an issue until the last few weeks, and it keeps getting worse. I am currently not able to play the game in what I would consider meaningful activities such as open world fates, instanced dungeons and raids.

When will this be fixed? I'd like to play the game. Thank you.

[Kirika-]

Run a Pathping to 204.2.229.98 (the Primal>Famfrit server IP) to see where packet loss is occurring.
https://docs.microsoft.com/en-us/pre...ectedfrom=MSDN

Usage:
Run Command Prompt
Type in:
pathping 204.2.229.98
Press Enter

It will take several minutes to complete.

Once done, you can screen shot the results (or mark and copy/paste) and post here and we can advise where the problem may be, just mung out the first three lines of the results to hide your own IP (hops #0, #1, and #2)

[Genuvien]

Tracing route to 204.2.229.98 over a maximum of 30 hops

0 DESKTOP
1 192.168
2 athn.oh.frontiernet.net [74.42.
3 ae4-0.car01.athn.oh.frontiernet.net [74.40.71.189]
4 ae5---0.car01.nrwl.oh.frontiernet.net [74.40.5.58]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% athn.oh.frontiernet.net [74.42
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% ae4-0.car01.athn.oh.frontiernet.net [74.40.71.189]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% ae5---0.car01.nrwl.oh.frontiernet.net [74.40.5.58]

Trace complete.

[Bloodb]

17% Packet loss
The USA election
Covid-19
Businesses, churches, and schools using video streaming now

I live in the midwest, USA
Here's some pings to google:

Microsoft Windows [Version 10.0.18363.1139]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\brend>ping google.com -t

Pinging google.com [2607:f8b0:4000:812::200e] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=23ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=19ms
Reply from 2607:f8b0:4000:812::200e: time=20ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=35ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=20ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=19ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=38ms
Reply from 2607:f8b0:4000:812::200e: time=34ms
Reply from 2607:f8b0:4000:812::200e: time=16ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=17ms
Reply from 2607:f8b0:4000:812::200e: time=36ms
Reply from 2607:f8b0:4000:812::200e: time=22ms
Reply from 2607:f8b0:4000:812::200e: time=18ms
Request timed out.
Reply from 2607:f8b0:4000:812::200e: time=21ms
Reply from 2607:f8b0:4000:812::200e: time=17ms

Ping statistics for 2607:f8b0:4000:812::200e:
Packets: Sent = 34, Received = 28, Lost = 6 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 38ms, Average = 21ms
Control-C
^C
C:\Users\brend>

17% packet loss! Take some deep breathes and go for a short walk. Try and be patient. Packet loss from user overload gets better and worse from time to time

One of the major causes of packet loss is link congestion. A simple analogy is rush hour traffic when there are more cars on the road than the road can sufficiently handle. Another analogy is a 4-lane road merging into 2 lanes. What happens is that there are more packets arriving on a link than that link is designed to handle.

Network congestion is a cause of packet loss that can affect all types of networks. When content arrives for a sustained period at a given router or network segment at a rate greater than it is possible to send through, there is no other option than to drop packets. If a single router or link is constraining the capacity of the complete travel path or of network travel in general, it is known as a bottleneck. In some cases, packets are intentionally dropped by routing routines, or through network dissuasion technique for operational management purposes.

[Kirika-]

Kinda odd there is only 5 hops between you and the server.... seems like a lot is missing.
I mean the last hop you show is still within your ISP's network, so it's not showing outside into the internet backbone nor into SE's ISP's network and SE's internal network.
If your pathping runs are truly cutting off within Frontier Net, then that is where the problem is.

[Genuvien]

C:\Users\kvasi>ping 204.2.229.98 -t

Pinging 204.2.229.98 with 32 bytes of data:
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=75ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=77ms TTL=51
Reply from 204.2.229.98: bytes=32 time=75ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51
Reply from 204.2.229.98: bytes=32 time=76ms TTL=51


not showing any packet loss, no loss to google.com or anywhere else I could find. 72-77ms is my constant ms for WoW in-game latency as well, so this looks normal to me. I raid in WoW weekly for 4-6 hours at a time without experiencing any rubberbanding like I see in FFXIV trying to raid.

Is this lag being caused by the servers then? I use to play FFXIV early morning, but I wanted to clear all savage/ultimate raid content so I've had to log in later in the day to find players. I guess I could test that myself by switching back to early-mid day play. I'll start now. Thanks for help so far.

[Genuvien]

That was an easy answer to find...Even my connection has changed on the login screen from 'Good' to 'Excellent' by just trying to login earlier in the day. Here's a screenshot from now. https://i.imgur.com/lo58X6x.png

That's a shame. Has it always been this way for FFXIV? Or will it be fixed going forward?


Edit: I was just able to complete 3 hours of raids with no issues at all, something I haven't been able to do for nearly 2 weeks. The game plays soooooo goooood holy hell what a difference, I really hope they expand to be able to handle the player influx. I guess you can mark this 'solved', since its not an issue on my end. Thank you guys for your help! Appreciate it.

[icy_]

It's the servers, and it's pretty bad for me right now, starting two days ago. Bloodb's data indicates a problem on their end, since pings to google are usually very reliable.
I currently have complete low pings to google, yet from 10% to 21% loss when I ping an FFXIV server. In-game this presents as constant rubberbanding. The average ping, when not timed out, seems to have risen at least 20ms since I last did such a test.

Ping statistics for 204.2.229.86:
Packets: Sent = 100, Received = 79, Lost = 21 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 119ms, Average = 116ms

[Rarrum]

Same problem on Aether today. In fact a lot of the deep dungeon community even on other DCs can't really play today, since small hiccups mean certain death in there solo on higher floors.

[Brave_Sir_Robin]

Just tried running HadesEx with a cross-world PF and most of us (at least 6 out of 8) were having nothing but latency issues, causing us to wipe multiple times and abandon the party. For context, I am hard-wired into my router and normally get about 90-100 Mbps. I'm able to stream and watch Youtube videos with no issue, but the latency with FFXIV has been pretty awful this last week. And yes, I did not have anything else opened or running while playing tonight.

Per the earlier suggestion, I ran a pathping trace to the Primal server and got the following result (bolded the data loss portion):

4 10ms 0/ 100 = 0% 0/ 100 = 0% 68.85.228.193
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% be-106-ar01.northdade.fl.pompano.comcast.net [69.139.182.105]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% be-20214-cr02.miami.fl.ibone.comcast.net [68.86.90.205]
0/ 100 = 0% |
7 12ms 0/ 100 = 0% 0/ 100 = 0% be-12274-pe01.nota.fl.ibone.comcast.net [68.86.82.154]
0/ 100 = 0% |
8 13ms 0/ 100 = 0% 0/ 100 = 0% 50.242.151.66
0/ 100 = 0% |
9 13ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
0/ 100 = 0% |
10 15ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r22.miamfl02.us.bb.gin.ntt.net [129.250.4.88]
0/ 100 = 0% |
11 47ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r24.dllstx09.us.bb.gin.ntt.net [129.250.2.219]
0/ 100 = 0% |
12 47ms 0/ 100 = 0% 0/ 100 = 0% ae-0.r25.dllstx09.us.bb.gin.ntt.net [129.250.2.80]
0/ 100 = 0% |
13 81ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
0/ 100 = 0% |
14 82ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
6/ 100 = 6% |
15 111ms 6/ 100 = 6% 0/ 100 = 0% ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
0/ 100 = 0% |
16 --- 100/ 100 =100% 94/ 100 = 94% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
0/ 100 = 0% |
17 115ms 9/ 100 = 9% 3/ 100 = 3% 204.2.229.234
0/ 100 = 0% |
18 107ms 6/ 100 = 6% 0/ 100 = 0% 204.2.229.98