Bad lag again with NTT's NA server network

[Sorjal]

Another day, another tracert (this time with .29 instead of .92 )

Tracing route to 204.2.29.122 over a maximum of 30 hops

1 2 ms 1 ms 1 ms <removed>
2 21 ms 13 ms 11 ms <removed>
3 15 ms 15 ms 11 ms <removed>
4 16 ms 15 ms 19 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 17 ms 17 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 20 ms 25 ms 21 ms 75.149.231.250
7 46 ms 65 ms 54 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 145 ms 122 ms 84 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 103 ms 86 ms 83 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 90 ms 93 ms 88 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * 91 ms * 204.2.29.241
12 91 ms 84 ms 85 ms 204.2.29.122

Trace complete.

[n_n]

I just logged on and it looks like my ping has shot from mid 50s to low 100s-109 today (the same numbers when connecting through the broken NTT node a month or so ago). Currently, it doesn't seem to be dropping packets when I check via command prompt, but if this issue is actually back and my method to "fix" it no longer works, then I won't be renewing my game time next week.

[Krojack]

Yup, lag and some packet loss started at exactly 6:19pm EST

Edit: Doesn't matter what VPN node I use, same out come. Either NTT is being DDoSed or someone messed up their routing (again?).

[n_n]

Thanks for your graph. Krojack.
Yeah, no matter what connection I use, I get the same result. The game is still playable at the moment, though. I'm not getting the crazy packet drops like before where it felt like ages to register actions/combos/etc. I just did some roulettes and I also didn't see people stopping in place.

[Janyd]

Aye, it's showing up as "Good" on Aether when I'm normally on "Excellent" again.

I'm beginning to think this might just be a DDoS on the nodes or somewhere in the network since I'm not getting really any packet loss either.



1 <1 ms <1 ms <1 ms (REDACTED)
2 18 ms 17 ms 18 ms (REDACTED)
3 18 ms 18 ms 19 ms (REDACTED)
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 33 ms 31 ms 31 ms (REDACTED)
8 30 ms 26 ms 25 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * * * Request timed out.
10 85 ms 85 ms 89 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 109 ms 109 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 * * * Request timed out.
13 108 ms 107 ms 107 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 104 ms 102 ms * 204.2.29.241
15 107 ms 104 ms 100 ms 204.2.29.122

EDIT (8:50 PM CDT): Okay, logging in shows as "Excellent" again and I'm really not noticing anything different when crafting things. Hmm, might be a temporary bug? We'll have to see.

[radhaz]

it's back, 3:19 PST Monterey CA. Ping was 25ms, now 80 plus with lost packets. So far Warp gets it back to normal.

[Khryseis_Astra]

This is the 4th week in a row of near constant lag for me... my connection status has said excellent on login throughout it all, but tonight it said good instead. Still seeing the high numbers/packet loss occurring inside NTT at LA (it was San Jose before, but that doesn't appear in my traces anymore) and Sacramento. Submitted the following trace to SE tonight:

8 18 ms 17 ms 17 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 23 ms 22 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 27 ms 29 ms 31 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 24 ms 23 ms 30 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 36 ms 33 ms 25 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 29 ms 33 ms 27 ms ae-2.r25.asbnva02.us.bb.gin.ntt.net [129.250.2.124]
14 85 ms 95 ms 91 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
15 93 ms 85 ms 96 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
16 101 ms 95 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
17 * 112 ms * ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
18 96 ms 102 ms 97 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 * * * Request timed out.
20 98 ms 100 ms 103 ms 204.2.29.122

[Janyd]

Yeah, went back to normal within the last hour or two, it seems.

Hopefully, it was just an anomaly or a DDoS that's been dealt with.

[n_n]

It's still acting weird for me, although the numbers have improved since earlier. My ping currently fluctuates wildy between early 50s to late 70s. (normally it is a stable 54-56)