Constant 90002 Errors when in Instances

[zookalicious]

System - PC
Server - Cactuar / Aether
How long has issue been occurring - started 3 days ago. No changes to our local network.
Issue description - Constant 90002 errors when in instanced content (dungeons raids etc). Two players are on the same network, one disconnects rarely (every 20 minutes or so), the other constantly (every minute). If playing in non-instanced overworld, there are no disconnects, or they are very rare.
Troubleshooting steps performed - PC restart, router restart, port forwarding, firewall check, VPN. None have helped.


Problem impact - Game is unplayable. Cannot proceed with any story or other content. We are both considering unsubbing if this does not improve as the game cannot be played.

Tracert results with VPN:
Tracing route to 204.2.229.9 over a maximum of 30 hops

1 29 ms 45 ms 32 ms 10.8.11.1
2 34 ms 41 ms 42 ms 199.229.249.254
3 45 ms 35 ms 32 ms 199.229.249.6
4 33 ms 45 ms 36 ms ae7-103.cr0-mtl1.ip4.gtt.net [98.124.173.101]
5 79 ms 52 ms 44 ms et-0-0-35.cr4-nyc3.ip4.gtt.net [89.149.182.238]
6 41 ms 48 ms 47 ms ae-7.r07.nycmny01.us.bb.gin.ntt.net [129.250.8.13]
7 * 41 ms * ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
8 99 ms 101 ms 101 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
9 101 ms 130 ms 104 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
10 119 ms 119 ms 118 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 122 ms 122 ms 121 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
12 121 ms 125 ms 123 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
13 122 ms 123 ms 122 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 121 ms 123 ms 127 ms 204.2.229.234
15 125 ms 122 ms 124 ms 204.2.229.9

Trace complete.


Tracert results without VPN:
Tracing route to 204.2.229.9 over a maximum of 30 hops

1 7 ms 10 ms 6 ms INTEL_CE_LINUX [192.168.0.1]
2 17 ms 17 ms 16 ms 99.234.120.1
3 18 ms 16 ms 16 ms 8079-dgw02.hnsn.rmgt.net.rogers.com [66.185.91.205]
4 16 ms 16 ms 12 ms 209.148.232.229
5 29 ms 23 ms 17 ms 9402-cgw01.bloor.rmgt.net.rogers.com [209.148.235.233]
6 33 ms 37 ms 37 ms 209.148.229.226
7 40 ms 34 ms 38 ms 209.148.231.50
8 35 ms 43 ms 47 ms ae-11.r07.nycmny01.us.bb.gin.ntt.net [140.174.28.13]
9 30 ms 33 ms 34 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
10 109 ms 103 ms * ae-4.r22.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 104 ms 101 ms 106 ms ae-0.r23.sttlwa01.us.bb.gin.ntt.net [129.250.6.30]
12 106 ms 108 ms 105 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 117 ms 122 ms 118 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
14 111 ms 121 ms 109 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
15 117 ms 116 ms 123 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 118 ms 109 ms 114 ms 204.2.229.234
17 111 ms 110 ms 114 ms 204.2.229.9

Trace complete.

Ping results with VPN:

Pinging 204.2.229.9 with 32 bytes of data:
Reply from 204.2.229.9: bytes=32 time=115ms TTL=52
Reply from 204.2.229.9: bytes=32 time=113ms TTL=52
Reply from 204.2.229.9: bytes=32 time=120ms TTL=52
Reply from 204.2.229.9: bytes=32 time=200ms TTL=52

Ping statistics for 204.2.229.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 200ms, Average = 137ms


Ping results with outVPN:
Pinging 204.2.229.9 with 32 bytes of data:
Reply from 204.2.229.9: bytes=32 time=133ms TTL=52
Reply from 204.2.229.9: bytes=32 time=109ms TTL=52
Reply from 204.2.229.9: bytes=32 time=125ms TTL=52
Reply from 204.2.229.9: bytes=32 time=113ms TTL=52

Ping statistics for 204.2.229.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 133ms, Average = 120ms

[zookalicious]

Somehow the issue seems even worse today. I tried doing one roulette and could only play for 10-15 seconds at a time between DCs.

[zookalicious]

Another update. I've been researching all over trying to figure out how to fix this. Surprise surprise, it looks like NTT nodes are dropping massive amounts of packets (almost 50%!!). Everything other game is fine though, so why on earth is FFXIV so aggressive about dropping your connection? Is there any possible fix for this?

[zookalicious]

Despite these nodes dropping packets, my attempts to get around the nodes via VPN have not resulted in any real difference to the amount of 90002 errors I'm getting.

[zookalicious]

Tried mudfish and other VPNs again. No improvement. Running out of things to try, so I'm really hoping that maintenance today fixes things...

[zookalicious]

So since maintenance on Monday, I have not experienced a single DC (during about 6 hours of game play over 3 days). I would like to clarify that I made no changes on my end during the maintenance, so whatever the issue was, I have to assume it was not on my end, but rather an issue with the FFXIV servers.

While it's possible that coincidentally the third party node sorted itself out at the same time that's not all that likely.

I'm a bit frustrated that any attempt at receiving support for this issue simply pushed the blame onto my configuration or my ISP. While I'm sure that's a common cause of these DC issues, it doesn't seem to be the case this time.

Anyways, this thread can be closed.