It's true that 1.1.1.1 fixed it for me but good God this is dumb. Hopefully this is fixed within another week but hopes not held high here.
Printable View
It's true that 1.1.1.1 fixed it for me but good God this is dumb. Hopefully this is fixed within another week but hopes not held high here.
We'll see legacii. Anyway that helped me too tho I haven't really strained it yet (getting ready for Momocon) so I proly won't be doing more than island for another week. I'm just hoping that it'll be fixed by next week, after momocon.
I know brother won't want to play on my pc really; Go in his sister's bedroom = no bueno especially when there's no rush and hopefully AT&T and NTT will quit shooting at each other, so to speak.
Your optimism is admirable but as someone stated earlier, this is a pissing contest between two huge internet companies. There is nothing SE can do, and tangentially nothing WE can do, except either use a VPN or vote with our wallets.
This isn't an anime or JRPG where fighting spirit and the power of friendship can win the day. This is late-stage capitalism at its finest.
Got a week left of sub. It would be a very sad way to say goodbye to this game but I don't see this being resolved soon if ever.
Hey all, first time posting on the Lodestone lol. I know this is not new information but I feel I need to add my voice to the fire.
Me and my Fiancé have been dealing with the packet loss issues as well since around May 15th, 2023. Making the game unplayable. We have submitted multiple tickets via the form mentioned on the last couple post by Square on socials and also submitted bug reports as well in-game.
This morning I decided to run Pingplotter and the tracert command to see if after the 6.4 patch today would've fixed the issue.
The only issue I saw from Pingplotter was that ONLY ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] was dropping nearly 100% packets. Otherwise it wasn't indicating we weren't losing packets. So I was sniffing that hopium throughout the workday.
Now with it being peak hours as of this post, we are consistently getting packet loss. This is across the board on all NTT nodes starting at the one mentioned above. In game there is massive delay between actions and players characters are stop and go. Completely unplayable. Below are my latest tracert results. Hopefully this helps.
1 <1 ms 1 ms 2 ms
2 9 ms 13 ms 7 ms
3 17 ms 19 ms 15 ms
4 * * * Request timed out.
5 * * * Request timed out.
6 31 ms 30 ms 31 ms 32.130.17.75
7 34 ms 31 ms 31 ms cgcil402igs.ip.att.net [12.122.133.161]
8 25 ms 24 ms 25 ms 192.205.32.194
9 27 ms 27 ms 23 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 69 ms 80 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 131 ms 137 ms 132 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 136 ms 133 ms 132 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 133 ms 141 ms * 204.2.29.241
14 141 ms 139 ms 130 ms 204.2.29.6
Without having to read through all 600 posts lol does anyone know which nodes will work for someone in Midwest USA to solve the issue using Surfshark?
I can't speak for Surfshark, but what worked for my VPN was a bit of trial and error. Essentially, I just ran ping and traceroute commands on each one, and saw what worked and what didn't from where I am in Texas. I noted each one respectively as a "use" or a "pass" once tests concluded.
What constitutes "what worked" is dependent on node and location, so long as the NTT problem nodes in Sacramento (documented countless in this thread) are avoided.
I really wish there was a simple, free work around for this issue on console... I just let my sub expire earlier this week because the game has been nearly unplayable for me, and I won't re-sub until it's fixed (if it ever is). Sucks to have this happen right before a big patch, was really looking forward to running a new dungeon and going through the new story content.
For me, the lag is still there, but at the moment, it has gotten a little bit better, but I'm keeping a close eye on it for a few days before doing more. Still playing on PS5.
It's patch day. . . . . and the lag persists. . . . AT&T had the audacity to send me a text saying that my issue was fixed. It is clearly not.
Here is the WINMtr from around 7pm EST
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| censored - 0 | 41 | 41 | 0 | 0 | 1 | 1 |
| censored - 0 | 41 | 41 | 1 | 1 | 4 | 2 |
| 99.173.77.14 - 0 | 41 | 41 | 2 | 2 | 5 | 2 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| 32.130.17.65 - 0 | 41 | 41 | 11 | 15 | 19 | 11 |
| 192.205.36.158 - 0 | 41 | 41 | 11 | 17 | 35 | 35 |
| ae-8.r25.atlnga05.us.bb.gin.ntt.net - 0 | 41 | 41 | 11 | 15 | 34 | 11 |
| ae-6.r21.dllstx14.us.bb.gin.ntt.net - 0 | 41 | 41 | 27 | 28 | 37 | 27 |
| ae-1.r20.dllstx14.us.bb.gin.ntt.net - 10 | 31 | 28 | 27 | 29 | 37 | 31 |
| ae-2.r24.lsanca07.us.bb.gin.ntt.net - 67 | 12 | 4 | 108 | 109 | 110 | 109 |
| ae-5.a01.scrmca03.us.bb.gin.ntt.net - 6 | 34 | 32 | 116 | 116 | 123 | 116 |
| ae-1.a00.scrmca03.us.bb.gin.ntt.net - 10 | 32 | 29 | 116 | 120 | 164 | 121 |
|xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net - 14 | 29 | 25 | 115 | 117 | 120 | 117 |
| 204.2.29.241 - 20 | 26 | 21 | 0 | 116 | 117 | 116 |
| 204.2.29.122 - 10 | 30 | 27 | 115 | 116 | 119 | 116 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider