Bad lag again with NTT's NA server network

[SonicRose]

I posted yesterday, this is today at around 3 PM EST

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 2 ms 3 ms 4 ms 23-116-200-1.lightspeed.toldoh.sbcglobal.net [23.116.200.1]
3 3 ms 3 ms 3 ms 71.153.70.124
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 12 ms 13 ms 32.130.17.77
7 19 ms 12 ms 12 ms cgcil402igs.ip.att.net [12.122.132.197]
8 10 ms 13 ms 16 ms 192.205.32.194
9 12 ms 13 ms 14 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 58 ms 57 ms 59 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 118 ms 118 ms 116 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 120 ms 120 ms 117 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 118 ms * 120 ms 204.2.29.241
14 117 ms 118 ms 117 ms 204.2.29.122

The latency has improved somewhat in game and yesterday 13 was complete timeout when I ran this. Still not great, but this is also not prime time for gaming.

[Krojack]

I regret to inform it did not last long. Back to PIA + Michigan for now.

Approx NOON CST:

Yeah, the pings start going up around 11am but you won't start getting packet loss till around 1 or 2pm EST.

I've also changed over to using either Chicago or Silicon Valley nodes. While using the Silicon Valley one, Google doesn't shove a captcha in my face every few times I try to do a search.

[ntt_routing_is_an_issue]

Yeah, the pings start going up around 11am but you won't start getting packet loss till around 1 or 2pm EST.

I've also changed over to using either Chicago or Silicon Valley nodes. While using the Silicon Valley one, Google doesn't shove a captcha in my face every few times I try to do a search.

you hate to see it... times in CST

[TaleraRistain]

Yeah, the pings start going up around 11am but you won't start getting packet loss till around 1 or 2pm EST.

I've also changed over to using either Chicago or Silicon Valley nodes. While using the Silicon Valley one, Google doesn't shove a captcha in my face every few times I try to do a search.

Yep I've been checking on and off since about 1pm and I started seeing packet loss around 1:30 EDT. Haven't seen anything higher than about 7% and I'm working so I can't jump in game to test performance. Last night I was getting up to 16%. I started seeing the latency jump on that traceroute, too. So it does seem to be about a 12 hour period of good and then 12 hours of bad.

[Illyrian94]

Well. Was hoping I'd be able to hop on tonight after work, but since I can only play in peak hours, well...
Picked a real good time to resub.

[Ath192]

[MoonmoonMoonmoon]

Proton VPN is pretty good, too.

[n_n]

Well. Was hoping I'd be able to hop on tonight after work, but since I can only play in peak hours, well...
Picked a real good time to resub.

Yeah, I just resubbed 3 days ago and I regret not reading the subreddit before doing so because it's been a total waste of money so far. I have to stay up for the late hours if I want the ability to actually play the game, but because of my schedule that only ends up being about an hour of playtime. I sure hope this congestion issue with those nodes gets fixed soon because this is getting ridiculous.

[Janyd]

For what it's worth, I've been giving Cloudflare WARP a try, at the suggestion of the r/FFXIV subreddit.
Since it's free, I figured, why not? (It's available at https://1.1.1.1 for those wondering)

I ran some traceroute and ping commands and here's what I got with WARP turned on, starting again at the Dallas NTT nodes:


4 31 ms 31 ms 37 ms ae-21.a01.dllstx14.us.bb.gin.ntt.net [140.174.28.245]
5 * * * Request timed out.
6 62 ms 63 ms 66 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
7 72 ms 72 ms 72 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
8 68 ms 69 ms 69 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
9 70 ms 68 ms 69 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
10 69 ms * * 204.2.29.241
11 71 ms 72 ms 72 ms 204.2.29.122

Pinging 204.2.29.122 with 32 bytes of data:
Reply from 204.2.29.122: bytes=32 time=71ms TTL=53
Reply from 204.2.29.122: bytes=32 time=72ms TTL=53
Reply from 204.2.29.122: bytes=32 time=71ms TTL=53
Reply from 204.2.29.122: bytes=32 time=72ms TTL=53

Ping statistics for 204.2.29.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 72ms, Average = 71ms

While it's not the 50-65 ms I would get normally, issues aside, I think we've got a potential free workaround on our hands.
Of course, your mileage may vary, depending on where you live and where Cloudflare approximates your location.

[Kestaa]

FWIW

The VPN I got last night has a free 30 day trial as well, PIA (private internet access). I'm located in Central Texas / SA and am using the Iowa node with perfect results. Someone back in this thread was kind enough to post nodes that worked with PIA if you're in a different part of the US with a node that is closer / lower ms.

Edit add: I went back and forth about getting / paying for a VPN to use FFXIV. It really sucks but my 2 cents is : if worse comes to worse its about 3$ a month and I can easily cancel it when this crap storm is over. If you're looking to raid with friends I personally think its worth it. From back in my hardcore wow raiding days, it feels super crappy to let 19 other people down when you're a core member / raid leader, I can only imagine its worse for a static of 8. I'm personally trying to do last min ready-ing and do degen crafting for 6.4 so I also think a vpn worth it - since I cant craft anything atm without the VPN. Other than that, screw um. Cancel your sub and let them know why you're doing it. Go learn an instrument in the mean time or practice an irl trade craft!