Bad lag again with NTT's NA server network

[Monochii]

The Chicago node's in flux? Curious.

I usually don't get sent there, I go through the Dallas node before the California ones.

Still, primetime doesn't start for another hour or two, so, we'll see what happens.

Yea it was weird one, now it mostly just San Jose and 204.2.29.241 now with any packet loss %. I should've mention to as far as I understand it doesn't really matter if a few hops get packet loss as long as the end destination connection or whatever isn't dropping any. Usually what weve been seeing lately is almost every NTT node is dropping packets somewhat. This is better so far.....

But yes, want to mention I've actually had Pingplotter up for an hour on accident but averaging still around 70ms to 75ms on Aether from East Coast with no dropped packets.

Cross our fingers. Again it was like this Friday then back to business as usual the next day. Hopefully this time it'll stick....

Try playing without a VPN if your willing all and pressure the connection tonight. Enjoy it why we can lol.

[Elizara]

Without Cloudflare Warp (still using it out of paranoia) I get a VERY nasty spike on ae-2.r24.lsanca07.us.bb.gin.ntt.net and on pingplotter, it's in yellow; avg on that node is 117. But it's the ONLY node in yellow.

Otherwise it's all green and I was finally able to get though all but the last part of the new raids. (and I mean the normals, I usualy don't do the extreme versions). Monochii; I hope it holds for crying out loud and then maybe me and 'Neko can be back in da house, not just this kitty. (I didn't finish it up b/c I had some rl stuff to do; that comes before game always.)

[Rekts]

Yeah not having any issues here either, but I'm not holding my breath. We got one good Friday night before this too. If it's lasts the rest of tonight all the way through tomorrow, maybe I'll hold my breath. Maybe.

[n_n]

Posting to confirm that my regular connection toward the game's servers is acting normal again just like others in this thread have reported today. We'll see how long that lasts.
I'm still directing the game's connection through my AWS proxy to be safe, though.

[Janyd]

Gonna throw on the traceroute I took just now, and then go out for dinner.
Hops are listed as such, starting at the NTT nodes, just to avoid doxxing of course.


8 54 ms 33 ms 30 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * 31 ms * ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 * * * Request timed out.
11 68 ms 61 ms 59 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 62 ms 73 ms 60 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 60 ms 61 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * 60 ms 204.2.29.241
15 60 ms 60 ms 59 ms 204.2.29.122

[TaleraRistain]

Also seeing some magical sorcery going on at 7pm eastern. Ran earlier today around 1pm and it was the same.

I have the axe standing at the ready, though.

I'm progging EX6 tonight so I'm still going to use my VPN and keep an eye out for whether the behavior is maintained before I trust the normal connection

5 10 ms 12 ms 14 ms 32.130.17.75
6 15 ms 14 ms 15 ms cgcil402igs.ip.att.net [12.122.133.161]
7 17 ms 8 ms 7 ms 192.205.32.194
8 9 ms 8 ms 8 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 * * * Request timed out.
10 88 ms 58 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 58 ms 58 ms 58 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 58 ms * * 204.2.29.241
13 58 ms 58 ms 58 ms 204.2.29.6

[gameofscones]

Still holding steady here too:

  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.

[Illyrian94]

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.

[Rekts]

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.

[Lahtori]

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.