Packet Loss issues with *.gin.ntt.net hops

I've been getting non-stop packet loss since the server move and its making the game unplayable.

I'm an east coast player and I'm really upset you didn't move the servers to a more centralized location of the US.


Hopefully this traceroute provides information to fix it on your end. Unfortunately I'll be forced to leave the game if this continues as its unplayable currently.

Code:

---

pathping 204.2.229.100

Tracing route to 204.2.229.100 over a maximum of 30 hops

  0  Blade [192.168.88.233]
  1  192.168.88.1
  2  *******************************************************
  3  *******************************************************
  4  *******************************************************
  5  *******************************************************
  6  hu-0-13-0-6-pe03.350ecermak.il.ibone.comcast.net [68.86.88.230]
  7  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  8  ae-4.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
  9  ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7]
 10    *    ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 11  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 12  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 13  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 14    *    204.2.229.234
 15  204.2.229.100

Computing statistics for 375 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          Blade [192.168.88.233]
                                0/ 100 =  0%  |
  1    0ms    0/ 100 =  0%    0/ 100 =  0%  192.168.88.1
                                0/ 100 =  0%  |
  2    8ms    0/ 100 =  0%    0/ 100 =  0%  *******************************************************
                                0/ 100 =  0%  |
  3  13ms    0/ 100 =  0%    0/ 100 =  0%  *******************************************************
                                0/ 100 =  0%  |
  4    9ms    0/ 100 =  0%    0/ 100 =  0%  *******************************************************
                                0/ 100 =  0%  |
  5  17ms    0/ 100 =  0%    0/ 100 =  0%  *******************************************************
                                0/ 100 =  0%  |
  6  16ms    0/ 100 =  0%    0/ 100 =  0%  hu-0-13-0-6-pe03.350ecermak.il.ibone.comcast.net [68.86.88.230]
                                0/ 100 =  0%  |
  7  17ms    0/ 100 =  0%    0/ 100 =  0%  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
                                0/ 100 =  0%  |
  8  21ms    0/ 100 =  0%    0/ 100 =  0%  ae-4.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
                                0/ 100 =  0%  |
  9  25ms    0/ 100 =  0%    0/ 100 =  0%  ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7]
                                7/ 100 =  7%  |
 10  99ms    12/ 100 = 12%    5/ 100 =  5%  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
                                0/ 100 =  0%  |
 11  97ms    11/ 100 = 11%    4/ 100 =  4%  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
                                0/ 100 =  0%  |
 12  100ms    10/ 100 = 10%    3/ 100 =  3%  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
                                0/ 100 =  0%  |
 13  102ms    8/ 100 =  8%    1/ 100 =  1%  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
                                0/ 100 =  0%  |
 14  101ms    8/ 100 =  8%    1/ 100 =  1%  204.2.229.234
                                0/ 100 =  0%  |
 15  101ms    7/ 100 =  7%    0/ 100 =  0%  204.2.229.100

---

I just realized there is a thread already going on with this, going to post it there instead.

I already posted this in the thread regarded connection issues after the data server move, but I've been having the exact same issue.

This is the traceroute. As you can see, the issue begins at jump 11, which is in Chicago. Also note the massive increase in ping when hitting that node as well, as big an increase as when the route jumps from Chicago to California, when the jump before that, also in Chicago, doesn't. I'm suspecting that this particular server is getting overloaded during peak hours.

yeah it sucks, I doubt its going to change. Its been like that for years AFAIK. SE really bit the bullet big time by not doing research on location before moving the servers.