Regarding Reports on Recent Connection Problems with the NA Data Center

[Ravenguard]

I just got back from vacation and decided to check the routes again to the FFXIV Lobby Servers during primetime. Here's a ten minute span:



I'm still getting around 7%-14% packet loss.

Also:

Thank you for your reply Chortle,

It seems to be the issue has subsided. I would suggest doing some of the trouble shooting steps now that the "big issue" has been taken care of. If you are still having issue please let us know so I can escalate this again.

hope to be of assistance.

Unless I'm misunderstanding what you're addressing, this issue has definitely NOT subsided.
Perhaps a lot of people, myself included, have been on vacation during the past couple of weeks and it's been showing less use / packetloss.
However, allow me to reaffirm that this packetloss issue is still alive and ongoing. Nothing has changed.

[MidnightWonko]

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 1 ms 1 ms RT-AC3200-C890 [192.168.1.1]
2 56 ms 63 ms 87 ms 10.72.160.1
3 9 ms 8 ms 7 ms irvnsysj01.oc.oc.cox.net [68.4.14.74]
4 10 ms 8 ms 17 ms ip68-4-11-68.oc.oc.cox.net [68.4.11.68]
5 12 ms 41 ms 16 ms 68.1.1.167
6 101 ms 32 ms 12 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 34 ms 33 ms 34 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 25 ms 26 ms 26 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 37 ms * 37 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 36 ms 35 ms 36 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 * 21 ms 20 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 25 ms 31 ms 24 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 23 ms 23 ms * 204.2.229.242
14 38 ms 39 ms 39 ms 204.2.229.9

Dunno if more of this information will help, though it's good to see that Einmimiria acknowledged it.

[Ravenguard]

Wewlad. So after getting caughtup reading the posts in this thread (and many other threads) since I last checked in about this packetloss issue, this is what I came to understand:



I seriously hope someone talks to SOMEONE soon, because with 4.2 coming up (with a brand-new raid tier), this is going to making playing new content nearly impossible.

[MidnightWonko]

Wewlad. So after getting caughtup reading the posts in this thread (and many other threads) since I last checked in about this packetloss issue, this is what I came to understand:



I seriously hope someone talks to SOMEONE soon, because with 4.2 coming up (with a brand-new raid tier), this is going to making playing new content nearly impossible.

Well, considering this:

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 and 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!

I'm hoping the issue is being considered VERY SERIOUSLY! I dunno if further traceroutes are useful to them at this moment, but if they are, here're the steps:

Win+R
(type cmd in the line that appears)
(console appears, type: tracert 204.2.229.9)
(Asterisks = dropped packets)

I am considering suspending my subscription until this issue is solved; the game is damn near unplayable in this condition!

[Kangaax]

Hey, another cox user here, just came back to ff14 to experience delicious constant rubberbanding because of packet loss. Can confirm the same issues as the previous posters.

[Aevumn]

Im still getting pretty bad rubber banding in evening still, for me I'm actually disconnecting more

[Ariellendera]

Good Morning,

I would like to correct my previous statement. I looked into this and the issue is still being investigated by Japan. We would still like to collect information from players in Arizona experiencing this issue. Please let us know here that you are still having this issue, report the issue to the ISP, get a confirmation code or reference number from contact with ISP. DO NOT post personal information here, once we get enough reports to send out emails again we will. Again I apologize for my post above.

Hope to be of assistance!

[Inbachi]

I didn't see this thread until now but I've been having the same issues and I'm in Arizona with Cox as my ISP. It's extremely frustrating because it happens during the evening after I'm off work which basically renders the game unplayable. The past few weeks haven't been as bad as earlier in December but it's still unacceptable. I sent a ticket to support but I'm not sure what other details, if any, are needed.

[Aristotle]

Just wanted to update and say I am still having this issue as an Arizona resident with Cox as my ISP in the evenings. It has gotten so bad that Astragalos is unplayable.

[Chortle]

The Southwest states are the unfortunate ones it seems. We all are being routed through a hop that gets overloaded during our peak play times of 6pm - 11pm (when everyone is off work). Packet loss and disconnects ensue. It's nice to know that SE is looking into the issue, but for an online game we continue to pay for via subscriptions, this does not bode well.

I love Final Fantasy, and I love this game. I hope this gets resolved quickly.