I completely agree. Be vigilant.Quote:
Originally Posted by RyuezaneWithersoul
Printable View
I completely agree. Be vigilant.Quote:
Originally Posted by RyuezaneWithersoul
Heres to hoping it holds
https://cdn.discordapp.com/attachmen...3202/image.png
June 2nd 6:30 (ish) pm S. FL Dish (Uses ATT Fiber)
2 78 ms 31 ms 29 ms 10.40.159.1
3 37 ms 40 ms 36 ms 12.244.143.181
4 26 ms 24 ms 38 ms 12.123.6.38
5 38 ms 87 ms 39 ms fldfl401igs.ip.att.net [12.122.155.169]
6 99 ms 71 ms 72 ms 192.205.35.118
7 14 ms 14 ms 18 ms ae-7.r23.miamfl02.us.bb.gin.ntt.net [129.250.2.109]
8 39 ms 37 ms 41 ms ae-4.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
9 38 ms 39 ms 38 ms ae-0.r25.asbnva02.us.bb.gin.ntt.net [129.250.2.36]
10 85 ms 98 ms 71 ms ae-4.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.117]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
Ping statistics for 204.2.29.122:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 339ms, Average = 79ms
Trouble used to begin at Sacramento node. Sacramento not showing up on tracer route. I used to begin time out at hop 14, think that is a setting on the other end. Now I begin timing out on the 11th hop. (No idea what this means if anything) Zero packet loss, I know that is GOOD...yea! 73ms is a bit higher than what I was getting three weeks ago but I'll take it if the game is playable. Maximum is scary at 339ms. Just glad to finally see what I think is momentum in the right direction.
EDIT: Just connected to game; first time I've had an Excellent connection in weeks. Something must have been done and if so I'm thankful. Not happy with the lack of communication (bad news or good) but will be pleased if this holds.
Just made an account to chime in, despite following this thread for the past few weeks.
I have AT&T Fiber, live near San Jose, and never had any issues until a few weeks ago. For the past few weeks, I've gotten around the packet loss with PIA VPN, but completely understand if other can't or don't on principle want to go that route.
Reporting that yesterday was the first day I could play with no packet loss, and noticed no rubber banding at all. Trace records since yesterday have also been near perfection, but again like so many of you, I'm not going to believe this is fixed until we get at least a week of clean peering through NTT's nodes.
Trace route as of right now:
Tracing route to 204.2.29.122 over a maximum of 30 hops
1 1 ms <1 ms <1 ms RT-AX88U-A188 [192.168.50.1]
2 2 ms 2 ms 1 ms 192.168.1.254
3 4 ms 3 ms 3 ms 162-226-172-1.lightspeed.sntcca.sbcglobal.net [162.226.172.1]
4 3 ms 3 ms 3 ms 71.148.149.102
5 5 ms 6 ms 7 ms 12.242.117.22
6 13 ms 19 ms 20 ms 192.205.37.58
7 6 ms 6 ms 9 ms ae-9.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
8 8 ms 13 ms 8 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
9 10 ms 10 ms 12 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
10 * * * Request timed out.
11 9 ms 9 ms 9 ms 204.2.29.122
Trace complete.
Update: The last three days I have had an Excellent connection to FFXIV, will check back in a few days, hope this continues.
ATT Fiber customer.
Still good with me as well, no issues so far today or yesterday. Hoping it's actually fixed but the last two weeks have made all of us doubtful for good reason.
Hopefully next time we don't have to worry every time a new patch is about to drop instead of being excited for new content.
2nd day in a row of normal hops. Not celebrating yet, let's see how it goes throughout the next week.Quote:
3 6 ms 3 ms 4 ms 71.155.29.140
4 * * * Request timed out.
5 14 ms 7 ms 7 ms 32.130.25.65
6 18 ms 15 ms 17 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
7 13 ms 11 ms 11 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
8 83 ms 83 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 57 ms 45 ms 43 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 42 ms 57 ms 45 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 43 ms 43 ms 43 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * 45 ms 204.2.29.241
13 42 ms 43 ms 43 ms 204.2.29.6
EDIT: Didn't notice it at first glance but still an issue with lsanca07 node. Shame.
9:30 PM EDT, still having a solid connection. Latest trace route is showing good results still. No funny hops or bad connections, I'm going through 192.205.32.194 into ae-4 chicago/illinois 9 (192.250.4.239) straight to ae-4 Sacramento-03 (129.250.7.57) and then to another Sacramento server then hitting XIV. All jumps once in Cali are sub 1ms.
Frontline went pretty well tonight. Very slight lag at the start, but it cleared up and was fine after. Fingers crossed it stays ok. But we'll see...
This is my tracetroute 5 * * * Request timed out.
6 * * * Request timed out.
7 11 ms 7 ms 7 ms 32.130.25.65
8 33 ms 33 ms 36 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * * * Request timed out.
10 * * * Request timed out.
11 43 ms 44 ms 43 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 44 ms 50 ms 44 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 44 ms 44 ms 44 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * * Request timed out.
15 44 ms 43 ms 43 ms 204.2.29.196
16 44 ms 44 ms 43 ms 204.2.29.12
Hopefully, it sticks through the weekend.