Seems like no one cares about the lag

[NaohaLanbatal]

The game has been completely unplayable the past few days. Once again, it is that one NTT hop in California. The rubberbanding is so severe I can't do anything. The game just pauses for 10, 20, even 30 seconds at a time, and that happens every few seconds.

[Lehas]

this server lag in Brynhildr is so bloody frustrating... Getting upwards to one minute lag spikes while in dungeons and just lousing about different areas... I had a better experience waiting in queue for 4000+ people then when they limited the amount of people coming into the servers. Only happens in ff14, all other games are fine.

[Jconix]

Ugh.. just when I thought it was finally fixed. Ping spike has happened.

Considering almost an entire week without it would be less bad but man x_x;

[joolzy]

huge lag spikes again tonight. same time, every time.

[Jashynvald]

Yeah, it was going so well for the week I was daring to hope that a fix was implemented.

[Jconix]

Ping spike starting an hour and 25 minute earlier than usual.@_@;; Ugh I hope this doesn't continue forward during this upcoming week...

[joolzy]

lag also started much earlier tonight, and is much worse than usual. heavy spikes every 30s

[NevaehQuest]

I am here...funny seeing so many new forum user just here talking about the same lag
.

[PeachCrisps]

Adding my experience. It seems to happen to me every night around 7:30 or 8 PM CST and lasts for an hour or longer. I can clear it up immediately by turning my VPN on, but I shouldn't have to rely on that.

Tracing route to 204.2.229.105 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2     1 ms     1 ms     1 ms  45-20-24-1.lightspeed.hstntx.sbcglobal.net [45.20.24.1]
  3     1 ms     1 ms     1 ms  71.149.39.122
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    12 ms    12 ms     7 ms  32.130.16.9
  8    10 ms    11 ms    12 ms  gar25.dlstx.ip.att.net [12.122.85.233]
  9     *       71 ms    58 ms  ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
 10     *       65 ms    80 ms  ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
 11    44 ms    46 ms    45 ms  ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12   202 ms   218 ms     *     ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
 13   206 ms   202 ms   207 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 14   209 ms   192 ms   202 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
 15   211 ms     *        *     204.2.229.230
 16     *      183 ms     *     204.2.229.105
 17   206 ms   174 ms   167 ms  204.2.229.105

Trace complete.

Everything is fine until it jumps onto NTT's servers where the reliability of the connection falls dramatically.

[joolzy]

Adding my experience. It seems to happen to me every night around 7:30 or 8 PM CST and lasts for an hour or longer. I can clear it up immediately by turning my VPN on, but I shouldn't have to rely on that.

Tracing route to 204.2.229.105 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2     1 ms     1 ms     1 ms  45-20-24-1.lightspeed.hstntx.sbcglobal.net [45.20.24.1]
  3     1 ms     1 ms     1 ms  71.149.39.122
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    12 ms    12 ms     7 ms  32.130.16.9
  8    10 ms    11 ms    12 ms  gar25.dlstx.ip.att.net [12.122.85.233]
  9     *       71 ms    58 ms  ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
 10     *       65 ms    80 ms  ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
 11    44 ms    46 ms    45 ms  ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12   202 ms   218 ms     *     ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
 13   206 ms   202 ms   207 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 14   209 ms   192 ms   202 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
 15   211 ms     *        *     204.2.229.230
 16     *      183 ms     *     204.2.229.105
 17   206 ms   174 ms   167 ms  204.2.229.105

Trace complete.

Everything is fine until it jumps onto NTT's servers where the reliability of the connection falls dramatically.

what vpn are you using if i may ask?