Regarding Reports on Recent Connection Problems with the NA Data Center

[Bluefve]

Cox got back to me. Confirmed on NTT.net's side, not a local network or Cox issue -- quite likely one of their several uplinks has has been designated for Cox users (perhaps, just for LA/OC) and is smaller than the real throughput traffic of Cox customers. Therefore, during peak times, it get's congested and drops packets and only users which have been assigned that particular route (based on ISP and perhaps geolocation) are affected and no one else.

Cox is unwilling to contact NTT.net directly, since they are the direct provider for SE. Cox urges users to pressure SE into getting their direct provider, NTT, to resolve the problem.

NTT.net is unwilling to investigate, unless a client directly requests it (AKA SE)-- per their Network Operations Team via noc@us.ntt.net.

Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well.

[Bluefve]

Hello Callinon Thank you for your reply,

We are going to be monitoring this issue. In the mean time, have you tried contacting your ISP? We suggest you report the issue to them and obtain a reference/ticket number from them. Thank you for your understanding while we try and get this issue resolved.

Thank you for playing Final Fantasy XIV! Hope to see you online.

I have a ticket number from Cox about this issue, if you'd like. I won't share it in public however, but you can PM me.

Regardless, the outcome of their investigation is that its confirmed on NTT.net's side, not a local network or Cox issue -- quite likely one of their several uplinks has has been designated for Cox users (perhaps, just for LA/OC) and is smaller than the real throughput traffic of Cox customers. Therefore, during peak times, it get's congested and drops packets and only users which have been assigned that particular route (based on ISP and perhaps geolocation) are affected and no one else.

Cox is unwilling to contact NTT.net directly, since they are the direct provider for SE. Cox urges users to pressure SE into getting their direct provider, NTT, to resolve the problem.

NTT.net is unwilling to investigate, unless a client directly requests it (AKA SE)-- per their Network Operations Team via noc@us.ntt.net.

Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well. If my ticket with Cox helps your engineers get in contact with them, I'll share the number.

[Einmimiria]

Cox got back to me. Confirmed on NTT.net's side, not a local network or Cox issue -- quite likely one of their several uplinks has has been designated for Cox users (perhaps, just for LA/OC) and is smaller than the real throughput traffic of Cox customers. Therefore, during peak times, it get's congested and drops packets and only users which have been assigned that particular route (based on ISP and perhaps geolocation) are affected and no one else.

Cox is unwilling to contact NTT.net directly, since they are the direct provider for SE. Cox urges users to pressure SE into getting their direct provider, NTT, to resolve the problem.

NTT.net is unwilling to investigate, unless a client directly requests it (AKA SE)-- per their Network Operations Team via noc@us.ntt.net.

Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well.

Thank you Bluefve for providing this information. We are currently in the process of gathering information and reporting it so we can find a solution to the issue. Unfortunately, it can take some time for this due to the many parties involved. We appreciate your understanding and patience as we work to investigate the issue. If anyone receives an email requesting connection information, please respond to it as soon as possible so we can use that information in our report.

We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

[Nega_Nomicon]

I called Cox and they also confirmed to me that it's NTT. I'm relieved to know that my ISP is NOT the issue but with 4.2 right around the corner the timing couldn't be any more disastrous. I hope that it's fixed soon because I can't justify paying for a game I can't play.

[LittleChickenNugget]

The game is basically unplayable for me at this point. Which sucks because it just renewed. Nothing else is having this issue. WoW. Youtube. Nothing other than FFXIV.

[LittleChickenNugget]

I don't have Cox but I have a company called Fairpoint - they've verified the issue isn't on their end. Which I could have told everyone that - every other game works just fine. SE please. We pay you ever month to play a game. The least you can do is make it a smooth experience for us.

[Callinon]

Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well. If my ticket with Cox helps your engineers get in contact with them, I'll share the number.

Any data they need is their's if it'll make this problem go away. Hell, I can make it up if they want.

[Mar_Vell]

I've been having lag issues for about a month now. I've done more or less everything everybody has tried. At this point I'm just desperate. Here's the trace route. Hopefully the information will help fix things.


1 2 ms 4 ms 1 ms 192.168.1.1
2 9 ms 11 ms 12 ms 10.82.56.1
3 12 ms 12 ms 12 ms ip68-4-13-44.oc.oc.cox.net [68.4.13.44]
4 11 ms 12 ms 10 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 12 ms 11 ms 9 ms 68.1.1.167
6 11 ms 9 ms 12 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 36 ms 38 ms 36 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 35 ms 27 ms 30 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 39 ms * 44 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 37 ms 35 ms 40 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 42 ms 36 ms 39 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 38 ms 38 ms 42 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 42 ms 39 ms 48 ms 204.2.229.242
14 39 ms 43 ms 41 ms 204.2.229.9

[Ariellendera]

I have a ticket number from Cox about this issue, if you'd like. I won't share it in public however, but you can PM me.

Regardless, the outcome of their investigation is that its confirmed on NTT.net's side, not a local network or Cox issue -- quite likely one of their several uplinks has has been designated for Cox users (perhaps, just for LA/OC) and is smaller than the real throughput traffic of Cox customers. Therefore, during peak times, it get's congested and drops packets and only users which have been assigned that particular route (based on ISP and perhaps geolocation) are affected and no one else.

Cox is unwilling to contact NTT.net directly, since they are the direct provider for SE. Cox urges users to pressure SE into getting their direct provider, NTT, to resolve the problem.

NTT.net is unwilling to investigate, unless a client directly requests it (AKA SE)-- per their Network Operations Team via noc@us.ntt.net.

Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well. If my ticket with Cox helps your engineers get in contact with them, I'll share the number.

Hello! Please keep a eye out for a email from us. No need to provide the ticket number here. Hope to be of assistance!

[PrincessPeaNuT]

Few of us are having this lag/dc issue usually during raid. I think since patch 4.15 or so...? Never had any connection issue until then, but often we experience lag while we are in raid instance. We usually raid after 8:30pm pst. Generally we are ok with other parts of the game except I started to see dungeon lags this past couple days.