Lagasaurus Rex

[Plastic_Fork]

It's not just you. It's everyone. People have been posting about it for months. I live in central USA. Same issue every night around 7pm CST-10pm CST. The problem is California. The high latency starts as soon as it reaches San Jose, CA or Sacramento, CA. I have zero latency or lag issues with anything else I do, including other games, latency tests, websites, streaming, or anything else. It's just FF14 and the nodes on the way to their servers. No lag during daytime hours weekdays or weekends. Just this time of the evening/night. Sometimes it's consistent, sometimes it only lasts for a little bit, then the high latency returns a little later.

I'll post again for the sake of posting, but nothing's been done anywhere to resolve it and it's been an issue for me for almost a year now.

• Platform: PC (Windows 7 Ultimate x64)
• Nature of the latency: high latency at evening hours the same times every night
• Type of connection: wired (Comcast)
• Other programs running while the game is playing (if any): none
• Everything you have tried to resolve the issue:

  reinstalling FF14, swapping network cards, updating drivers, relaxing security, forwarding ports, game running as Administrator, game runs in DX11, pretty much everything else that's been suggested

• Error Code (if any): none

Traceroute from about 30 minutes ago:

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.10
  2    10 ms    11 ms    10 ms  96.120.53.45
  3    13 ms    11 ms    13 ms  68.86.195.241
  4    16 ms    16 ms    15 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  5    31 ms    25 ms    23 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  6    31 ms    23 ms    22 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  7    23 ms    22 ms    24 ms  50.242.151.58
  8    23 ms    29 ms    26 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
  9    32 ms    23 ms    27 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 10    40 ms    39 ms    47 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 11    97 ms   109 ms   109 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12   197 ms   209 ms   198 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 13     *      202 ms   208 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 14     *      203 ms   191 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net 129.250.195.46]
 15   124 ms   102 ms   118 ms  204.2.229.234
 16   203 ms   210 ms   200 ms  204.2.229.96

Trace complete.

The high latency subsided a little bit. And came back.
Here's another traceroute 90 minutes later. Raids, dungeons, and PvP are totally unplayable.

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.10
  2    18 ms     9 ms    15 ms  96.120.53.45
  3    11 ms    11 ms    12 ms  68.86.195.241
  4    24 ms    68 ms    16 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  5    25 ms    23 ms    23 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  6    23 ms    31 ms    27 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  7    24 ms    22 ms    23 ms  50.242.151.58
  8    27 ms    23 ms    22 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
  9    30 ms    29 ms    28 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 10    41 ms    39 ms    40 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 11   174 ms   160 ms   181 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12   188 ms   198 ms   192 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 13   205 ms     *      199 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 14   194 ms   198 ms   195 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 15   191 ms   174 ms   169 ms  204.2.229.234
 16     *      205 ms   195 ms  204.2.229.96

Trace complete.

Here's another traceroute done 30 minutes later while things calmed back down.
This is what a normal traceroute and latency looks like for me for my server when the high latency spikes aren't happening in California.

Tracing route to 204.2.229.96 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.10
  2    11 ms     9 ms    11 ms  96.120.53.45
  3    13 ms    12 ms    11 ms  68.86.195.241
  4    16 ms    16 ms    16 ms  ae-32-ar02.goodslettvll.tn.nash.comcast.net [162.151.23.26]
  5    26 ms    24 ms    23 ms  be-22909-cr02.56marietta.ga.ibone.comcast.net [68.86.91.245]
  6    22 ms    22 ms    32 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254]
  7    23 ms    24 ms    23 ms  50.242.151.58
  8    25 ms    23 ms    23 ms  ae-11.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
  9    35 ms    22 ms    23 ms  ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
 10    48 ms    40 ms    40 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
 11    78 ms    78 ms    90 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12    82 ms    83 ms    81 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 13    81 ms    80 ms    82 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 14    82 ms    82 ms    88 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 15    80 ms    83 ms    83 ms  204.2.229.234
 16    85 ms    88 ms    83 ms  204.2.229.96

Trace complete.