Regarding Reports on Recent Connection Problems with the NA Data Center

[XenoCranel]

Did they solve your issue or are they still working on it?

This is my tracert

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 16 ms 12 ms 68.4.15.8
4 29 ms 29 ms 29 ms ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 31 ms 30 ms 34 ms 68.1.1.63
6 33 ms 31 ms 34 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 58 ms * 57 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 * 64 ms 70 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 58 ms * 55 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 * 56 ms * ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 44 ms 51 ms 43 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 60 ms 70 ms 61 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 60 ms 59 ms * 204.2.229.242
14 50 ms 42 ms 44 ms 204.2.229.9

UPDATE:

I just got off the phone with a Cox Tier II Agent.

Total time on the phone investigating this issue together, 40 min or so.

In my hop 6-12, the server ntt.net is a japanese owned data center that Cox has no control over.

If you look up via WhoIs for ntt.net, you will find more info.

These are located in the LA area, lsanca means that it is LA (Los Angeles) based.

This is not only a cox issue, this is an issue for players that are being routed via the LA based ntt.net server.

Cox cannot do anything about this, so the issue seems to point toward the FF data center

[drebbe]

Did they solve your issue or are they still working on it?

This is my tracert

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 16 ms 12 ms 68.4.15.8
4 29 ms 29 ms 29 ms ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 31 ms 30 ms 34 ms 68.1.1.63
6 33 ms 31 ms 34 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 58 ms * 57 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 * 64 ms 70 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 58 ms * 55 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 * 56 ms * ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 44 ms 51 ms 43 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 60 ms 70 ms 61 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 60 ms 59 ms * 204.2.229.242
14 50 ms 42 ms 44 ms 204.2.229.9

UPDATE:

I just got off the phone with a Cox Tier II Agent.

Total time on the phone investigating this issue together, 40 min or so.

In my hop 6-12, the server ntt.net is a japanese owned data center that Cox has no control over.

If you look up via WhoIs for ntt.net, you will find more info.

These are located in the LA area, lsanca means that it is LA (Los Angeles) based.

This is not only a cox issue, this is an issue for players that are being routed via the LA based ntt.net server.

Cox cannot do anything about this, so the issue seems to point toward the FF data center

Correct, SE's datacenter is on NTT's servers which is why everyone routes through NTT. There is no fix from our side until SE puts a lot of pressure on NTT or moves companies.