Bad lag again with NTT's NA server network

Quote:

---

Originally Posted by Deadlyhazard

Anyone still getting issues? Feel like I'm the only one still with the same issues since Tuesday, still tons of delay on stuff. Most of my friends issues have been resolved.

---

Just had my game crap the bed a few minutes ago, casts dropping left and right, several second long hang ups into the game just booting. Reclears have been impossible this week because of it. Been like this for about a week now.

Traceroute to NA Center as instructed and to Exodus server IP. From MA via Xfinity/Comcast. This is why I can't even think about trying savage content, as I already have too many instances of getting hit by mechanics that I've avoided on my PC screen. Around 9pm EST but this happens all the time, even 4-5 am EST on weekdays. It's reached a point where I have to watch to see if crafting actions complete when using keybinds, as I've messed up some when just going by rhythm.

2 13 ms 11 ms 18 ms 96.120.64.125
3 12 ms 13 ms 13 ms 24.124.210.93
4 20 ms 15 ms 13 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 20 ms 19 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 16 ms 16 ms 21 ms 75.149.231.250
7 37 ms 37 ms 37 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102] + 16-21 ms from Comcast to NTT
8 82 ms 83 ms 87 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] + 45-50 ms within NTT
9 87 ms 83 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 84 ms 89 ms 85 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 86 ms 90 ms 88 ms 204.2.29.122

2 16 ms 25 ms 13 ms 96.120.64.125
3 11 ms 11 ms 17 ms 24.124.210.93
4 15 ms 22 ms 15 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 21 ms 17 ms 19 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 20 ms 19 ms 19 ms 75.149.231.250
7 36 ms 40 ms 36 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102] + 16-20 ms from Comcast to NTT
8 90 ms 83 ms 89 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] + 43-54 ms within NTT
9 91 ms 93 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 89 ms 88 ms 92 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 86 ms 95 ms 87 ms 204.2.29.83

And snippet of Resource Monitor:

https://chi01pap001files.storage.liv...&cropmode=none

Traceroute, Sun 6-18-23 11:15p EST

2 14 ms 11 ms 11 ms 96.120.64.125
3 13 ms 11 ms 11 ms 24.124.210.93
4 18 ms 15 ms 17 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 18 ms 15 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 15 ms 15 ms 17 ms 75.149.231.250
7 36 ms 35 ms 63 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 82 ms 81 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 85 ms 83 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 86 ms 88 ms 87 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 84 ms 83 ms 83 ms 204.2.29.122

Traceroute, 6-19-23 4:46a EST (seriously, 4 AM)

2 11 ms 9 ms 12 ms 96.120.64.125
3 10 ms 9 ms 11 ms 24.124.210.93
4 14 ms 13 ms 14 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 14 ms 15 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 15 ms 17 ms 15 ms 75.149.231.250
7 35 ms 35 ms 45 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 90 ms 89 ms 79 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 87 ms 83 ms 83 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 86 ms 86 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * 84 ms 204.2.29.241
12 84 ms 83 ms 86 ms 204.2.29.122

6-19-23, 5:00-5:10am est

https://chi01pap001files.storage.liv...&cropmode=none

Going to submit another trace route to SE tonight, because I’m still seeing the same problem.

Sorjal: your trace looks a lot like mine once it gets to NTT. Both of us are seeing issues start at San Jose. Comcast was having trouble the other morning, unrelated to this since I’ve been dealing with this since last Sunday, but all my local numbers are still low. It’s that San Jose node where I see everything quadruple.

Definitely don't let up as the problem continues to be unresolved.

Still seeing the awful lag... looks like the San Jose node has been removed or rerouted and now the one in LA (?) is acting up? Now I'm starting to get numbers in the hundreds... had a couple hours last night where the lag was minimal, but it came back around midnight again.

8 20 ms 24 ms 18 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 29 ms 27 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 31 ms 31 ms 25 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 27 ms 27 ms 31 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 33 ms 33 ms 30 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 35 ms 31 ms 26 ms ae-2.r25.asbnva02.us.bb.gin.ntt.net [129.250.2.124]
14 94 ms 93 ms 84 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
15 98 ms 100 ms 85 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
16 89 ms 92 ms 90 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
17 90 ms 145 ms 93 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
18 92 ms 97 ms 89 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 * 90 ms * 204.2.29.241
20 93 ms 98 ms 95 ms 204.2.29.122

Not sure what's going on, again, but latency has increased 5-8ms more than average. I haven't been playing as much as I usually do, but I did some reclears on Tuesday and had an amazing 58-59ms stable connection. Currently I'm in the 65-69ms range and well, why? This is really dumb.

Quote:

---

Originally Posted by ArcadiaP

Not sure what's going on, again, but latency has increased 5-8ms more than average. I haven't been playing as much as I usually do, but I did some reclears on Tuesday and had an amazing 58-59ms stable connection. Currently I'm in the 65-69ms range and well, why? This is really dumb.

---

Yeah I was getting this too when I was trying my normal connection a couple weeks ago. Going from 58 to 65+ at certain times of the day. I don't experience this on proxy connection, so I've just been playing on that from now on. Especially since I experienced really bad lag for 15 mins straight one time.

Also last night I saw a sizeable amount of people in duty and big city shout chat complaining about really bad lag, 300+ ping, etc. Seems to still be broken for some. I'm surprised this thread has really slowed down now despite that.

Square's customer support just told me...

"Hello there,

Thank you for contacting Square Enix Customer Support. Let me assist you with the connection error that you are receiving.

Broadly speaking, connection issues come from three places: your home network, the server, and the route connecting the two. Since everyone connects to the same server or group of servers and we do not have multiple reports of connection issues at this time, we can safely rule the server out. To troubleshoot your home network, we provided the suggestions in our previous response. Since none of those suggestions have resolved the issue, the problem likely does not stem from here. This leaves the route in between as the most likely culprit.

This most likely is caused by congestion or routing issues along the way to the server, causing latency, packet loss, and disconnections. This is sometimes caused by severe weather conditions or technical malfunctions anywhere between a PC/Console and the server, not necessarily around the devices' immediate area.

Unfortunately, we do not have any direct control over how the device is routed to the server so we are unable to resolve this. As such, we would suggest contacting your Internet Service Provider and making a report with them.

You can also submit a report on any connection issues via this link here:
http://sqex.to/vzc

Again, we apologize that we are unable to assist you with this issue further and hope that you can still continue to enjoy the game.
"
... completely ignoring that this thread even exists, or that NTT is Their provider...

There is a problem with NTT the last few days that I wasn't experiencing at all until now. My ping has increased by 100. All but one of the points on the way to NTT have this extra 100 ping.

Actually it's all over the place. It increases to 400 ping sometimes, then 200, then 300, with occasional packet loss across all the NTT points. Occasionally it's normal. But it is affecting my weaving a lot and very noticeable.

I have tested this on two separate internet connections on two separate ISPs because I actually have two. And both have the problem.

Using Windows Command Prompt to ping Aether it's giving me 380+ms with a 25% drop rate usually. Never had any problems until today about 5 hours ago. Incredibly annoying and makes the game unplayable, hope this is resolved ASAP.

Quote:

---

Originally Posted by Yaesrei

Using Windows Command Prompt to ping Aether it's giving me 380+ms with a 25% drop rate usually. Never had any problems until today about 5 hours ago. Incredibly annoying and makes the game unplayable, hope this is resolved ASAP.

---

I am in Eastern Canada with a Canadian ISP and that's what I am getting on all North American servers too: 350+ ms ping with 50% packet loss on Aether and 25% on Excalibur. This has been happening regularly since about a month. In the meantime I tested on European server Chaos and am getting 100ms.

Edit: tried with two ISPs at 2 homes, Bell and Videotron, same bs.

I'm in NYC with Verizon Fios. On Thursday night during raid, I started getting 300+ ms ping, up from my usual of around 76ms, making it unplayable. It would stabilize itself sometimes, then jump again. Friday was fine. Now today its acting up again, with my current average ping being over 330ms. It seems to be just like the issue affecting AT&T customers some time ago, and I don't really know what to do or if this issue is going to get resolved, or if I should just resort to a VPN. I've never had problems like this with Verizon before and its incredibly annoying because just when I think its stabilized it jumps again.

Ottawa, Ontario. Rogers ISP. Lag so bad I can activate Quickcast and have the effect only apply halfway through my next cast. I have to click an item on a gathering node multiple times in order to get it to actually gather.

Unplayable for me currently.

Getting this ping issue from NTT nodes on WOW internet based out of Michigan US, unplayable on anything but the simplest dungeons

Looks like NA server network is once again having problems. NTT doing it's usual and adding considerable lag.

Come on SE, add in cross-region DC travel already so we can bail out when these problems out and come back when it's fixed.

Well, I did notice a poor connection on Primal. but I have not to sever lagged yet. kind of sucks that this isn't fixed =/

It really does seem like every time one region sees improvement the issues start up in another! But I’m still seeing it, and it’s going on the 3rd week in a row now. There are very brief periods when the lag is minimal, but otherwise it’s near constant and it doesn’t seem to matter what time of day I’m on.

I just keep sending them traceroutes… how could they tell the other poster that they’ve had no reports! It’s not our ISP, it’s theirs! Just really upsetting because this is my main game and trying to do any actual content is near impossible.

Quote:

---

Originally Posted by Valcarde

Ottawa, Ontario. Rogers ISP. Lag so bad I can activate Quickcast and have the effect only apply halfway through my next cast. I have to click an item on a gathering node multiple times in order to get it to actually gather.

Unplayable for me currently.

---

Yo, I'm in Ottawa too, with Bell however. Same poor connection, terrible lag, experiencing pretty much full packet loss after pinging Crystal server.

Eastern North Carolina, tried with Verizon FIOS and two seperate Centurylink ISP connections.
It's all over the place on all NA datacenters, ping will constantly go from ~150ms up to ~2000ms, it's never been this bad before. Has only been like this since last server maintenance.

Upstate South Carolina with Comporium & still seeing periodic packets just fall off the face of the earth starting at the NTT nodes in Ashburn, Virginia. Occasionally the drops occur a bit later into the line, but 99% of the time its on the first NTT node in the batch (Ashburn).

Quote:

---

Originally Posted by Suimetsu

Upstate South Carolina with Comporium & still seeing periodic packets just fall off the face of the earth starting at the NTT nodes in Ashburn, Virginia. Occasionally the drops occur a bit later into the line, but 99% of the time its on the first NTT node in the batch (Ashburn).

---

Interesting… I’m also routed through Ashburn. My numbers don’t look awful til California but I’m no tech expert and I just learned how to do a trace route a few weeks ago. lol

Could the Ashburn node be the problem even though I’m not seeing the high numbers until San Jose or LA? I think you’re the only other person I’ve seen so far mention Ashburn specifically. I have been dealing with this for about 3 weeks now.

Quote:

---

Originally Posted by Khryseis_Astra

Interesting… I’m also routed through Ashburn. My numbers don’t look awful til California but I’m no tech expert and I just learned how to do a trace route a few weeks ago. lol

Could the Ashburn node be the problem even though I’m not seeing the high numbers until San Jose or LA? I think you’re the only other person I’ve seen so far mention Ashburn specifically. I have been dealing with this for about 3 weeks now.

---

Its quite possible some issues aren't caught in the exact moment a trace is being done, and you happen to catch only a portion of the issue in action midway through. That said, two examples are below. (As far as the California nodes go, I'm confident they're amongst the biggest culprits, but none of the nodes are exempt from scrutiny considering how long this issue has been going and how widespread it seems to be)

https://i.imgur.com/tp9CGd4.png
You can see the packet loss starts at Ashburn and just trickles down. To be fair, some of it are false positives since some of the nodes down prioritize pings and the such.

https://i.imgur.com/yizxctf.png
Similar as the previous. Overall point is that the issue, for me at least, is incredibly sporadic and comes at unpredictable intervals - be it in the morning when I'm just doing a few dailies & setting my island agenda or at night when I'm trying to prog with my static

I know some of the others in the thread most likely suffer vastly worse issues than the two simple examples here and what I've shown doesn't seem too extreme. If anything, it looks incredibly mild in comparison to when I hear someone say their latency is in the triple, if not quadruple digits. In the end, the point is simply to show that the issues begin at the NTT nodes and not within the individual users' ISP network

Another day, another tracert (this time with .29 instead of .92 :))

Tracing route to 204.2.29.122 over a maximum of 30 hops

1 2 ms 1 ms 1 ms <removed>
2 21 ms 13 ms 11 ms <removed>
3 15 ms 15 ms 11 ms <removed>
4 16 ms 15 ms 19 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 17 ms 17 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 20 ms 25 ms 21 ms 75.149.231.250
7 46 ms 65 ms 54 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 145 ms 122 ms 84 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 103 ms 86 ms 83 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 90 ms 93 ms 88 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * 91 ms * 204.2.29.241
12 91 ms 84 ms 85 ms 204.2.29.122

Trace complete.

I just logged on and it looks like my ping has shot from mid 50s to low 100s-109 today (the same numbers when connecting through the broken NTT node a month or so ago). Currently, it doesn't seem to be dropping packets when I check via command prompt, but if this issue is actually back and my method to "fix" it no longer works, then I won't be renewing my game time next week.

Yup, lag and some packet loss started at exactly 6:19pm EST

Edit: Doesn't matter what VPN node I use, same out come. Either NTT is being DDoSed or someone messed up their routing (again?).

https://i.imgur.com/uMMVHaE.jpg

Thanks for your graph. Krojack.
Yeah, no matter what connection I use, I get the same result. The game is still playable at the moment, though. I'm not getting the crazy packet drops like before where it felt like ages to register actions/combos/etc. I just did some roulettes and I also didn't see people stopping in place.

Aye, it's showing up as "Good" on Aether when I'm normally on "Excellent" again.

I'm beginning to think this might just be a DDoS on the nodes or somewhere in the network since I'm not getting really any packet loss either.



1 <1 ms <1 ms <1 ms (REDACTED)
2 18 ms 17 ms 18 ms (REDACTED)
3 18 ms 18 ms 19 ms (REDACTED)
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 33 ms 31 ms 31 ms (REDACTED)
8 30 ms 26 ms 25 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * * * Request timed out.
10 85 ms 85 ms 89 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 109 ms 109 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 * * * Request timed out.
13 108 ms 107 ms 107 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 104 ms 102 ms * 204.2.29.241
15 107 ms 104 ms 100 ms 204.2.29.122

EDIT (8:50 PM CDT): Okay, logging in shows as "Excellent" again and I'm really not noticing anything different when crafting things. Hmm, might be a temporary bug? We'll have to see.

This is the 4th week in a row of near constant lag for me... my connection status has said excellent on login throughout it all, but tonight it said good instead. Still seeing the high numbers/packet loss occurring inside NTT at LA (it was San Jose before, but that doesn't appear in my traces anymore) and Sacramento. Submitted the following trace to SE tonight:

8 18 ms 17 ms 17 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 23 ms 22 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 27 ms 29 ms 31 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 24 ms 23 ms 30 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 36 ms 33 ms 25 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 29 ms 33 ms 27 ms ae-2.r25.asbnva02.us.bb.gin.ntt.net [129.250.2.124]
14 85 ms 95 ms 91 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
15 93 ms 85 ms 96 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
16 101 ms 95 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
17 * 112 ms * ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
18 96 ms 102 ms 97 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 * * * Request timed out.
20 98 ms 100 ms 103 ms 204.2.29.122

it's back, 3:19 PST Monterey CA. Ping was 25ms, now 80 plus with lost packets. So far Warp gets it back to normal.

Yeah, went back to normal within the last hour or two, it seems.

Hopefully, it was just an anomaly or a DDoS that's been dealt with.

It's still acting weird for me, although the numbers have improved since earlier. My ping currently fluctuates wildy between early 50s to late 70s. (normally it is a stable 54-56)

Chiming in that last night doing some farming, my ping was at 120ms and very bad, had to immediately jump into VPN. It's very early in the morning and I'm still in the high 60's and low 70's. Something once again, is massively broken and wrong.

Getting tired of having to monitor my ping for XIV and babysitting it.

This is looking similar to the AT&T problem from a month ago, only that using a VPN doesn't completely get around it. It lowers the ping time some and almost eliminates the packet loss.

https://i.imgur.com/0FvYvYW.jpg
The small drop just after 10am is when I turned my VPN off. I left it connected all night long.

Yeah, it's hovering around 100-109ms for me in the "Good" range again. Still no notable packet loss for the moment on my end, but that could change.

The fact that a VPN doesn't always get around it and that it seems to affect more than just AT&T this time (think I saw a Comcast report in the thread recently) gives me reason to believe this issue's different than last time.

That and the packet loss isn't as bad or noticeable for some people, but is very noticeable/bad for others. Hmm...

EDIT (1:55 PM CDT): Noticed a few small bits of packet loss during a Crystalline Conflict (Casual) match. Not that it affected the outcome that much, still won the game in overtime, but it was a bit disconcerting.

I ran a ping to the Aether datacenter and... 50% packet loss. No packet loss on my ping to the lobby server, though. The latest traceroute is enclosed and already submitted to SE via the form here:
https://support.na.square-enix.com/c...ss%20and%20lag

Seems to be that traffic heading into California from anywhere else is affected across multiple connections. I wonder if it's a localized infrastructure problem that seems to be spilling over.


1 <1 ms <1 ms <1 ms (REDACTED)
2 18 ms 17 ms 17 ms (REDACTED)
3 18 ms 18 ms 18 ms (REDACTED)
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 31 ms 31 ms 32 ms (REDACTED)
8 25 ms 25 ms 25 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 27 ms 25 ms 26 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 * 96 ms 101 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 108 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 98 ms 101 ms 105 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 110 ms 109 ms 110 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 99 ms * 204.2.29.241
15 109 ms 107 ms 110 ms 204.2.29.122

Quote:

---

Originally Posted by Janyd

The fact that a VPN doesn't always get around it and that it seems to affect more than just AT&T this time (think I saw a Comcast report in the thread recently) gives me reason to believe this issue's different than last time.

---

Yeah I’m on Comcast… my issues started about the time most of the AT&T users were starting to see some improvement! An FC mate further south from me is also seeing the issue; usually her VPN takes care of it, but not always. I just keep submitting the trace routes to SE because it’s not my ISP that’s the culprit, it’s theirs. This has been about a month for me now, and it’s near constant. By that I mean, I maybe get 20-30 minutes here and there, with no particular pattern, where the lag is still there, but tolerable enough to run a short duty, like a trial or normal raid. There has not been one day since June 11th that I haven’t had lag for mostly the entire time I’m on, and I’m on a lot. lol

Quote:

---

Originally Posted by Khryseis_Astra

Yeah I’m on Comcast… my issues started about the time most of the AT&T users were starting to see some improvement! An FC mate further south from me is also seeing the issue; usually her VPN takes care of it, but not always. I just keep submitting the trace routes to SE because it’s not my ISP that’s the culprit, it’s theirs. This has been about a month for me now, and it’s near constant. By that I mean, I maybe get 20-30 minutes here and there, with no particular pattern, where the lag is still there, but tolerable enough to run a short duty, like a trial or normal raid. There has not been one day since June 11th that I haven’t had lag for mostly the entire time I’m on, and I’m on a lot. lol

---

Ah, so at least it's a shared problem across two different major ISPs, even though it still stings.

Also, can confirm my VPN has eliminated the latency/packet loss issues. My ping tests came back at 69 ms (nice) so that's about 8 to 10 ms more than what I had prior, which is negligible for me.

Yeah it's pretty garbage over all.

This is an example from May 24th, 2023 for 1 day. The high pings on the left and the packet loss on the right. (blue line is avg pkt loss)
https://imgur.com/vZw9HrY.jpg


This is today. Packet loss isn't as bad but it's there and will impact game play.
Note: I've also added a second ping chart that shows my min, avg, and max pings for my VPN connection. The right side yellow is packet loss avg. It's pretty much 0%
https://imgur.com/EessppW.jpg

Hi ya'll! My sub had lapsed and I wanted to give it some time to see if things stayed good before resubbing... resubbed two days ago... and here we are again. I starting having issues today around 1pm EST (noticeable rubberbanding in PVP and at the Gold Saucer) with a "Good" connection. 7pm EST now and connection is "poor". Really disappointed this is continuing.

https://i.imgur.com/1TlqWgX.png
Day 2: my ping sits at 119-120 on my proxy connection that was perfect until yesterday lol.
And I just DC'd in a Prae roulette. A few minutes before me, 2 other's DC'd that got stuck in queue.
it seems like things are getting worse now?
Hopefully this gets fixed soon... otherwise, I guess I'll go play something else next week when my sub runs out.

Maybe the kicking of people were them changing something. Seems lag is fixed..... for now.

https://imgur.com/DQJkUeY.jpg