Extreme lag and rubberbanding.

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.

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)

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.

17% Packet loss :mad: :(
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:

Quote:

---

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

Quote:

---

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.

---

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.

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.

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.

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

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.

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

Yeah...So I wanted to try now that it's later in the day. I am having issue even logging in to the game at this time of day. Visual here as "Poor". https://i.imgur.com/feD2jd9.png


Damn that's awful. My latency has now become entirely unstable like it usually has been the past few weeks.

I'm getting severe packet loss, my latency has went from a very normal 76ms to fluctuating wildly between 85-117ms. I'm talking like 4-6 seconds of rubberbanding.

I can still ping google.com with no problem, and I can log in to my other games with no latency issues.

I joined a e5s just to see what would happen, but its not just me, they're all lagging so hard we can't do mechanics. Hell some of the mechanics don't even seem to exist because you lag so hard you can't see them.

I said I'd off tank because the lag spikes, but I lagged so hard that I never saw the add even spawn or attach to me, or walk to me. I just died after everyone ran in place for a few seconds on screen.

Can anyone ping the server with less than 100ms, and not get packet loss at this time of day? Is this a new issue? Is this just how its always been and I never knew?

Been happening here as well on two different accounts on two separate computers. Internet works fine elsewhere but FF14. This was an issue all day, and it seemed to be related to AT&T being blocked by SE or the other way around. Maybe a DDoS? Seemed to happen to others on discord who are on AT&T. FF14's IPs were getting lots of packet loss.

Looks like they've fixed packet loss, but not the variable ping. Earlier in the day I did a ping check, got my ~85ms consistently across 100 pings. Did a test just now, and it's consistently ~115ms.

So what's causing +30ms? Even in primetime in the past it might go up single digits, but not this huge amount.

Edit: nevermind, the packetloss is back again. It's 10:06AM in Japan right now, are they doing some kind of heavy workload testing in live servers right now?

Been getting this, myself, for the past couple weeks. Everything else runs perfectly except FF14, and the best I can get after switching between Data Centers a few times is "Good" when finally logging into Primal, when before, it never dipped below "Excellent". I was able to get a stable connection on the evening of 11/9, but nothing like it since.

Having this issue as well since Monday (11/9/2020). Constantly dropping connection in FFXIV only (S:0 repeatedly)- other online games, websites, and streaming are all fine and uninterrupted. Comcast, North East US.

Same issues here on Jenova, starting today around lunch CST. Major rubberbanding once every few seconds. Completely unplayable. I am a network engineer; I've run diagnostics on my home network, and ruled out any issues on my end. Zero packet loss to Google DNS over a 10 minute trace, and a rock solid 900 up/900 down fiber connection. All other games (including MMOs), streaming, et al, function normally, with no performance degradation. Using AT&T fiber, Southeastern US.

Meanwhile, traces to FFXIV show 50% packet loss. The issue occurs once I hit an Akamai-owned address block. Akamai is often used by MMOs to protect against DDoS attacks. Oddly, the connection icon within the FFXIV UI shows me with "Good" connection.

Having crazy lag spikes in game today. Here's my tests:

Tracing route to 204.2.229.98 over a maximum of 30 hops


3 10 ms 4 ms 4 ms 99.176.76.234
4 4 ms 4 ms 4 ms 99.15.141.86
5 8 ms 6 ms 5 ms 12.83.106.9
6 120 ms 85 ms 24 ms 12.122.29.186
7 106 ms 22 ms 132 ms 12.122.141.233
8 17 ms 17 ms 17 ms 192.205.36.158
9 20 ms 20 ms 20 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 31 ms 34 ms 31 ms ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 112 ms 83 ms 133 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 69 ms 70 ms 69 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 72 ms 72 ms 72 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 80 ms 75 ms 75 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 72 ms 72 ms 72 ms 204.2.229.234
16 73 ms 72 ms 72 ms 204.2.229.98

Trace complete.

Microsoft Windows [Version 10.0.19041.572]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\Me>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=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=228ms TTL=49
Reply from 204.2.229.98: bytes=32 time=134ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Request timed out.
Reply from 204.2.229.98: bytes=32 time=71ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=164ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=248ms TTL=49
Reply from 204.2.229.98: bytes=32 time=157ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=74ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=179ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=171ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=149ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=208ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=173ms TTL=49
Reply from 204.2.229.98: bytes=32 time=239ms TTL=49
Reply from 204.2.229.98: bytes=32 time=149ms TTL=49
Reply from 204.2.229.98: bytes=32 time=228ms TTL=49
Reply from 204.2.229.98: bytes=32 time=124ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=100ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=270ms TTL=49
Reply from 204.2.229.98: bytes=32 time=76ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=213ms TTL=49
Reply from 204.2.229.98: bytes=32 time=154ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=96ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=229ms TTL=49
Reply from 204.2.229.98: bytes=32 time=169ms TTL=49
Reply from 204.2.229.98: bytes=32 time=211ms TTL=49
Reply from 204.2.229.98: bytes=32 time=269ms TTL=49
Reply from 204.2.229.98: bytes=32 time=170ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=89ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=158ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=159ms TTL=49

Tracing route to 204.2.229.98 over a maximum of 30 hops


3 99.176.76.234
4 99.15.141.86
5 12.83.106.9
6 12.122.29.186
7 12.122.141.233
8 192.205.36.158
9 ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 204.2.229.234
16 204.2.229.98

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% 99.176.76.234
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% 99.15.141.86
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 12.83.106.9
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 12.122.29.186
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 12.122.141.233
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 192.205.36.158
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
0/ 100 = 0% |
10 58ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
0/ 100 = 0% |
11 95ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
0/ 100 = 0% |
12 99ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
0/ 100 = 0% |
13 98ms 1/ 100 = 1% 1/ 100 = 1% ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
0/ 100 = 0% |
15 96ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.234
0/ 100 = 0% |
16 95ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.98

Trace complete.

On Siren I've been getting severe lag around primetime ever since the latest maintenance (I say primetime as that's when I start playing and it seems to calm down later at night).

Not everyone seems to get lag but several of my FC mates do.

All of the above issues on Exodus. Rubber Banding. Disconnecting. Game freezing up. Was in Puppet's Bunker today and the entire alliance was complaining about it. Was practically unplayable.

Greetings everyone!

We appreciate you all for bringing this to our attention. For us to look into your concerns properly, we would like for you to provide additional details following our template below.

• Type of Issue/Feedback: (What type of issue are you encountering? Be as detailed as possible!)
• Name of your Internet Service Provider (ISP):
• State/Country:
• Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.)
• World Name:
• Frequency: (How often does the issue occur?)
• Traceroute records (optional) (Learn how to generate traceroute record)

Thank you!

It is like a Multiple stage issue.

1. You have to hope the launcher even works. - blank/partialy blank..etc
2. Then you have to hope that your character screen loads.
3. Then you have to hope you get into game sucessfully
4. Then you have to hope that you dont freeze/lock up/stutter


I started noticing it heavily after tuesday.
Alot of people seem to be having this issue, hopefully something is fixed sooon

Type of Issue/Feedback: Intermittent lag and disconnects. Dungeons and raids are virtually impossible because of the lag and disconnecting.

• Name of your Internet Service Provider (ISP): AT&T (Fiber optic service is what I have, next to highest speed available.)

• State/Country: Mobile, Alabama / USA

• Date/Time: After maintenance on Tuesday, November 10, 2020

• World Name: Mateus

• Frequency: (How often does the issue occur?) Constantly

Tracing route to 204.2.229.98 over a maximum of 30 hops


3 9 ms 11 ms 8 ms 99.176.76.234
4 4 ms 4 ms 4 ms 99.15.141.86
5 6 ms 9 ms 9 ms 12.83.106.9
6 141 ms 139 ms 23 ms 12.122.29.186
7 29 ms 21 ms 24 ms 12.122.141.233
8 17 ms 16 ms 17 ms 192.205.36.158
9 20 ms 59 ms 29 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 32 ms 33 ms 32 ms ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 * 139 ms * ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 71 ms 79 ms 72 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 78 ms 72 ms 72 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 172 ms 178 ms 79 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 72 ms 83 ms 78 ms 204.2.229.234
16 113 ms 188 ms 73 ms 204.2.229.98

Trace complete.

Type of Issue/Feedback: Disconnect and frequent launcher issuers when trying to reconnect. Massive latency spikes and rubberbanding if able to get in game.

• Name of your Internet Service Provider (ISP): AT&T

• State/Country: Tennessee, United States

• Date/Time: Daily since November 10

• World Name: Balmung

• Frequency: (How often does the issue occur?) Daily; usually around 6 EST give or take. Usually resolves after a few hours.

Tracing route to 204.2.229.98 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms {RouterModel-REMOVED} [192.168.1.150]
2 1 ms 1 ms 1 ms 172-11-84-1.lightspeed.nsvltn.sbcglobal.net [172.11.84.1]
3 5 ms 3 ms 3 ms 99.174.25.158
4 11 ms 15 ms 14 ms 12.122.148.254
5 10 ms 14 ms 14 ms attga22crs.ip.att.net [12.122.2.41]
6 11 ms 13 ms 14 ms attga402igs.ip.att.net [12.122.117.121]
7 9 ms 9 ms 25 ms 192.205.36.158
8 9 ms 9 ms 9 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
9 23 ms 22 ms 22 ms ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
10 66 ms * 66 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
11 * * * Request timed out.
12 68 ms 68 ms 68 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 69 ms 68 ms 76 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 68 ms 68 ms 68 ms 204.2.229.234
15 68 ms 68 ms 67 ms 204.2.229.98

Trace complete.


Every time I've checked, it seems like a somewhat consistent issue with the ntt.net server on hop 10 (ae-2.r25.snjsca04.us.bb.gin.ntt.net). I would wager a guess that anyone who does not have an issue is avoiding that server.

• Type of Issue/Feedback: Intermittent and sometimes severe rubberbanding and lag both in the open world and in duties (including trials, pvp, dungeons etc) -- often manifests as menus taking a while to come up, or even mini cactpot taking 30 seconds to get through.
• Name of your Internet Service Provider (ISP): Comcast
• State/Country: Alexandria, VA US
• Date/Time: Since the last maintenance.
• World Name: Siren
• Frequency: Every day since the most recent maintenance. I've been getting on around 7-8PM EST and it's usually pretty bad up until post-primetime (10-11pm and later).
• Traceroute records (optional)

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 10.0.0.1
2 11 ms 12 ms 15 ms 96.120.104.225
3 8 ms 9 ms 10 ms 24.124.182.41
4 8 ms 10 ms 11 ms 96.108.111.170
5 13 ms 9 ms 11 ms 96.110.6.5
6 10 ms 9 ms 18 ms ae-16-ar01.capitolhghts.md.bad.comcast.net [162.151.60.233]
7 11 ms 12 ms 12 ms be-31421-cs02.ashburn.va.ibone.comcast.net [96.110.40.21]
8 13 ms 21 ms 22 ms be-2211-pe11.ashburn.va.ibone.comcast.net [96.110.32.126]
9 13 ms 14 ms 12 ms 50.208.234.170
10 13 ms 14 ms 21 ms ae-10.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
11 72 ms 72 ms 81 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 110 ms 107 ms 107 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 115 ms 107 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 108 ms 115 ms 108 ms 204.2.229.234
15 109 ms * 109 ms 204.2.229.9

• Type of Issue/Feedback: Intermittent and sometimes severe rubberbanding and lag both in the open world and in duties (including trials, pvp, dungeons etc)
• Name of your Internet Service Provider (ISP): Comcast
• State/Country: Florida, United States
• Date/Time: Since the last maintenance.
• World Name: Mateus
• Frequency: Every day since the most recent maintenance. I've been getting on around 5-6PM EST and it's usually pretty bad up until primetime (8-9pm and later).
• Traceroute records (optional):
Tracing route to 204.2.229.11 over a maximum of 30 hops

1 2 ms 1 ms 2 ms 10.0.0.1
2 23 ms 12 ms 11 ms 96.120.97.141
3 10 ms 9 ms 10 ms 96.110.136.177
4 9 ms 11 ms 10 ms be-120-ar01.northdade.fl.pompano.comcast.net [68.87.162.105]
5 13 ms 12 ms 14 ms be-20214-cr02.miami.fl.ibone.comcast.net [68.86.90.205]
6 18 ms 12 ms 11 ms be-12274-pe01.nota.fl.ibone.comcast.net [68.86.82.154]
7 11 ms 11 ms 11 ms 50.242.151.66
8 115 ms 128 ms 116 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
9 10 ms 18 ms 11 ms ae-4.r22.miamfl02.us.bb.gin.ntt.net [129.250.4.88]
10 46 ms 61 ms 48 ms ae-2.r24.dllstx09.us.bb.gin.ntt.net [129.250.2.219]
11 45 ms 46 ms 44 ms ae-0.r25.dllstx09.us.bb.gin.ntt.net [129.250.2.80]
12 * * * Request timed out.
13 * * * Request timed out.
14 102 ms 133 ms 129 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 121 ms 102 ms 105 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 115 ms 121 ms 102 ms 204.2.229.234
17 114 ms 138 ms 118 ms 204.2.229.11

Trace complete.

This has so far for me, been resolved. What I did, will probably not work for you, or who knows. I just changed my dns on pc and router back to cloudflares public dns.

This should not have really fixed anything, and likely it didnt, and I'm just experiencing survivor bias. However, I now keep a constant lower latency with no lag.

Basically, from what I see from the posted Trace Routes, is it looks like NTT Communications' hardware in California is having the issues with one or more of the nodes.
As that is outside of your own hardware and ISP, it will be up to SE to forward the connection issues to NTT Com (which they likely have by now), and hope that NTT fixes their stuff.... so it is basically up to NTT.

Also, the reason this is effecting FF14 and maybe not your other games or internet activity, is likely because whatever you are connecting to is not passing through the effected hardware within NTT's network.
Further, changing DNS hosts or using a VPN, may be routing you traffic around the bad NTT nodes.

Think of the internet like a large road and highway map.
You can get from your house to another house across the map, using several different routes. (Paths)
Each of those routes may be a longer or shorter ride and have different road and traffic conditions that directly effect how long it will take you to get the the house. (Ping)
On some of the routes, there may be road work going on resulting in slow traffic (Packet Loss) or an accident resulting in lanes blocked (Time Outs)
At certain times, the traffic may be in a 'Rush Hour' situation, were all lanes are at a crawl (Network Hardware Overload) and you may have to get off that highway and take a back road (Network Traffic Offload/Re-route)

So, even though you can make it quickly to a house on one part of the map (Low Ping, Less Hops) another house route may be experiencing really bad traffic conditions (High Ping, Packet Loss, Time Outs) yet the issues is not with your car (Your Hardware) or the driveway at the housing you are going to (The Game Server). The issue it the conditions between your house and the house you want to go too, which unfortunately neither you nor SE have direct control of for correcting.

Good morning and thank you for posting on the Final Fantasy XIV Technical Support Forums.

Thank you for keeping us updated. As the original poster has stated the issue is resolved, we will be moving this thread to "Closed Concerns".

Good luck with your adventures through Eorzea!