Regarding Reports on Recent Connection Problems with the NA Data Center

[HiddinVirus]

Hello,

I would like to know who still experiencing this issue currently?

Also Cox ISP, experiencing same issue here.

  5    22 ms    21 ms    22 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  6    40 ms    21 ms    21 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  7    49 ms    51 ms    47 ms  ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  8    37 ms    48 ms     *     ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  9    47 ms    43 ms     *     ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
 10     *       47 ms     *     ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 11    47 ms    46 ms     *     ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
 12    47 ms    48 ms    49 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 13     *        *       49 ms  204.2.229.242
 14    49 ms     *       53 ms  204.2.229.9

  5    21 ms    26 ms    28 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  6    22 ms    22 ms    21 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  7     *       49 ms     *     ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  8    38 ms     *        *     ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  9     *       48 ms    46 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
 10     *        *        *     Request timed out.
 11    47 ms     *       46 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
 12    49 ms     *       47 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 13    49 ms    48 ms    53 ms  204.2.229.242
 14    46 ms    62 ms    47 ms  204.2.229.9

I'm also seeing 20-25% packet loss looking at the path on Ping Tracer. Using mudfish to connect to different nodes doesn't fully alleviate my issues either.

[Khaleasi]

I'm getting the exact same thing. This makes this game unplayable for me. I get 90k several times a night. I'm in Phx, Az and have Cox. My boyfriend works in IT and has tested everything on our end and it's fine. He said it's something going on with ntt.net.

5 29 ms 30 ms 29 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
6 23 ms 24 ms 24 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 49 ms 46 ms 51 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 44 ms 35 ms * ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 * 46 ms 47 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 54 ms * 60 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
11 51 ms 45 ms 44 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
12 47 ms 47 ms 51 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 49 ms * * 204.2.229.242
14 51 ms 51 ms * 204.2.229.9
15 50 ms * 51 ms 204.2.229.9

Trace complete.

[Dualgunner]

Here to report even with WTFast I've been experiencing some heavy issues with my connection tonight.

[Derik]

8:51 PM AZ time, 90006 disconnect. Dropping packets. Its just as bad as ever.
My first post I mistype the IP but here is my update

Ping statistics for 204.2.229.9:
Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 51ms, Average = 46ms

tracert 204.2.229.9

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 <1 ms <1 ms <1 ms 192.168.0.1
3 8 ms 9 ms 9 ms 10.49.208.1
4 10 ms 10 ms 11 ms 100.127.74.22
5 23 ms 9 ms 9 ms 70.169.74.152
6 22 ms 22 ms 22 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
7 21 ms 23 ms 20 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
8 45 ms 44 ms 44 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
9 36 ms 36 ms 37 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
10 * * * Request timed out.
11 42 ms 42 ms 44 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 54 ms 51 ms 48 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
13 48 ms 48 ms * xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
14 48 ms 50 ms * 204.2.229.242
15 * 46 ms 47 ms 204.2.229.9

Trace complete.

With google IP
ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=21ms TTL=57
Reply from 8.8.8.8: bytes=32 time=47ms TTL=57
Reply from 8.8.8.8: bytes=32 time=21ms TTL=57
Reply from 8.8.8.8: bytes=32 time=47ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 47ms, Average = 34ms

I reported this issue to cox again and provided all the info you guys have been posting. Told them that there are a lot of people in Arizona experiencing the same issue. They are going to open an investigation based on reports that were actually given to them. So if you haven't contacted cox to report the issue, please do.

[KonaKai]

COX in South Cali/Orange County

Tracing route to dyn-209-2-229-9.dyn.columbia.edu [209.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 11 ms 11 ms 11 ms ip68-4-13-52.oc.oc.cox.net [68.4.13.52]
4 9 ms 9 ms 9 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 9 ms 11 ms 10 ms 68.1.1.167
6 10 ms 16 ms 12 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 16 ms 19 ms 18 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 25 ms 22 ms 20 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 26 ms 23 ms 26 ms ae-2.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.238]
10 11 ms 13 ms 9 ms be3025.ccr41.lax04.atlas.cogentco.com [154.54.9.29]
11 11 ms 10 ms 11 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
12 22 ms 22 ms 22 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85]
13 30 ms 30 ms 30 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
14 47 ms 47 ms 47 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
15 61 ms 63 ms 61 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129]
16 73 ms 71 ms 72 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
17 78 ms 78 ms 84 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
18 78 ms 78 ms 78 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
19 122 ms 78 ms 78 ms 38.122.8.210
20 81 ms 77 ms 77 ms cc-core-1-x-nyser32-gw-1.net.columbia.edu [128.59.255.5]
21 78 ms 76 ms 76 ms cc-wlan-1-x-cc-core-1.net.columbia.edu [128.59.255.78]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

UPDATE: Think I fixed it? Went to my ISP FAQ and did a simple ip refresh. pinging and tracert working after several tests.

tracert 209.2.229.9

Tracing route to dyn-209-2-229-9.dyn.columbia.edu [209.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 10 ms 8 ms 9 ms ip68-4-13-52.oc.oc.cox.net [68.4.13.52]
4 8 ms 9 ms 7 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 10 ms 11 ms 10 ms 68.1.1.167
6 19 ms 16 ms 9 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 22 ms 21 ms 23 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 22 ms 21 ms 23 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 27 ms 27 ms 34 ms ae-2.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.238] 10 11 ms 9 ms 9 ms be3025.ccr41.lax04.atlas.cogentco.com [154.54.9.29]
11 11 ms 11 ms 11 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
12 22 ms 22 ms 25 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85]
13 32 ms 33 ms 47 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
14 47 ms 47 ms 46 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
15 66 ms 60 ms 61 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129] 16 71 ms 74 ms 72 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
17 77 ms 78 ms 79 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
18 78 ms 79 ms 80 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
19 77 ms 78 ms 77 ms 38.122.8.210
20 78 ms 79 ms 77 ms cc-core-1-x-nyser32-gw-1.net.columbia.edu [128.59.255.5]
21 78 ms 77 ms 78 ms cc-wlan-1-x-cc-core-1.net.columbia.edu [128.59.255.78]
22 168 ms 101 ms 101 ms dyn-209-2-229-9.dyn.columbia.edu [209.2.229.9]

Trace complete.

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Reply from 209.2.229.9: bytes=32 time=189ms TTL=18
Reply from 209.2.229.9: bytes=32 time=109ms TTL=18
Reply from 209.2.229.9: bytes=32 time=129ms TTL=18
Reply from 209.2.229.9: bytes=32 time=153ms TTL=18

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 189ms, Average = 145ms

[cieli]

My boyfriend and I have been having the same issue. I've contacted support and so far none of their suggestions has worked. We are in Arizona.

We did expert roulette today and our games froze every 2 seconds, lasting 10 seconds to a minute of stagnant screen. Unplayable.

If Square Enix doesn't fix this soon, they will be losing a lot of their player base. I won't continue to pay for a game that I can't even play.

[SGAllaria]

Me and a buddy both have been experiencing this for a while. We assumed it was still DDOS attacks. We've been having lag that lasts 1 to 2 second frequently, 10 second DCs occasionally, and at least 1 disconnect a night. We can't do any serious content with this amount of lag and DCs.

We are also in the Phoenix Metro area and use the ISP COX. I will try to call them tomorrow. I hope SE try's to leverage their voice in this matter if they can.

[Amirya]

My niece and I are both using Cox in the Phoenix Metro area, and we are also having serious issues. It was especially on Monday, Dec 11, 2017, just before maintenance. It remained unplayable until Thursday, Dec 14, 2017. No issues at all until tonight (Monday, Dec 18, 2017).

Either my niece, or I, will contact Cox tomorrow as well.

[Einmimiria]

Are you 100% sure there is no affiliation (rhetorical question)?

From my understanding this and this would seem to suggest otherwise.

Either way, I'm hoping it all gets ironed out in the long run so that my raid team can continue to play together. Thanks for working through all this with us, and escalating the issue, we appreciate all the help we can get.

We apologize for any confusion, please allow us to clarify. The nodes themselves are operated by NTT. As such, we do not have direct control over them nor can we control how you are routed through them. This doesn't necessarily mean you aren't using the NTT network to connect to the game. What was meant is that NTT is not a part of Square Enix's service and our actual influence over the nodes is limited at best.

[Aerile]

I'm having the same experience as everyone else, I'm in the Phoenix Metropolitan area.

I'm freezing every two seconds and WTFast doesn't seem to help. This tends to happen from 5pm till around 11pm mountain time and I noticed this started happening on Dec. 8th.