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.

It's NTT again.

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

Can we please get a bump on this? I've reported the same issue in several threads and it's making it very difficult to run anything in the evening. This isn't an ISP issue with our providers, this is NTT or whomever y'all are using for your datacenters.

I knew it was too good to be true when I saw a reply saying it got fixed after the patch. It was fine yesterday for me as normal around 7 pm and thankfully my static raid went fine, but now it started spiking 30 mins after 7 pm and here I am worrying once again. There's not much we can do here.


4 20 ms 19 ms 19 ms 12.242.117.22
5 180 ms 178 ms 178 ms 192.205.37.58
6 176 ms 152 ms 155 ms ae-9.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
7 152 ms 148 ms 166 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
8 184 ms 169 ms 151 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
9 * 180 ms * 204.2.229.230
10 182 ms 182 ms 135 ms 204.2.229.10

Guys, it's been a week and a half since this started. Please address whatever is happening in your network or your provider's (NTT) network.

6 9 ms 11 ms 9 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 10 ms 12 ms 12 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 12 ms 9 ms 15 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 * 46 ms 45 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 196 ms * 148 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 155 ms 140 ms 134 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 194 ms 209 ms 202 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * * Request timed out.
14 169 ms 186 ms 200 ms 204.2.229.10

Trace complete.

Quote:

---

Originally Posted by Jconix

I knew it was too good to be true when I saw a reply saying it got fixed after the patch. It was fine yesterday for me as normal around 7 pm and thankfully my static raid went fine, but now it started spiking 30 mins after 7 pm and here I am worrying once again. There's not much we can do here.0

---

Same experience for me. Where did you see the reply saying it got fixed?

Quote:

---

Originally Posted by joolzy

Same experience for me. Where did you see the reply saying it got fixed?

---

It was from this thread, but it seems they said to disregard it. Honestly, I still hope there's something to be addressed.

https://forum.square-enix.com/ffxiv/...nstalled/page9

I submitted a ticket to their support this evening and was given the typical copy\paste template from a 1st tier support rep telling me that I need to reboot my PC, check my ports and antivirus, etc...

I'm not sure if this is standard 1st response to meet an SLA or not, but it's definitely annoyed the hell out of me. Applications, port configurations, etc may affect my game client, but it's not going to affect a damn ping response between a very specific time window.

I recommend that people with this issue start opening tickets with their support if they want to have any actual attention bought regarding this problem. Otherwise, it's too easy for them to just blow us off and say it's not their problem or responsibility to fix.

same here~! they needa fix this thing asap. T , T

Bumping this... Started again like clockwork tonight at 7pm PST. It's always ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]

My ping went from 65ms to 220ms.

The only way this will get fixed is if someone from SE yells at NTT to fix it.

Bump. Same issue again tonight. Started around 9pm CST. Same node within NTT's network in San Jose.
The support ticket I have they stated that they have numerous reports of this and they are working on it. Take that as you will.

Quote:

---

Originally Posted by Liralara

Bump. Same issue again tonight. Started around 9pm CST. Same node within NTT's network in San Jose.
The support ticket I have they stated that they have numerous reports of this and they are working on it. Take that as you will.

---

Well, on the plus side they are at least aware of it. That's what these threads have been trying to accomplish.

I have this same exact thing too! I live near Los Angeles, CA, and every night from 7pm~11pm-ish there's unplayable lag. Please fix this!

Bumping this thread too. I'm so tired of not being able to raid with my team because of this unplayable lag. Happens almost every night starting at 9:00 CST consistently.

Also bumping this thread by posting a reply of my own. Having the same exact issues with the San Jose node and having the same lag spikes from the same general time frame of around 7pm-10pm PST. Please fix this issue Square Enix....

I'm also having the same issue with my ping spiking at a certain point during the evening, but now my ping has been spiking throughout the whole day. I'm sure its not my ISP, because everything else on my computer runs fine.

Bump, same issue since Monday the 10th, unplayable lag spikes in the afternoon/night, same as others ISP is not the issue since everything else works just fine.

Bumping for weekly update,

Today: No sudden spikes on the usual time. It spiked just a tad bit around 9:10 pm pst but settled down to normal ping right after.

Still having high ping episodes as detailed in this thread. Problem is still not resolved.

Another night, another bump... Same exact thing on snjsca04. Does SE support even look in these threads? This lack of communication not encouraging.

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.254
2 19 ms 18 ms 19 ms 76-206-252-1.lightspeed.irvnca.sbcglobal.net [76.206.252.1]
3 19 ms 19 ms 19 ms 70.232.228.61
4 26 ms 23 ms 23 ms 12.123.30.210
5 23 ms 23 ms 23 ms ggr2.la2ca.ip.att.net [12.122.128.101]
6 50 ms 49 ms 44 ms ae-5.a02.lsanca20.us.bb.gin.ntt.net [129.250.9.61]
7 * 58 ms 52 ms ae-1.r25.lsanca07.us.bb.gin.ntt.net [129.250.2.115]
8 * 154 ms * ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
9 156 ms 171 ms 174 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
10 140 ms 129 ms 116 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
11 142 ms * * 204.2.229.230
12 185 ms 185 ms 191 ms 204.2.229.10

Trace complete.

Been bad. Continues to be bad.

Yep, throwing in my traceroute to the pile.


9 45 ms 46 ms 39 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
10 47 ms 44 ms 46 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
11 64 ms 63 ms 64 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 212 ms 222 ms 187 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 223 ms 219 ms 200 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 221 ms 224 ms 221 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 184 ms 190 ms 221 ms 204.2.229.230
16 209 ms 173 ms 156 ms 204.2.229.9

SE and NTT are long overdue for an investigation of the San Jose nodes.

ikr, come on plz. I am here to escape real life issues and looking at this just reminds me how little care we are really getting. I am paying money to feel worthless. Its been a whole month with this issue, and nothing from the official.

A very short ping spike than the normal 2-3 hours. Only 1.5 hours before it dialed back to normal and still is as of this moment. Going to keep this bumped as well as the other threads up just so hopefully Square can just notice (even if it's so slightly..)

Bumping this once more as the Ping spike returned after a couple of quiet days.

March 22nd and the ping is still unbearable at night, especially for east coast players like me. It's to the point where I would probably have a better experience playing on EU data centers rather than NA, which is frankly unacceptable.
My tracert:
11 40 ms 39 ms 41 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
12 * * * Request timed out.
13 95 ms * 92 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
14 99 ms 97 ms 92 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 98 ms 97 ms 95 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 96 ms 109 ms 97 ms 204.2.229.230
17 97 ms 100 ms 97 ms 204.2.229.10

Trace complete.

100 ms might not seem that bad, but at random points there will be massive lag spikes up to 300 ms during gameplay.

Ook ook ug ug me no understand how physics works. Unga bunga put one datacenter for multiple countries it work in Japan it work here. What you mean Japan has fraction of population? Me no understand them big words!

Seriously Square get with it and pressure NTT to update their aging nodes for the love of the twelve. Even the VPN is not working anymore, must keep switching routes every. single. day. All friends are experiencing issues making healer/tank nearly impossible to play. 420 mil, time to hire competent sysadmins and stop blaming shortages. There was 56 week lag time on acquiring new hardware, it is not unobtainable only there will be delays. Now they are installing new servers in CA when the issue is that there simply are not enough entry nodes to service so many players maaahhh!

22ms allllllll the way across Comcast ibone until you hit glorious NTT where the ping is high and the nodes smell like burning.

Tracing route to 204.2.229.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms
2 11 ms 11 ms 9 ms
3 13 ms 10 ms 12 ms
4 11 ms 10 ms 13 ms
5 14 ms 27 ms 13 ms
6 19 ms 15 ms 13 ms be-31631-cs03.pittsburgh.pa.ibone.comcast.net
7 * 21 ms 21 ms be-1311-cr11.pittsburgh.pa.ibone.comcast.net
8 17 ms 22 ms 18 ms be-301-cr12.ashburn.va.ibone.comcast.net
9 20 ms 20 ms 20 ms be-1112-cs01.ashburn.va.ibone.comcast.net
10 20 ms 17 ms 24 ms be-2111-pe11.ashburn.va.ibone.comcast.net
11 27 ms 20 ms 22 ms 50.208.234.170
12 28 ms 24 ms 23 ms ae-3.sayonara-maruf.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.144]
13 75 ms 77 ms 77 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 82 ms 76 ms 77 ms ae-4.sayonara-maruf.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 78 ms 81 ms 78 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 78 ms 78 ms 80 ms 204.2.229.1

Trace complete.

I can not remember who else this has happened to on Twitch but I remember someone who streamed contacting comcast to fix a node. They denied it being an issue until covid when so many people were working from home. It was only than when they got multiple complaints before they did anything about it.

Look I want to play the game, my vpn is also timing out no matter what routes I chose now only subsiding depending on time of day people connecting and many other factors. Connecting to Canada is impossible now and that was how I would get good ping to ffxiv. I can only imagine how it is for people with no vpn and live in Canada timing out randomly for no reason possibly getting strikes on their accounts for disconnecting. If that ever happens to me as much as I love this game I am never buying another copy or subscribe again and you will lose me a customer. There is nothing I can physically do to fix this because it a node in California. I can not contact the service provider myself because I am not a customer. Square is the customer. Call them and tell them to investigate why a ton of people are getting timed out from that location and to check to see if there is anything broken and than fix it. I also will not pay for a game I can not play.

This has caused loss progress in potd, random disconnects but only within dungeons. Out in the main world hub save for maybe one hour last week I was lagging in the over world but never kicked with the 9006 error only when going into an instance leading me to believe it is one of the connections to the instance server. I will post the trace route again when it is actually timing out but this is the route I usually am being routed through. The only thing of note is the massive ping increase when entering the NTT network.

Also for informational purposes this will happen differently for people within the same household using the same exact connection. One of us will dc and the others connection will be perfectly fine which is great for informing the team what is actually happening and the person will be back. I can infer that each character connects to the instance server through a separate channel. This has happened to multiple friends and their partners during random duties and random times of day, not even prime time.

Oh man it's been a solid 2 months since I spiked up this bad. Except tonight was even worse because my game started freezing and nobody was moving .__.;

bump
NTT at it again.

Yeah. It looks like it's happening again.

Spikes up at exactly 8 pm pst like yesterday. @_@ ugh;;