Bad lag again with NTT's NA server network

[Lahtori]

Hmm... Mine are still okay. There's two nodes that jump to 90ms, but at least it's not all nodes.

[Janyd]

Hmm... Mine are still okay. There's two nodes that jump to 90ms, but at least it's not all nodes.

Hmm, an interesting discrepancy from hops 10 and on. The IP address ending in 18 has the lowest ms of all the Sacramento nodes. How curious.

[Lahtori]

It's back in style. The hopium train has derailed before leaving the station.

[TaleraRistain]

Right on schedule, it's back on the BS

5 9 ms 12 ms 13 ms 32.130.17.75
6 8 ms 16 ms 13 ms cgcil402igs.ip.att.net [12.122.133.161]
7 8 ms 9 ms 8 ms 192.205.32.194
8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 * 55 ms 55 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 111 ms 110 ms 107 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 111 ms 108 ms 100 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 109 ms 109 ms 110 ms 204.2.29.6

[Kwehvehpeh]

It's back in style. The hopium train has derailed before leaving the station.

Well, looks like VPN purchasing it is!

[HoneyLamp]

I use AT&T fiber, and same thing happens here, lag and packet loss between 12:00pm to 12:00am EST.
Have sent the report. Hopefully they'll get it fixed before patch 6.4 release.

8 35 ms 43 ms 29 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
9 38 ms 36 ms 37 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
10 38 ms 37 ms * ae-1.r20.dllstx14.us.bb.gin.ntt.net [129.250.3.54]
11 110 ms 114 ms 113 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 120 ms 122 ms 122 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 114 ms 121 ms 118 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 123 ms 122 ms 121 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 120 ms 118 ms 121 ms 204.2.29.8

[Janyd]

Hopefully. Thanks for your report, HoneyLamp.
They do help keep the pressure on all parties involved to get things done.

But I will admit, five days of this is more than unacceptable. It's abysmal, and a long list of words that I can't say in public.

[Lahtori]

I just tweeted FFXIV again, and this time gave NTT a tweet too. Honestly, if it's not resolved by patch day, it may be time to look at the dreaded "game news". I refuse to believe there is no power SE cannot use to push NTT into action - it's their nodes.

Also got my partner to submit his own report to SE.

I'm just at a loss of words. Five days and on going.

[TaleraRistain]

Between this and being affected by the sound issue during 6.0 where I couldn't play with sound or it was horrendously garbled, it's definitely been a rough few months for me with this game. Worst I've experienced in 9 years of playing. I'm not angry, just disappointed. I know this isn't in SE's direct control and hope they can leverage some influence. Or maybe move to a different option if that's possible if the issue is with NTT and NTT isn't going to give US customers with certain ISPs good service.

[Janyd]

Honestly, I hope they reconsider their deal with NTT in North America. Or at least, SE and/or AT&T should give NTT an ultimatum due to these problems.
Either fix them immediately or find another (more competent) partner for these nodes.