Regarding Reports on Recent Connection Problems with the NA Data Center

[Bluefve]

I have Cox im AZ and have not been noticing any issues with latency and the game. No lag spikes. No 90001 errors.

A 30 minute span during prime time. As you see I have no packet loss.


I'm unclear why some people are having problems and others not.

A few observations.
1. If it were NTT servers that were at fault then the latency problems would not be limited to just one ISP. All ISPs would be effected.

Wrong. MMOs don't work like that. Internet Data Centers often have numerous routes and uplinks, depending on geolocation and IP (for the intent of optimizing connections and providing more bandwidth. This could be a situation where one particular uplink is messed up, and why not everyone sees it.

2. I don't see how an Cox support operator would know details for why just one game isn't working.

True, but an ISP Network Engineer would have better insight and understanding for enterprise-level network architecture and their own infrastructure. The engineer I spoke to talked about his own experience working with Blizzard on a similar issue, back in 2013, for WoW.

3. Back when the game passed through Level3 servers, a few people had these same problems. People complained that Level3 servers were garbage and they we're at fault. Like people are blaming NTT now.

Level3 does have bad routing. Its worse in certain geographic areas though, like France.

4. A lot of people like me aren't experiencing problems. But you never here from us because why visit these threads unless we start having trouble.

Right, no one said EVERYONE is experiencing the problem. But the internet is a complicated beast, and a large number of people ARE experiencing a problem.

Two additional observations from your own data that I've noticed, is that...
1) Mostly (if not all) everyone who's having this problem is from California, CA. (You yourself are in AZ, which may not be affected)
2) Mostly (if not all) everyone who's reporting the problem are pinging 204.2.229.9 (You are pining 204.2.229.103 -- could mean everything, could mean nothing)

I don't know how relevant these details are, but they are nonetheless details.

My Pingplotter results taken just now.

Target Name: 204.2.229.9
IP: 204.2.229.9
Date/Time: 1/10/2018 9:19:17 PM - 1/10/2018 9:29:17 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 472 0 0.55 18.01 1.56 SYNOLOGYROUTER [192.168.1.1]
2 472 0 4.72 23.56 9.00
3 472 0 4.70 24.54 9.65 ip68-4-11-194.oc.oc.cox.net [68.4.11.194]
4 472 0 5.25 30.27 11.06 ip68-4-11-16.oc.oc.cox.net [68.4.11.16]
5 472 0 7.47 68.47 14.58 68.1.1.63 [68.1.1.63]
6 472 0 8.26 53.58 15.94 ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 472 1 17.92 40.26 21.84 ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 472 1 8.12 34.10 14.00 ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 472 3 34.06 59.62 38.16 ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 472 3 32.97 55.35 37.39 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 472 8 35.81 61.52 41.08 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 472 8 37.46 68.59 41.03 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 472 23 36.84 57.31 41.21 204.2.229.242 [204.2.229.242]
14 472 5 35.93 98.00 41.41 204.2.229.9 [204.2.229.9]

Would be interesting to see more people's PingPlotter results, too, versus plain traceroutes.