game lag during peak hours since last patch - eu datacenter.

[mutantx]

my ping shows around 32ms - at any time of day/night, then i spent an hour on the phone with 2nd line support at my isp looking through tracerts together - where they said the issue is with square enix.
secondly i tracert the server ip (195.82.50.52) at different times of the day - and i noticed and verified this with 4 other people who live across eu/uk with different isps that the ip (195.82.50.234) which is just before the final ip has a crazy ms range

11 am gmt - 370ms
1 pm gmt -550ms
7pm gmt -1332ms.........
1am gmt - 32ms .........

As you can see at 7pm the game becomes totally unplayable for me - even using wtfast during these times it reports a 500 + ping (still unplayable) however when i test it at 1am wtfast shows 32ms ping - mmmm that buttery smooth game play : )
and i can even play without wtfast but i get a bit more overhead from my isp. What i don't understand is why some like myself seem to be affected at peek times while others are not.

[Norna]

Is 14:00 GMT (2 in the afternoon for those with 12 hour clocks) considered a peak hour? Because using the IP addresses from ARRstatus.com, this is what a 30 second PingPlotter trace had to say about things:

Cerberus and Odin:

Phoenix and Zodiark:

Maybe there is some kind of trouble at the EU data center or something? Because going from 60 to 1300+ in ping is kind of... Yeah. Oh and of course there is packet loss (PL%), which most MMOs can't handle very well.

[Verius_Nox]

We get it on the US datacenter, too. I experience a lot of lag during peak hours on Balmung. It's pretty much neutered my ability to play.

[Nghthawk]

We get it on the US datacenter, too. I experience a lot of lag during peak hours on Balmung. It's pretty much neutered my ability to play.

In looking at the thread they created mentioning the latency complaints on NA Data Center, there is a common theme I've seen with their ISP: Comcast

Not everyone is experiencing the same issue latency complaints.

[Verius_Nox]

In looking at the thread they created mentioning the latency complaints on NA Data Center, there is a common theme I've seen with their ISP: Comcast

Not everyone is experiencing the same issue latency complaints.

That's all well and good, except this is the only game this type of issue is experienced. Every other game I've played at peak hours has had 0 issues.

[MatthiasS]

In looking at the thread they created mentioning the latency complaints on NA Data Center, there is a common theme I've seen with their ISP: Comcast

Not everyone is experiencing the same issue latency complaints.

To be fair, Comcast is also the largest ISP in the US.

[Raist]

Something definitely appears to be up with 195.85.50.234. Traced/pinged from routers in different areas (Hamburg, Paris, California) and they all get a nasty response over a full second:

core1.ham1.he.net> traceroute 195.82.50.9 source-ip 216.218.252.216 numeric
  
Tracing the route to IP node (195.82.50.9) from 1 to 30 hops

  1    77 ms   46 ms   24 ms 184.105.80.97
  2   153 ms  152 ms  153 ms 213.248.72.145
  3   151 ms  163 ms  154 ms 62.115.140.172
  4   170 ms  158 ms  165 ms 62.115.136.125
  5   174 ms  175 ms  174 ms 213.248.65.121
  6   175 ms  174 ms  175 ms 62.115.137.227
  7   174 ms  175 ms  174 ms 62.115.32.110
  8   175 ms  174 ms  175 ms 195.82.60.29
  9   174 ms  175 ms  173 ms 195.82.61.14
 10  1450 ms 1374 ms 1500 ms 195.82.50.234
 11   174 ms  175 ms  212 ms 195.82.50.9
# Entry cached for another 47 seconds.

core1.par2.he.net> traceroute 195.82.50.9 source-ip 216.218.252.184 numeric
  
Tracing the route to IP node (195.82.50.9) from 1 to 30 hops

  1   172 ms  175 ms  174 ms 62.115.35.249
  2   150 ms  158 ms  145 ms 62.115.138.126
  3   169 ms  174 ms  175 ms 80.91.246.180
  4   174 ms  175 ms  174 ms 62.115.137.239
  5   175 ms  174 ms  175 ms 62.115.32.110
  6   174 ms  175 ms  174 ms 195.82.60.29
  7   175 ms  177 ms  172 ms 195.82.61.14
  8  1474 ms 1506 ms 1542 ms 195.82.50.234
  9   181 ms  204 ms  190 ms 195.82.50.9
# Entry cached for another 47 seconds.

core1.fmt1.he.net> traceroute 195.82.50.9 source-ip 216.218.252.161 numeric
  
Tracing the route to IP node (195.82.50.9) from 1 to 30 hops

  1    10 ms   <1 ms   <1 ms 184.105.213.66
  2    <1 ms   <1 ms   <1 ms 80.239.167.173
  3    78 ms  147 ms   76 ms 80.91.253.1
  4   100 ms   81 ms   86 ms 80.91.254.176
  5   199 ms  170 ms  268 ms 62.115.139.16
  6   233 ms  176 ms  174 ms 62.115.137.227
  7   179 ms  170 ms  180 ms 62.115.32.110
  8   170 ms  173 ms  173 ms 195.82.60.29
  9   172 ms  183 ms  172 ms 195.82.61.14
 10  1501 ms 1500 ms 1438 ms 195.82.50.234
 11   179 ms  194 ms  228 ms 195.82.50.9
# Entry cached for another 51 seconds.

core1.ham1.he.net> ping 195.82.50.234 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.50.234, timeout 5000 msec, TTL 64
Reply from 195.82.50.234   : bytes=16 time=1351ms TTL=245
Reply from 195.82.50.234   : bytes=16 time=1498ms TTL=243
Reply from 195.82.50.234   : bytes=16 time=1500ms TTL=245
Reply from 195.82.50.234   : bytes=16 time=1376ms TTL=244
Reply from 195.82.50.234   : bytes=16 time=1396ms TTL=245
Success rate is 100 percent (5/5), round-trip min/avg/max=1351/1424/1500 ms.
# Entry cached for another 50 seconds.

core1.par2.he.net> ping 195.82.50.234 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.50.234, timeout 5000 msec, TTL 64
Reply from 195.82.50.234   : bytes=16 time=1289ms TTL=249
Reply from 195.82.50.234   : bytes=16 time=1320ms TTL=249
Reply from 195.82.50.234   : bytes=16 time=1324ms TTL=249
Reply from 195.82.50.234   : bytes=16 time=1340ms TTL=249
Reply from 195.82.50.234   : bytes=16 time=1275ms TTL=249
Success rate is 100 percent (5/5), round-trip min/avg/max=1275/1309/1340 ms.
# Entry cached for another 51 seconds.

core1.fmt1.he.net> ping 195.82.50.234 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.50.234, timeout 5000 msec, TTL 64
Reply from 195.82.50.234   : bytes=16 time=1471ms TTL=247
Reply from 195.82.50.234   : bytes=16 time=1498ms TTL=245
Reply from 195.82.50.234   : bytes=16 time=1430ms TTL=245
Reply from 195.82.50.234   : bytes=16 time=1493ms TTL=244
Reply from 195.82.50.234   : bytes=16 time=1450ms TTL=247
Success rate is 100 percent (5/5), round-trip min/avg/max=1430/1468/1498 ms.
# Entry cached for another 52 seconds.

Directly pinging the hop right before it (195.82.61.14) is still more "normal" (does have a bit much jitter, but not nearly as bad), but when you ping 195.82.50.234 directly it goes to pot:

core1.ham1.he.net> ping 195.82.61.14 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.61.14, timeout 5000 msec, TTL 64
Reply from 195.82.61.14    : bytes=16 time=174ms TTL=52
Reply from 195.82.61.14    : bytes=16 time=221ms TTL=54
Reply from 195.82.61.14    : bytes=16 time=178ms TTL=55
Reply from 195.82.61.14    : bytes=16 time=175ms TTL=53
Reply from 195.82.61.14    : bytes=16 time=174ms TTL=52
Success rate is 100 percent (5/5), round-trip min/avg/max=174/184/221 ms.
# Entry cached for another 56 seconds.

core1.par2.he.net> ping 195.82.61.14 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.61.14, timeout 5000 msec, TTL 64
Reply from 195.82.61.14    : bytes=16 time=35ms TTL=59
Reply from 195.82.61.14    : bytes=16 time=22ms TTL=59
Reply from 195.82.61.14    : bytes=16 time=25ms TTL=59
Reply from 195.82.61.14    : bytes=16 time=27ms TTL=59
Reply from 195.82.61.14    : bytes=16 time=22ms TTL=59
Success rate is 100 percent (5/5), round-trip min/avg/max=22/26/35 ms.
# Entry cached for another 57 seconds.

core1.fmt1.he.net> ping 195.82.61.14 numeric count 5
  Sending 5, 16-byte ICMP Echo to 195.82.61.14, timeout 5000 msec, TTL 64
Reply from 195.82.61.14    : bytes=16 time=178ms TTL=57
Reply from 195.82.61.14    : bytes=16 time=210ms TTL=57
Reply from 195.82.61.14    : bytes=16 time=189ms TTL=57
Reply from 195.82.61.14    : bytes=16 time=198ms TTL=57
Reply from 195.82.61.14    : bytes=16 time=174ms TTL=57
Success rate is 100 percent (5/5), round-trip min/avg/max=174/189/210 ms.
# Entry cached for another 59 seconds.

Time to submit a formal ticked to SE I guess.

[mutantx]

yes - trying to do some Ravana farm atm as ninja and its so bad ... i lock up for 5-10 seconds even miss lb heals on the party and have a constant jitter/lag - funny thing is everyone watch that ping drop from 1300 to 30ms from about 12-1am ish - and game play be super smooth. again im fine in any other game - or streaming etc its just ffxiv in prime play hours.

it would be nice in fact if people could also verify my claim to smooth gameplay in the early hours - and a drop in ping to that ip. also this issue has only been noticed by me at least since the last patch.

[Raist]

Ticket formally submitted to SE. #5596288

Hope they can get someone on it soon for your guys

[mutantx]

Thank you Raist