Recent Lag Issues

[SteamedShoes]

I am in Boston connection to Leviathan. I just returned to playing again, and noticed I have been getting weird lag and very quick disconnects when in dungeons, raids, and trials. When I was playing about a year ago I did not have these issues, and I am using the same internet connection and computer as I was then. Here is the connection I am using. https://imgur.com/a/MVkcoH9 . I don't believe its lag or anything caused by the connection speed. It is my university wi-fi, which does had p2p ports blocked, but I don't believe this should be an issue, as it wasn't a year ago. Anyone else have this issue and know the fix?

[KRIPTICON]

I would love some light shed on this as well. I have been playing for years and never experienced the kind of lag spikes and rubber banding that I have been seeing in the last few days. Even at 2.0 launch when the servers were getting pounded it wasn't this bad. I feel like something abnormal must be going on. I haven't seen anything official at this point but the game is nearly unplayable at the moment.

[Tsathogguaz]

I'm having exactly the same problem. Constant 90002/90006 errors and stand-still screens no matter the content I'm doing, no matter the time of day or night. It's effectively impossible to stay connected to the server for more than 15m, and I'll usually get kicked within two minutes of logging on.

[SteamedShoes]

Ok so I looked into this myself since nobody seems to be able/want to help. It seems that its being caused by dropped packets to the data center. I ran ping 204.2.229.10 -nt 100 5 or 6 times while doing some alphascape raids and while in Rhalgar's Reach . I noticed that it would drop around 2-3 packets everyone session I ran pretty consistently. Its causing my to have small instances of everyone just standing still and nothing happening, and then goes back to normal. I have had a few experiences where for upwards of 10 seconds I have this as well. Where the game is running fine, but everyone just stands still and nothing happens.

[KRIPTICON]

Ok so I looked into this myself since nobody seems to be able/want to help. It seems that its being caused by dropped packets to the data center. I ran ping 204.2.229.10 -nt 100 5 or 6 times while doing some alphascape raids and while in Rhalgar's Reach . I noticed that it would drop around 2-3 packets everyone session I ran pretty consistently. Its causing my to have small instances of everyone just standing still and nothing happening, and then goes back to normal. I have had a few experiences where for upwards of 10 seconds I have this as well. Where the game is running fine, but everyone just stands still and nothing happens.

I am having the exact same problem you are describing. There are also other threads on the issue written within the past week or less. I did read a moderator response to a thread featuring an image of a trace route that a player ran on their data center/server connection. Unfortunately, the response basically blamed the players ISP so it was not helpful. For my part, this is a new issue and nothing on my end has changed. This goes beyond a simple ping or latency issue. I'm getting in game freezes lasting several seconds at a time. I'm dying in dungeons because my game is freezing during boss mechanics. It's not just instanced content either. I couldn't even log out the other day because the game was just sitting there after the UI command rather than exiting the game world. This is 100% not normal.

[Stjevne]

I've been noticing frequent packet loss lately while playing FFXIV. Every other game runs fine. Running a tracert/pathping to FF servers shows a significant packet loss at an NTT router hop along the way, and without routing through a proxy and praying for a different routing table, there's not much I can do, or so I'm told. I would love to be proven wrong, however. I'm not sure if Squeenix has the capability of contacting the network administration for that particular node, but wishful thinking couldn't hurt.

Here's the raw. I have a Google Wi-Fi router connected to a Motorola Surfboard modem on Comcast.

Tracing route to 204.2.229.9 over a maximum of 30 hops

0 VIDNE-MKII.lan [192.168.86.21]
1 testwifi.here [192.168.86.1]
2 192.168.0.1
3 96.120.9.181
4 96.108.119.45
5 96.110.24.214
6 96.110.25.65
7 be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
8 be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
9 be-1302-cs03.ashburn.va.ibone.comcast.net [96.110.32.177]
10 be-2307-pe07.ashburn.va.ibone.comcast.net [96.110.32.194]
11 ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
12 ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
13 ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
14 ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
16 ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
17 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 204.2.229.234
19 204.2.229.9

Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 VIDNE-MKII.lan [192.168.86.21]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% testwifi.here [192.168.86.1]
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
3 110ms 0/ 100 = 0% 0/ 100 = 0% 96.120.9.181
0/ 100 = 0% |
4 135ms 0/ 100 = 0% 0/ 100 = 0% 96.108.119.45
0/ 100 = 0% |
5 126ms 0/ 100 = 0% 0/ 100 = 0% 96.110.24.214
0/ 100 = 0% |
6 123ms 0/ 100 = 0% 0/ 100 = 0% 96.110.25.65
0/ 100 = 0% |
7 127ms 0/ 100 = 0% 0/ 100 = 0% be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
0/ 100 = 0% |
8 138ms 0/ 100 = 0% 0/ 100 = 0% be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
0/ 100 = 0% |
9 145ms 0/ 100 = 0% 0/ 100 = 0% be-1302-cs03.ashburn.va.ibone.comcast.net [96.110.32.177]
0/ 100 = 0% |
10 114ms 0/ 100 = 0% 0/ 100 = 0% be-2307-pe07.ashburn.va.ibone.comcast.net [96.110.32.194]
0/ 100 = 0% |
11 134ms 0/ 100 = 0% 0/ 100 = 0% ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
0/ 100 = 0% |
12 148ms 0/ 100 = 0% 0/ 100 = 0% ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
0/ 100 = 0% |
13 151ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
0/ 100 = 0% |
14 207ms 0/ 100 = 0% 0/ 100 = 0% ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
0/ 100 = 0% |
15 215ms 0/ 100 = 0% 0/ 100 = 0% ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
0/ 100 = 0% |
16 201ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
0/ 100 = 0% |
17 --- 100/ 100 =100% 100/ 100 =100% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
0/ 100 = 0% |
18 206ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.234
0/ 100 = 0% |
19 252ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.9

Trace complete.