Bad lag again with NTT's NA server network

[brnslpy]

I'm skeptical, but I'll keep my tracer and ping tracker running today.

Also skeptical. Still got a couple more hours until that 12-hour cycle starts again.

FWIW, in my haste to get *something* working in readiness for 6.4, I signed up for a different ISP, Xfinity, and put my PS5 on that service last night (plus a laptop to run traceroute/ping)

On Xfinity, pings/latency stayed around 70ms and no lag or rubberbanding.

I did a couple traceroutes at the same time, one going out of ATT Fiber and one going out Xfinity but same physical location / house.

They both went through some of the nodes we've been seeing, like going through the Chicago, San Jose and Sacramento NTT nodes and included IPs like 128.241.2.18 and 129.250.4.239 but Xfinity never went through 129.250.7.57.

The ATT connection had 20% packet loss and 120ms pings spiking to 200ms but the Xfinity connection was perfectly fine.

[Lahtori]

TY SE for the prompt response especially considering the patch is around the corner. ^_^ I hope everyone has been similarly fixed.

Not to be a downer, but prompt isn't the word I'd use.

I'm very skeptical that the issue has actually been resolved. But I hope it has. Time will tell, it's usually around now that it starts to act up. I'll run my own tracert in a few hours and report back.

[Krojack]

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.

[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

[KSarv]

I cancelled my sub because of this, but have a few days left of play time. I'm also skeptical about last nights crash/reset/outage being the permanent fix, but it seems to be working fine for me right now. Time will only tell.

[Kwehvehpeh]

I saw on the lodestone that this issue was fixed! Can anyone confirm that they aren't having issues around prime time?

Thank you!

[Illyrian94]

I saw on the lodestone that this issue was fixed! Can anyone confirm that they aren't having issues around prime time?

Thank you!

Sadly I think the Lodestone post was just about an outage that occurred last night--none of the posts I'm seeing on there look like they pertain to our exact issue. I'm going to be keeping an eye on ping and packet loss today and will see how things look around when the issue normally starts to rear its head.
I'm not holding out hope, though. At this rate I'm probably just going to cancel my sub until we get an actual acknowledgement that this specific issue has been resolved.

[Kwehvehpeh]

Sadly I think the Lodestone post was just about an outage that occurred last night--none of the posts I'm seeing on there look like they pertain to our exact issue. I'm going to be keeping an eye on ping and packet loss today and will see how things look around when the issue normally starts to rear its head.
I'm not holding out hope, though. At this rate I'm probably just going to cancel my sub until we get an actual acknowledgement that this specific issue has been resolved.

Ah, that's a shame then. Despite knowing better, I'm still holding out hope!

[Lahtori]

Ah, that's a shame then. Despite knowing better, I'm still holding out hope!

The hopium/copium train is that the server outage was due to NTT fixing their node / doing maintenance, which interrupted all FF servers (since NTT is what's used to get there, it's just some unfortunate folks (us) go through a bad node). That's the train I'd like to be on... I'm tentatively on it. One toe in.

[Kwehvehpeh]

The hopium/copium train is that the server outage was due to NTT fixing their node / doing maintenance, which interrupted all FF servers (since NTT is what's used to get there, it's just some unfortunate folks (us) go through a bad node). That's the train I'd like to be on... I'm tentatively on it. One toe in.

Yeah. I've been holding out on getting a VPN, hoping that they would get it resolved before the weekend. But if its still bad today, I suppose I'll dish out the money for it again.
I pray that we do not have to return to the lagging sands tonight.