Bad lag again with NTT's NA server network

[Ath192]

Cross posting for visibility

More fun with graphs now that SE has acknowledged there are some network issues in NA. First the route map:



Hop 4 is leaving AT&T's network, hop 5 obviously is entering NTT's network. First we look at our traffic statistics from AT&T to NTT:



There are a couple of spikes, but pretty comfortable 20ms on average. Then we get to hop 6, which is another NTT node in Dallas:



Here we start seeing maximums of almost 2 second latency, but still no packet loss. However, when we look at hop 7 which is the long haul from Dallas to Los Angeles (I previously thought this was San Francisco as I only had the device name to go off of) and we start to see a massive problem:



From the 14th at 2030 CST we start seeing ~30% packet loss which lasts roughly 12 hours. There's a short window where it stabilizes until 0900 on the 15th then starts dropping packets again for two straight days. This resolves at roughly 1300 on the 17th, then starts back up at 1800.

I understand the SE NOC can not feasibly monitor service quality from every players origination point to the game servers, but when the support staff just copy and paste the same 3 boxes over and over again blaming our ISP's for the issue and never escalating it, it's pretty annoying.

The only thing that gives me pause is that yesterday we confirmed someone from Optimum was not having the same issues and he posted his Tracert that showed his traffic going through the exact same nodes you posted. With a 50ish ms response.

Here's that section on my friend, not sure if Dallas, but in Texas with Optimum. Not hitting that same node we're all showing issues with.

7 * * * Request timed out.
8 58 ms 52 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 54 ms 56 ms 56 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 61 ms 79 ms 54 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 54 ms 54 ms 54 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 59 ms * 204.2.29.241
13 55 ms 57 ms 53 ms 204.2.29.6

This is also mine last night around 3 or 4 am when things were smooth enough to play. But nowhere near that same jump they're trying to say is expected going from Texas to Sacramento for that same node at that time.

8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 68 ms 55 ms 57 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 59 ms 61 ms 59 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 60 ms 59 ms 59 ms 204.2.29.6

I can confirm no loses either this morning but until we hit 5-9 PM with no issues I won't be convinced.