Bad lag again with NTT's NA server network

[Janyd]

Just did some quick ping commands while Cloudflare WARP was Disabled, at 10:40 AM Central.

First one is to the main NA Datacenter Lobby, the second is to the Aether Datacenter:

Pinging 204.2.29.122 with 32 bytes of data:
Reply from 204.2.29.122: bytes=32 time=63ms TTL=49
Reply from 204.2.29.122: bytes=32 time=73ms TTL=49
Reply from 204.2.29.122: bytes=32 time=58ms TTL=49
Reply from 204.2.29.122: bytes=32 time=59ms TTL=49

Ping statistics for 204.2.29.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 73ms, Average = 63ms


Pinging 204.2.29.6 with 32 bytes of data:
Reply from 204.2.29.6: bytes=32 time=64ms TTL=50
Reply from 204.2.29.6: bytes=32 time=64ms TTL=50
Reply from 204.2.29.6: bytes=32 time=62ms TTL=50
Reply from 204.2.29.6: bytes=32 time=58ms TTL=50

Ping statistics for 204.2.29.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 64ms, Average = 62ms


With Cloudflare WARP Enabled, these are usually both around 70ms, so still acceptable.

[Illyrian94]

So far looking alright for me as well (Indiana, ATT fiber). Every other day this week when I checked over my lunch ping values were in the 100ms range w/ lots of packet loss.



Fingers crossed!

[ntt_routing_is_an_issue]

From what I see it was only the lobby server that stopped responding for a very short time. There was even a lodestone post about that.

https://na.finalfantasyxiv.com/lodes...ef015671754060

Lobby server stopped responding between 2:52 and 3:04am EST. Monitored world server didn't.
Packet loss also literally stopped at 2am EST like clockwork.


I'm not getting my hopes up though.

If they can keep it stable going forward I'll celebrate. This "fixed for a day" or "fixed for a week" is getting old

[Janyd]

Don't celebrate just yet, folks.

Tracing route to 204.2.29.122 over a maximum of 30 hops


8 29 ms 30 ms 26 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 27 ms 27 ms 33 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 81 ms 80 ms 82 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 100 ms 117 ms 96 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 112 ms 108 ms 104 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 109 ms 103 ms 110 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 72 ms * 204.2.29.241
15 97 ms 97 ms 106 ms 204.2.29.122

[Krojack]

I lost power at my place for about 2 1/2 hours so I don't have ping graphs for when the lag starts.

Power back and graphs are graphing. Looks like the pings are still bad. It's hovering from 80-100ms. Like in the past, I don't expect packet loss to start till 1 or 2pm. So in about an hour we will see.

But so far not looking good.

[Janyd]

Dang, and I was hoping the servers taking a dump last night would get rid of this garbage.

Alas, back to our posts we go. Remain vigilant, and keep hounding AT&T, NTT, and Square Enix. Pressure and social media callouts work.

[Illyrian94]

Looks like I spoke too soon. NTT nodes spiked to 100+ms of latency and packet loss has started.
Kinda doubt they'll get this fixed by 6.4 at this rate.

[Janyd]

They'd have to act quickly before maintenance if they want to save face.
That, or explicitly take time during server maintenance to get with NTT and AT&T to fix and test things.

One has to hope a proper Lodestone post about this serious problem would come if it persists into 6.4.

[Kwehvehpeh]

Looks like I spoke too soon. NTT nodes spiked to 100+ms of latency and packet loss has started.
Kinda doubt they'll get this fixed by 6.4 at this rate.

That is really heartbreaking to see.

[Lahtori]

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