Nearly unplayable lag, varying 230-250 ms each evening from Node in San Jose CA

I live in Florida and each evening my latency skyrockets to nearly unplayable levels. I ran a tracert and it's coming from a series of nodes in CA, mainly starting in San Jose but carrying on to your servers. I'll post the tracert here, minus my local stuff.

6 40 ms 36 ms 35 ms ae-6.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
7 58 ms 58 ms 61 ms ae-8.r20.dllstx14.us.bb.gin.ntt.net [129.250.2.219]
8 58ms 59 ms 62 ms ae-1.r21.dllstx14.us.bb.gin.ntt.net [129.250.3.55]
9 100 ms 96 ms * ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 226 ms 194 ms 212 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 248 ms 256 ms 236 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 230 ms 211 ms 195 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 253 ms * 204.2.229.230
14 232 ms 227 ms 224 ms 204.2.229.9

Trace complete.


As you can see it starts at the first hop to San Jose, then doubles, then continues through Sacramento to your servers. Some sort of action on your end to have them fix this, wherever this is and from whoever it belongs to, would be appreciated. Thanks.

Yeup, starts around 7-8pm and stops at exactly midnight CST. Every night. Like.. to the second. That one node.

Seeing the exact same issue from Texas. It's definitely not my ISP, it's whatever ISP SE is using within their server datacenter. It's been happening since Sunday night and it's really killing the mood for trying to run anything during my evenings.

Tracert from my location to the SE datacenter here, as well as seen packet loss occurring when running a constant ping to that same location:

5 11 ms 14 ms 15 ms 32.130.16.9
6 12 ms 9 ms 9 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 30 ms 9 ms 11 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 9 ms 8 ms 9 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 46 ms 45 ms 49 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 173 ms 152 ms 177 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 178 ms 168 ms 179 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 209 ms 171 ms 176 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 154 ms * 204.2.229.230
14 173 ms 154 ms 183 ms 204.2.229.10

Packet loss seen:
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=117ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48
Reply from 204.2.229.10: bytes=32 time=212ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Reply from 204.2.229.10: bytes=32 time=185ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=194ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=194ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=197ms TTL=48
Reply from 204.2.229.10: bytes=32 time=188ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=183ms TTL=48
Reply from 204.2.229.10: bytes=32 time=210ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Reply from 204.2.229.10: bytes=32 time=163ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=188ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48

Ping statistics for 204.2.229.10:
Packets: Sent = 12503, Received = 12316, Lost = 187 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 219ms, Average = 118ms

Bump.
Not quite technically savvy enough follow the tracert, but the timeline for my lag has been very similar. Starting approximately December 26th, maybe a day or two earlier, the lag starts around evening prime time, approximately 7:00PM EST, and was calming down around 11:30 PM EST yesterday.

Having the exact same issue, Verizon is probably very annoyed with me complaining to them, here's my tracert just to add to the list. Problem starts at 7-9pm EST and ends at midnight.

7 23 ms 24 ms 24 ms ae-11.r08.chcgil09.us.bb.gin.ntt.net [129.250.9.121]
8 23 ms 26 ms 23 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
9 72 ms 70 ms 71 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 74 ms 76 ms 75 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
11 74 ms 75 ms 75 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
12 * 75 ms * 204.2.229.230
13 76 ms 75 ms 76 ms 204.2.229.9

Can confirm I have the exact same issue at the exact same nodes. The 'ae-##.r##.snjsca04.us.bb.gin.ntt.net' hop has become a big packet dropper. Over a 10 min period, it can range anywhere from 5%-50% dropped packets in the evenings over a 10 min period.

I have Wave Broadband, live in the Bay Area (very close to the servers!), and never had a problem with lag until very recently. This NTT hop in San Jose is the new bane of my existence.

Bump.

It definitely has been this way for me as well since Christmas, and originally I thought it was my Aunt's poor internet. I didn't realize this was a constant thing until I was in the middle of an Endwalker EX2 run.

All of last week barring New Years Eve (surprisingly the pings were normal) at exactly 7pm pst or a couple minutes before 7 to roughly 9:45-10:30, my ping would spike from 25ms to 120-300ms. I sent a bug report as advised by their support but I'm not sure what else I can do aside from waiting that Square Enix can acknowledge some form of connectivity issue as my ISP can't detect no issues and everything else as far as my internet is concerned is normal. Never had this issue before in the past and I'm worried that this is going to affect my static groups raid times as the evenings generally work.

Having the same problem from Northern VA on Verizon FiOS. My latency doubles and drops anywhere from 5-15% of my packets to 204.2.229.10 and 204.2.229.9, specifically in this time range.

Quote:

---

Originally Posted by Zinzu

Having the same problem from Northern VA on Verizon FiOS. My latency doubles and drops anywhere from 5-15% of my packets to 204.2.229.10 and 204.2.229.9, specifically in this time range.

---

I am also in Northern Virginia and have the same issue. I've also tried VPNing into different areas (Chicago, Texas, etc.) and that same problem node keeps appearing.

Yeah, same thing has been happening for me this evening. East coast US. I noticed it earlier in the afternoon but it stopped, so I didn't pay it much mind. But it started hitting me pretty hard this evening, to the point I didn't feel comfortable registering for any duties that might affect other players, so I called it a night. I've ran many, many speed tests and checked my connection otherwise. There is nothing wrong with my internet.