Printable View
I have the following one supplied by them. I can even enable IP Passthrough which means the modem just acts as the connection. All data can be passed though to your own personal router if your choice. The modem at that point is pretty much invisible to anything on your network. It's no longer your router, firewall, wifi or anything. Your new router does all that.Quote:
Originally Posted by aerimisia
https://www.amazon.com/802-11a-Wirel.../dp/B08PCRYJPW
Been checking back in with this thread for any news and updates on the lag situation. Nord VPN has been working really well since Cloudflare took a shit and stopped working. Sucks that I had to do this and spend money to play something I am already subbing to but it's like Sweet Tooth said in Twisted Metal Black, "Let's face it boys and girls. A man has to have his priorities." Quality time with my dearest is essential so I gotta do what I gotta do.
replying to add more info. not on ATT, on centurylink fiber in midwest US, getting routed through bad NTT nodes as well. getting tons of packet loss to game, just started yesterday
Unfortunate that the issue seems to be spreading and getting worse. All with no proper acknowledgement from Square, either. They responded to my support ticket yesterday by saying they were "aware of the issue" and directing me to submit another tracert result to the form the community manager posted earlier--so basically the same response we've been getting this whole time.
I'll post my daily "still broke" screenshot later today like usual. Cloudflare Warp is thankfully still working for me, but once my currently canceled sub runs out I'll probably be done with the game for awhile unless Square decides to finally bless us with a proper response.
I hope they do get on the ball Illy; as for me, got Aetherfont done this morning and my island's set up for Momocon, so I'll be back after the con. It's aggravating that me and 'Neko can't play together until Square/NTT gets their act together. He works, I don't have a job at the moment (tho working on that) so I can get some stuff done early in the day if I get up in time.
(And off topic; if anyone's going to Momocon, look out for this miqot'e in human form! I'm planning on showing up at the FFXIV panel and the photoshoot.)
When does the lag usually get better in the evenings? Last night I go a bit of a reprieve around 11:30 PM EST. Thought that maybe they did something, but heard that there was widespread DC'ing early this morning.
My Traceroute showed that the issue was in NTT specifically. First hop on their network had good ping, but after the first, it dies. Probably why AT&T isn't doing anything about it. Ironically, this happened in the past I found on reddit. 2 years ago same issue.
Kind of feel this ATT NTT node issue along with other ISPs will last till next month because no way they will fix this problem before Savage next week. kinda sucks that the ff14 Twitter page is just pointing fingers at our isp to say something yet most of the responses have been going to square or we can't really contact NTT to fix the problem but I'm just going to stick with the lag since I can't afford a VPN. sometimes cloudflare crashes around midnight for me. so rather just suffer with the lag till it fixes itself. I personally feel they throttled us hard and knew half of us were hyped for 6.4 and I personally feel they sabotage the severs with lag.
The latency is - as others have alluded to - starting later in the day now. I'm not holding my breath though. It's still not what I would get on a normal play session prior to 05/15. Let's see how it holds later.Code:3 6 ms 3 ms 3 ms 71.155.29.140
4 * * * Request timed out.
5 13 ms 7 ms 7 ms 32.130.25.65
6 8 ms 6 ms 7 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
7 9 ms 6 ms 8 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
8 * * * Request timed out.
9 48 ms 43 ms 45 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 62 ms 66 ms 57 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 45 ms 45 ms 51 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 75 ms 68 ms 65 ms 204.2.29.241
13 45 ms 44 ms 44 ms 204.2.29.6
While the AT&T response with the most info is not from an employee, but from an "expert", I do tend to agree with what they and AT&T reps say: it's on NTT. I really do hope it's not some sort of dumb money spat between the two, that would just make me so sad to suffer because of greed.
Issue started popping up today in the early AM around 5-7am EST for me instead of just during "prime" time.