Bad lag again with NTT's NA server network

[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

[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.

[TaleraRistain]

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.

Yeah I was talking to my husband about it last night. He read a book called Tokyo Vice and I guess the gentlemen in it described that sometimes these things in Japan are monopolies in everything but name only. Everyone agrees that X will handle this or Y will handle this. And of course when you have a setup like that, the offender has no impetus to change. Their US servers were in another place in the past, though, so if there is another option then I would hope they'd at least look into it.

[brnslpy]

Its fascinating the differences between two traceroutes from the same physical location but two different ISPs -- yet still going through similar NTT nodes once it gets to California:

ATT:

7 cgcil402igs.ip.att.net (12.122.132.197) 8.477 ms 8.791 ms 8.019 ms
8 192.205.32.194 (192.205.32.194) 15.443 ms 7.090 ms 20.245 ms
9 ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239) 7.508 ms 7.972 ms 8.069 ms
10 * ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 55.329 ms 60.330 ms
11 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 111.620 ms 113.681 ms 112.283 ms
12 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 113.674 ms 113.522 ms 114.396 ms
13 * * 204.2.29.241 (204.2.29.241) 114.096 ms

Comcast:

9 be-2311-pe11.350ecermak.il.ibone.comcast.net (96.110.33.202) 19.727 ms
10 ae-3.a06.chcgil09.us.bb.gin.ntt.net (129.250.8.65) 29.949 ms 23.228 ms 21.926 ms
11 ae-10.r23.chcgil09.us.bb.gin.ntt.net (129.250.3.37) 45.485 ms 26.543 ms 21.283 ms
12 ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 65.812 ms 74.105 ms 68.419 ms
13 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 70.537 ms 71.024 ms 74.866 ms
14 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 67.851 ms 73.041 ms 70.355 ms

Something is definitely going on between NTT + ATT - who knows whose fault it is at this point but good grief can't someone update their routing tables to get around their own congestion? *sigh*