Bad lag again with NTT's NA server network

[MiraZurha]

I followed this thread when it first kicked off as I was experiencing the wild and crazy ATT lag like everyone else. Since it was largely resolved for most users, I haven't seen any more issues. I haven't yet (knock on wood) had my latency issues return.
That said, when the server went funky a few minutes ago, I had to hop over to see if it may be related. Like n_n's post, my friend was playing frontlines and got kicked. When he returned, whole alliances were missing from the match. About 5-10 minutes later, while I was rearranging hot bars, I got the boot too. Now waiting in the queue.



Just adding my voice here that the server connection and latency issues experienced in NA these last few months have been seriously concerning. As someone with thousands of hours, these past few quarters have been the worst condition of quality and reliability I've seen so far. I've got my finger's crossed that it gets better.

[Janyd]

Ah, so the servers had a hiccup just now? That checks out.

I'll be keeping my VPN subscription handy for at least the rest of the month as a backup plan since I can afford to do so. But it's fine, I've done worse with my spare change.

[n_n]

My ping is at a steady 68~69 now, so it's not 100% back to normal for me... but better than the awful 120 earlier.
Here's hoping it behaves now...

[Janyd]

Hovering at 59 to 60 ms for me with ping commands.

[Krojack]

I'm at a solid 56ms which is normal for me.

[Khryseis_Astra]

Got kicked off earlier and had over 500 in queue to get back in. After I got back in, lag was still there for me. Looks like LA is gone and I'm back on the crappy San Jose route...if they're doing anything at all, it's just shuffling the problem around and I'm unfortunately always on a bad route it seems! I've never had issues lasting over a month like this before...

Tonight's trace...
8 28 ms 20 ms 13 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 25 ms 28 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 32 ms 31 ms 23 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 19 ms 26 ms 24 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 29 ms 33 ms 24 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 29 ms 31 ms 33 ms ae-3.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.144]
14 * 80 ms 87 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 88 ms 87 ms 146 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 85 ms 83 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * * Request timed out.
18 83 ms 84 ms 83 ms 204.2.29.122

[SaberMaxwell]

Got kicked off earlier and had over 500 in queue to get back in. After I got back in, lag was still there for me. Looks like LA is gone and I'm back on the crappy San Jose route...if they're doing anything at all, it's just shuffling the problem around and I'm unfortunately always on a bad route it seems! I've never had issues lasting over a month like this before...

Tonight's trace...
8 28 ms 20 ms 13 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 25 ms 28 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 32 ms 31 ms 23 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 19 ms 26 ms 24 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 29 ms 33 ms 24 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 29 ms 31 ms 33 ms ae-3.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.144]
14 * 80 ms 87 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 88 ms 87 ms 146 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 85 ms 83 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * * Request timed out.
18 83 ms 84 ms 83 ms 204.2.29.122

I ran several traceroutes myself and had similar results; the penultimate node times out consistently. For me that node's IP address is 204.2.29.241 and my target IP is 204.2.29.79.

Past two weeks I've had so many issues with disconnecting, rubberbanding, and insane amounts of packet loss. Game is virtually unplayable like this for me :/

[Kaitlen]

I was recently in the US for vacation (east coast) and I actually had a worse experience trying to play on a Verizon FIOS line.
It was okay except for certain times of the day where it was impossible to do anything.

Came back home and connection remains stable (refer to my previous posts in this thread).

Tracing route to 204.2.29.98 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 2 ms 118.23.27.227
3 5 ms 4 ms 2 ms 118.23.27.17
4 5 ms 4 ms 5 ms 118.23.4.1
5 5 ms 2 ms 4 ms 180.8.126.45
6 6 ms 3 ms 3 ms 118.23.168.145
7 3 ms 3 ms 3 ms ae-5.r03.tokyjp05.jp.bb.gin.ntt.net [120.88.53.25]
8 3 ms 3 ms 3 ms ae-4.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.34]
9 118 ms 107 ms 106 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 115 ms 109 ms 110 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 113 ms 112 ms 114 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 113 ms 112 ms 111 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * * * Request timed out.
14 110 ms 111 ms 110 ms 204.2.29.98

Trace complete.

The irony of being further way from the SE NA DC, but having a more stable connection than when on same continent as the DC. lol...

[Merricat]

Just chiming in to say that while my connection has vastly improved from what it was in May, it is still not back to normal. It's really frustrating that something completely out of our control can affect us like this, with seemingly no recourse.

[Sorjal]

Nothing to see here, everything's normal... (below is a little over 6 hours of PingPlotter to the Exodus server) with additional spikes brought to you by Comcast, home of Xfinity.