Bad lag again with NTT's NA server network

[Epoxen]

Been having similar issues for the last few days as well. I haven't had any connection issues prior to this aside from when the servers have been DDOSed and gameplay is usually smooth as butter. Currently however, players and NPCs are sliding around, rubber banding, actions - even bringing up retainers - taking a while to register, enemy attacks and AoEs happen all at once as the game tries to catch up, a few disconnects, etc. The game is basically unplayable in any real capacity for me currently.

My connection is rock solid with everything aside from FFXIV. Running the Windows version and in Massachusetts using Xfinity.

[DariRyusei]

Been there, done that. Nobody that's high enough to do anything is in contact with any of the customers. Spectrum's answer was basically a shrug and "iunno man, ain't our issue, sucks for ya tho".

Forgive me if this sounds rude or cross, but hasn't one of the posters in this thread isolated the problem area and identified precisely where the problem is happening -- that is, NTT's San Jose node? I admit I don't know or understand what Squeenix's back-end policies and practices regarding this sort of thing are, but it seems a large waste of time and energy to cast the net wide when the exact area of the problem may have already been determined.

[KiyoKatsumi]

This has been going on since Monday/Tuesday Night this week.
I have run the traceroute and sent in an error report to Square.
I have Spectrum in OH. Not my net, it's 940mbps down/41 up. Everything else works, no lag elsewhere, I host a server on MC too and no lag for my friend in Portugal.

I'm not getting bounced to San Jose with the traceroute, but getting bounced from Ohio to ASBNVA to PARIS FREAKING FRANCE before it decides to request time out the rest of the route.

By the twelve, I just wanted to do roulettes tonight. I don't want to mess with a VPN.

[Mayaka]

I would like to second the issue being with an NTT San Jose node. I ran multiple traceroutes over the course of an hour, from two different IP addresses (located in the same place), and the issue popped up in the same spot every time. Please see below (with some unrelated nodes removed for privacy):

8 68 ms 54 ms 50 ms ae-25.a06.chcgil09.us.bb.gin.ntt.net [129.250.8.61]
9 40 ms 56 ms 51 ms ae-10.r23.chcgil09.us.bb.gin.ntt.net [129.250.3.37]
10 50 ms 49 ms 49 ms ae-11.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.138]
11 * 92 ms 48 ms ae-0.a05.asbnva02.us.bb.gin.ntt.net [129.250.3.242]
12 * * * Request timed out.
13 * * * Request timed out.
14 326 ms * * ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 297 ms 345 ms 323 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 354 ms 466 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * * Request timed out.
18 347 ms 368 ms 316 ms 204.2.29.122

See above the two request timeouts before connecting to the San Jose node snjsca04 129.250.6.237.

The next traceroute I ran, however, came out like this:

8 114 ms 50 ms 73 ms ae-25.a06.chcgil09.us.bb.gin.ntt.net [129.250.8.61]
9 124 ms 44 ms 52 ms ae-10.r23.chcgil09.us.bb.gin.ntt.net [129.250.3.37]
10 64 ms 49 ms 52 ms ae-11.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.138]
11 * 154 ms 55 ms ae-0.a05.asbnva02.us.bb.gin.ntt.net [129.250.3.242]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I continued to experience this for the past hour. Every single time, without fail, traceroute shows the issue beginning on the 12th hop after leaving Ashburn. The issue began around 4 or 5am Eastern time for me, and got progressively worse. Multiple times I was disconnected from the game, with the game closing itself once. I also wasn't able to receive messages in the chat, although strangely enough, my party was able to see my messages. I want to emphasize that my internet is otherwise working fine, and I'm able to be in VoIP calls, browse websites, stream videos, and so on, with 300+ Mbps. I was also able to connect and play just fine on Japan servers just fine while this issue was going on (Elemental/Kujata to be precise).

Multiple people with multiple ISPs in Eastern NA are experiencing this same issue that seems to correlate with a particular San Jose node. While playing with my friend who's in Washington state, he had no such issue. There may be a problem with the way players in Eastern US/Canada are being routed to the server.

EDIT: Speak of the devil, just after submitting this reply, I got disconnected from the server with a 90003 error. Traceroute looks exactly the same as above.

EDIT 2: Tested with a VPN routing me through Seattle. The repeated timeouts never occurred, and it never seems to have attempted to connect to ae-2.r2d.snjsca04 129.250.6.237. Here is the traceroute for that one, note the difference in IP addresses between ae-2.r2d.snjsca04 (the one mentioned in my previous traceroute, repeatedly seen in traceroutes posted by players on at least 4 different sites over the past week), and the instances of snjsca04 here (connected to in this traceroute with minor to no issues in comparison):

1 99 ms 101 ms 99 ms [removed]
2 111 ms 100 ms 101 ms [removed]
3 100 ms 111 ms 106 ms ae-50.a03.sttlwa01.us.bb.gin.ntt.net [128.241.15.49]
4 101 ms 104 ms 115 ms ae-3.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.206]
5 119 ms 116 ms 134 ms ae-3.r25.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
6 134 ms 119 ms 122 ms ae-1.a03.snjsca04.us.bb.gin.ntt.net [129.250.2.191]
7 * * * Request timed out.
8 121 ms 117 ms 117 ms ae-6.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.158]
9 121 ms 138 ms 120 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 121 ms 120 ms 123 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 121 ms * 122 ms 204.2.29.241
12 118 ms 121 ms 123 ms 204.2.29.122

[Maxilor]

12:51 AM EST Packet Loss and Disconnected Again.

[ChewieFlakes]

Every god damned night at the same time for the past two weeks, unplayable lag and constant 90k/2k disconnects. Spectrum, NE coast. Internet connection is perfectly fine and this is the only game affected. How long is this crap going to continue?

[Britha]

Every god damned night at the same time for the past two weeks, unplayable lag and constant 90k/2k disconnects. Spectrum, NE coast. Internet connection is perfectly fine and this is the only game affected. How long is this crap going to continue?

I agree. I've avoided posting and have been sending in trace route to the link provided but nothing seems to be happening. This is utterly ridiculous and contacting our ISP does nothing, they just give us the runaround and excuses.

[DariRyusei]

Confirmed, it is indeed Happening Again. Several people have identified the exact problem, and from what it looks like -- though I admit I'm not experienced with such matters, so I have no clue if there's additional concerns that I'm not aware of -- these people have also provided Square-Enix with literally the exact location of the issue. They have the "who", "what", "when", "where", AND "why". So I'm confused as to why this continues, and why Square-Enix seems to be sitting on all the information they need rather than taking action. Again, though, I don't know if there are more considerations that I am unaware of.

[CaptainTaz]

A Canadian friend in Ontario, and I in eastern PA are both seeing issues for the past week, every evening around 12:30-1AM we're getting the disconnection errors. This has been really a sour note on our evening grind sessions and I hope someone at SE can assist with getting this fixed sooner rather than later.

[RhaesDaenys]

Had this happen for the first time too... east coast.