NA server issues over the last week is becoming unacceptable

[MisterNublet]

Well, if it makes you guys feel better, they're apparently aware of it

https://twitter.com/FF_XIV_EN/status...63004749402114

First comment: "The linked article is from a year ago btw. They've had this open for a year and have had access to the code of both of the third party tools that fix their animation lock/latency bug and are still "collecting information".

Spoiler: SE isn't gonna do anything about it.

I'm on Frontier Fios and it's impossible for me to play at 10:30 am.

[Valkyrie_Lenneth]

First comment: "The linked article is from a year ago btw. They've had this open for a year and have had access to the code of both of the third party tools that fix their animation lock/latency bug and are still "collecting information".

Spoiler: SE isn't gonna do anything about it.

I'm on Frontier Fios and it's impossible for me to play at 10:30 am.

Animation lock is intended. That however isn't the problem here. They can't fix NA ISPs. Or EU ones apparently.



The link is from a year ago because it's still relevant. They need user reports to have ammo to take to their provider to say "hey, this is a problem for our users". And it's not a one time fix.



The internet doesn't work the way people seem to think it does. It's not an on or off connection. It's not one link.

[RyuDragnier]

West Coast NA, frequent rubber-banding day 3. Unplayable.

An easy fix for now is to use a VPN. The second I did, I had no more lag issues. I do hope they fix this soon though, last thing anyone wants is the patch being released with this going on.

[ATTSucksNow]

My solution for may not work for everyone but I went to Verizon and grabbed a 5G home network from them. I can use it for < 30 days and return and cancel the service if I am not interested. I will use the 30 days to prog the tier while AT&T fixes their network issue. If it is fixed before, I will hang on to the Verizon home network until about day 29.

Good luck savage progging, friends!

[MisterNublet]

Animation lock is intended. That however isn't the problem here. They can't fix NA ISPs. Or EU ones apparently.

The link is from a year ago because it's still relevant. They need user reports to have ammo to take to their provider to say "hey, this is a problem for our users". And it's not a one time fix.

The internet doesn't work the way people seem to think it does. It's not an on or off connection. It's not one link.

I should have only copied the first part. "The linked article is from a year ago btw."

It has been a known issue that NTT is trash for more than a year, and nothing has been done about it.

[Valkyrie_Lenneth]

I should have only copied the first part. "The linked article is from a year ago btw."

It has been a known issue that NTT is trash for more than a year, and nothing has been done about it.

Every backbone provider has issues. You probably weren't around for it, but when the servers were in Montreal, we had similar issues, only this time the meme was Level3. They had a node that crapped out almost every day at 6pm est.

[MisterNublet]

Every backbone provider has issues. You probably weren't around for it, but when the servers were in Montreal, we had similar issues, only this time the meme was Level3. They had a node that crapped out almost every day at 6pm est.

A previous issue with a different provider doesn't make the current issue any less of a problem.

[Valkyrie_Lenneth]

A previous issue with a different provider doesn't make the current issue any less of a problem.

That's not what I'm saying. I'm saying the internet is complicated and no provider is safe from issues. See my earlier post on page one with the trace.



Or page w/e if you have only 10 posts per page.

[MisterNublet]

That's not what I'm saying. I'm saying the internet is complicated and no provider is safe from issues. See my earlier post on page one with the trace.



Or page w/e if you have only 10 posts per page.

Gotcha.

Currently though, every time I've had connectivity issues, it has been NTT, and it's almost always the same nodes. Nothing is gonna change since NTT is a Japanese run company.

[Valkyrie_Lenneth]

Gotcha.

Currently though, every time I've had connectivity issues, it has been NTT, and it's almost always the same nodes. Nothing is gonna change since NTT is a Japanese run company.

Well, currently it seems to be att that's causing issues. Yes, ntt is problematic, but again, it's complicated. Switchgear has dozens to hundreds of ports. That's why not everyone who goes through the same nodes has issues when others do.