Bad lag again with NTT's NA server network

Still holding steady here too:

Code:

---

  5    *        *        *    Request timed out.
  6    14 ms    14 ms    14 ms  32.130.17.75
  7    20 ms    13 ms    15 ms  cgcil402igs.ip.att.net [12.122.133.161]
  8    13 ms    14 ms    21 ms  192.205.32.194
  9    14 ms    13 ms    15 ms  ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
 10    *      79 ms    *    ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 11    *        *      63 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 12    63 ms    63 ms    63 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 13    *        *        *    Request timed out.
 14    62 ms    63 ms    62 ms  204.2.29.6

Trace complete.

---

Given that we had one nice day last week, I'm not holding my breath on this one; I'll want to see a couple weeks of good connections before I resub. But at least I was able to run a couple raids today and grab some gear I needed before my sub expires.

Hopefully this is actually a positive change, but I'm not crossing my fingers at this point. I'm wondering if tonight being the "early" release day for Diablo 4 is affecting traffic enough to make a dent.

I'd say it's absolutely Diablo 4, or at least a part of it. I'm currently trying to play D4 but of course ps5 ppl can't get in lol.

Have tons of luck this month with games. At least ffxiv is actually working atm.

D4 servers have barely been up for like, an hour. Latency and packet loss would start happening long before - this reprieve is NOT because of D4. That said, I am not celebrating as we had a short lived moment last Friday evening. Until my tracerts show normal latency for at least a week (7 days in a row), I am operating under the assumption that the issue is not fixed.

Hope everyone who is trying out D4 enjoys! I'll be joining in when I'm not progging savage.

Anyone planning to play SF6 instead of just Diablo 4 while we continue updates on 14 hell lol

Quote:

---

Originally Posted by Legacii

Anyone planning to play SF6 instead of just Diablo 4 while we continue updates on 14 hell lol

---

Not tonight because work tomorrow, but I'm probably playing a fair amount of SF6 this weekend, yeah. Gotta poke my head out of the retirement home once in a while.

I could see both Diablo IV and Street Fighter 6 having an effect on the load, to the benefit of FFXIV.

Despite Blizzard's... ownership being all kinds of words that would get me banned here, there's no denying people are going to play D4.

But, so far so good tonight. I was busy with work last Friday, so I didn't get to notice that effect much.

Let's hope it holds. Being more of a casual player, I got done with Pandy finally and now it's just time to level island, pile up coweries, and do roulettes to upgrade gear..IF this holds. I can do island with lag since I got things set up in such a way that all I have to do is plant crops, gather what I don't have, set up what the mammets have to make and that kinda thing. Roulettes..I don't DARE when I'm lagging. A laggy whm is a very unhappy whm who can't heal worth stink.

If it holds it also means my brother can come back and maybe he can get though that fight-as-a-certain-npc instance (I won't say what b/c I don't see a spoiler button; I don't know where everyone in this thread is and I don't like being spoiled, won't do it to someone else) in Shadowbringers that he couldn't pass b/c of the lag, he swore it was killing him on EASY when it shouldn't have. Lag, much?

Gonna be honest i hope this got fixed and I hope we don't have to suffer on the weekend with packet loss again. but I will take it and play as much as I can before it spikes up again.

...end game content is relatively unplayable right now. Any updates? I'm supposed to have high speed in Texas, and every step is 40 ms and up.

Last night I didnt have any lag. There was a wierd time around 1pm est yesterday where my connection got really bad and jumped to 400ms and the login screen was showing connection poor but that was only for 5 minutes. After that I had excellent connection and no lag spikes the remaineder of the day. It looks like they are working on it but this weekend will be the real telling factor.

Last night in a leveling roulette, both the tank and the healer were having bad lag that wiped us multiple times. Unsure if it was the same issue or a weird coincidence, though. My hotspot is still working as well as it normally does, but I hope I can start using my fiber connection soon... If this thread still has positive posts by tonight, I may give it a try in Frontline just to see.

I've been raiding using Mudfish so I don't have any bad experiences week 1, but decided to check the thread how things were doing, which is not good at all, until maybe last night.

Through my router, just now at 11:55 AM EDT, my router is pinging Crystal-Coeurl for a very consistent and 'normal' 61.27ms - 65.11ms range. 'Normal' because we know they're capable of bringing our latency down another 5ms or so. I will report back in either an update if not too many people posted, or a new post, at around 4:30 PM EDT for those results, and one more time closer to 9 PM EDT.

I personally don't think anyone should be getting hopeful. NTT and ATT are both being trash fire right now, and it's very hot outside, so they reek too.

Lets hope it's fixed for real this time and not toying with us.

At 2pm EST yesterday it dropped down then dropped to normal around 11:30pm EST. So far today it's been fine.

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

Update @ 4:30pm EST: Mine is still holding solid at 55ms ping. This is my original ping since about pre-April 7th after which my ping went up to 62ms avg.

Almost 3pm eastern and still steady. The Friday trend may continue and tomorrow will be the real test

6 11 ms 14 ms 14 ms cgcil402igs.ip.att.net [12.122.133.161]
7 9 ms 8 ms 9 ms 192.205.32.194
8 8 ms 8 ms 8 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 55 ms 57 ms 58 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 58 ms 58 ms 58 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 61 ms 58 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 58 ms * 58 ms 204.2.29.241
13 62 ms 58 ms 58 ms 204.2.29.6

I hope tomorrow it stays this way so I can start working on my gear and so 'Neko can finally get though that fight that was vexing him ^^ Let's hope guys.

4:30 PM EDT update, Router is pinging Crystal-Coeurl and I'm seeing a nice and steady 60ms-63ms pings. Not broken yet. Will post closer to the evening when all the raiders and Warriors of Light log in.

Roughly the same as yesterday for me too:

Code:

---

  5    *        *        *    Request timed out.
  6    17 ms    15 ms    15 ms  32.130.17.75
  7    15 ms    15 ms    14 ms  cgcil402igs.ip.att.net [12.122.133.161]
  8    14 ms    13 ms    13 ms  192.205.32.194
  9    25 ms    18 ms    20 ms  ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
 10    *      60 ms    62 ms  ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 11    64 ms    75 ms    64 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 12    67 ms    65 ms    63 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 13    63 ms    *        *    204.2.29.241
 14    63 ms    64 ms    62 ms  204.2.29.6

Trace complete.

---

Game is at least playable at the moment. But like I said yesterday, until I see consistent good connection for a couple weeks at least, I'm gonna consider this a fluke like last week.

8 32 ms 36 ms 31 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 29 ms 33 ms 30 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 104 ms * 100 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 60 ms 60 ms 61 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 60 ms 60 ms 67 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 61 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 60 ms 60 ms * 204.2.29.241
15 60 ms 59 ms 59 ms 204.2.29.122

As you can see, holding steady-ish for now as well. Oddly enough, I'm being routed through Dallas to LA to Sacramento, and not Dallas to San Jose to Sacramento.

Perhaps they're slightly easing the load by changing up the pathing between the central parts of the US and California?

Seems to me that those that got routed through Chicago and through Dallas are having some small, small variances in ms.

I hope the connection stays stable during the weekend. Plus I know the severs have been a bit of a fluke lately. they just posted something about congested severs with dc travel not to long ago. i know that doesn't affect the situation where in atm. But gonna stay vigilant about this.

Quote:

---

Originally Posted by RyuezaneWithersoul

I hope the connection stays stable during the weekend. Plus I know the severs have been a bit of a fluke lately. they just posted something about congested severs with dc travel not to long ago. i know that doesn't affect the situation where in atm. But gonna stay vigilant about this.

---

I completely agree. Be vigilant.

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.

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

---

2nd day in a row of normal hops. Not celebrating yet, let's see how it goes throughout the next week.

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.

Chiming in again. I've been following and glad to see so many positive posts. Hopeful, but not going to resub just yet. I'll wait until it's reasonable to believe everything is fixed and stable.

Also want to thank everyone for keeping this thread going with reports. Without a sub, it's the only way many of us have to know what the playing conditions are. So, thank you!

Page 100! I did quite a few dungeons and trials last night with no noticeable issues. Hoping it's not a fake out like last week!

Cleared p9s last night with a stable connection and no issues on AT&T. Looks good to me.

Last night after work I completely forgot to enable Nord VPN before logging on and I experienced zero lag on my end. I did see a couple of players rush forward really fast during two separate duties but no rubberbanding and no failure of abilities to proc. It was lag/latency free for me last night without using a VPN.

Just ran my usual ping commands on the lobby and Aether DC IPs... both coming in around 58ms and 60ms each.

So far so good.

Just chiming in that I've been off the VPN and raiding, stable 60ms all day. Still not hopeful.

Chiming in that I am still receiving 80+ms on lsanca07 node, but everything else is normal ms. (Trace run without VPN.) I'm still playing on VPN though, because I have lost faith in the connection.

Chiming in as a PS5 player, that as of right now, connection seems stable. Connection is logged as excellent and I just complete a Nier raid. I also just stood around Limsa with no issues. {All during 5pm to 630pm EST} {ATT Fiber/ East NA}

Well, haven't slapped on Cloudflare Warp all day tho I'm leaving it on my pc for now out of paranoia. If 'Neko can log on and get though that instance I'll be happy, I swear the lag was messing him up bigtime.

Let's hope this holds.

Seems the connection is stable to night i hope it pulls through the week. !