Bad lag again with NTT's NA server network

[penguinicus]

Same here - AT&T customer in south TX routing through Dallas...

[Mistmonster]

Att South Florida.. it not playable ;;

[Myanisa]

I'm having the same issues in Dallas, TX with AT&T!

[TaleraRistain]

AT&T in the Midwest and getting severe rubber-banding tonight. I just logged out. I will lag from time to time and get occasional rubber-banding but it's never been this bad. Seeing that same doubling right around where the trace hits Sacramento.

[n_n]

AT&T user here from the east coast, I too am getting very bad lag-- it is completely unplayable. :<

[Ath192]

Texas, same issue around 15% packet loss. Too laggy. I escalated my ATT ticket as much as I could, they told me they would get back to me but it seems they can't do anything per previous comments here.

[Janyd]

Yes, I've heard the same runaround from AT&T.

Unfortunately, this is up to SE and NTT to sort out sooner rather than later.

The more responses and feedback this thread and other similar ones get, the better. Share them with your FCs, Linkshells, etc., and see what they can offer for feedback.

However, there is a Support form we can also use to submit traceroutes: https://support.na.square-enix.com/c...382&la=1&fty=2

[Dragoonhuntz]

AT&T user here to say "me too". The ping and packet loss issues are identical on my end to what everyone else describes.

Using a VPN seems to have fixed the issue on my end. That being said I certainly don't count that as an ideal solution and do not welcome yet another additional monthly subscription if the problem doesn't get resolved.

[n_n]

AT&T user here from the east coast, I too am getting very bad lag-- it is completely unplayable. :<

The lag has disappeared for me as of 10 minutes ago. I'm currently doing crafting with a macro with zero problems.
Here's hoping it stays this way...

[MoonmoonMoonmoon]

The lag has disappeared for me as of 10 minutes ago. I'm currently doing crafting with a macro with zero problems.
Here's hoping it stays this way...

Looks like it's fixed. I've been monitoring it and it appears to have disappeared. Perhaps they did a nightly server restart and that fixed the issues.