Regarding Reports on Recent Connection Problems with the NA Data Center

Quote:

Originally Posted by Bongaboi

Connection problems have affected my live stream tonight on Twitch. I have been inundated with 90Ks and 3Ks tonight. You guys need to lift, Square. If you need to deliver a hotfix and put the servers on maintenance do it now and do it quick.

This has been happening for the last 4 weeks.

I cannot run duty runs in fear of disconnect, getting removed from runs. Cannot do dailies in fear of disconnect while attempting to complete. Cannot do any FC runs because of fear they will not have patience for my disconnects happening.
I'm trying crafting now but now I fear of crafting and disconnect while attempting to complete a craft. Even loading this page / site takes long to load.

I fear disconnects while playing FFXIV.

Quote:

Originally Posted by Gilaverde

This has been happening for the last 4 weeks.

I cannot run duty runs in fear of disconnect, getting removed from runs. Cannot do dailies in fear of disconnect while attempting to complete. Cannot do any FC runs because of fear they will not have patience for my disconnects happening.
I'm trying crafting now but now I fear of crafting and disconnect while attempting to complete a craft. Even loading this page / site takes long to load.

I fear disconnects while playing FFXIV.

The fear is real, I just moved to a play where Cox has monopoly, so I have no other options. I 90ked while loading into an instance, and now my character is stuck logged in the game, I 90k trying to load into him.

Quote:

Originally Posted by Kyp

The fear is real, I just moved to a play where Cox has monopoly, so I have no other options. I 90ked while loading into an instance, and now my character is stuck logged in the game, I 90k trying to load into him.

Its not Cox IMO. SE made some changes back in Nov 2017 and refuses now to change it back. Its never been this bad. After the 4.1 update, the disconnects started.

Edit: after 4.15 update did the problems start.

I've been experiencing connection issues, lag spikes that would delay game play for 1-10 seconds. 90ked once. Issue seems to only be present with ff14. Located in California. Also, Cox. The only internet monopoly in my area.

Cox ISP, this has been ongoing for WEEKS, if not MONTHS!

Quote:

Originally Posted by Gilaverde

Its not Cox IMO. SE made some changes back in Nov 2017 and refuses now to change it back. Its never been this bad. After the 4.1 update, the disconnects started.

Edit: after 4.15 update did the problems start.

I'm not surprised if you are right. I'm not with Cox ISP though, I'm with Sky and ever since the 4.06a patch in September 2017 I have had a terrible connection and no troubleshooting has helped. I've tried absolutely everything SE and my ISP has suggested...it's never changed. 4 months of this awful connection, getting ready to give up and play something else, this game isn't worth paying for in this state.

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.

More d/cs tonight. One accompanied by what looked like a server hiccup (but no corresponding latency spike) and one just for no particular reason at all (no latency, no server delays). Both of these were 90002s. Fortunately they happened before and after I main tanked an alliance roulette... that's a fun way to cause random problems.

Quote:

And when I've set up 2 FF14s running on my PC, one using the keyboard, the other using a controller, either my account or my friends account would be DCed, but not the other.
(Remember, same computer, just 2 different accounts. And which one gets DCed is random.)

That's interesting. I remember reading once that FFXIV is SUPER twitchy about any kind of CPU misfiring (in some weird effort to prevent movement hacks I guess.... the flying RMT BLM bots would suggest it doesn't work). I could see running two clients side by side like that causing some issues if one of them missed its timing a couple times even if it didn't necessarily affect the other one.

Been having the same issues the last week or so. Spikes of 600-1000 in instance but not in the world. Just got blm to 70 but can't keep Enochian up or get out of mechanics because of lag. I just drop party. I been running test with my ISP and my PC trace route etc. I keep coming back to FFxiv as the problem.

MOAR DATA

Code:

C:\Users\Jon>pathping 204.2.229.97 Tracing route to 204.2.229.97 over a maximum of 30 hops 0 Lapis [192.168.1.54] 1 RT-AC68U-5570 [192.168.1.1] 2 96.120.28.53 3 te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 4 68.85.183.142 5 be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 6 be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 7 be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 8 ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 9 ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111] 10 ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213] 11 ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 12 * * ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 13 ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58] 14 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 15 204.2.229.242 16 204.2.229.97 Computing statistics for 400 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Lapis [192.168.1.54] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% RT-AC68U-5570 [192.168.1.1] 0/ 100 = 0% | 2 9ms 0/ 100 = 0% 0/ 100 = 0% 96.120.28.53 0/ 100 = 0% | 3 10ms 0/ 100 = 0% 0/ 100 = 0% te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 0/ 100 = 0% | 4 10ms 0/ 100 = 0% 0/ 100 = 0% 68.85.183.142 0/ 100 = 0% | 5 12ms 0/ 100 = 0% 0/ 100 = 0% be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 0/ 100 = 0% | 6 13ms 0/ 100 = 0% 0/ 100 = 0% be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 0/ 100 = 0% | 7 12ms 0/ 100 = 0% 0/ 100 = 0% be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 0/ 100 = 0% | 8 14ms 0/ 100 = 0% 0/ 100 = 0% ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 0/ 100 = 0% | 9 11ms 0/ 100 = 0% 0/ 100 = 0% ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111] 0/ 100 = 0% | 10 14ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213] 0/ 100 = 0% | 11 114ms 6/ 100 = 6% 6/ 100 = 6% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 0/ 100 = 0% | 12 63ms 0/ 100 = 0% 0/ 100 = 0% ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 0/ 100 = 0% | 13 166ms 7/ 100 = 7% 7/ 100 = 7% ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58] 0/ 100 = 0% | 14 67ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 0/ 100 = 0% | 15 67ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.242 0/ 100 = 0% | 16 84ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.97 Trace complete.

So tonight I just opted not to deal with it. I'll go play something else rather than play an unplayable game. Notice how once again it's NTT that's the issue? Two nodes with very high ping times and dropping packets. SE, please, have a talk with your ISP. Get this figured out. Because it isn't going away.

I've been hit by this the last night and tonight on Zalera. During EST roughly 8pm to 12am I'll get spiked and occasionally 90006'd. It's been fine at other times.

Same issue here, along with two of our friends but not everyone in our static. Getting really obnoxious. We're on Coeurl. All three of us were getting 90002 errors at the same time yesterday, and today we're getting lag spikes randomly but at different times. All three of us have Comcast, but one isn't in the same state for what it's worth.

Happening to me all day now.

- When the disconnects started occurring: Noticed as of 5 PM PT, still happening.
- Platform (PC, PS4, Mac): PC
- Any error codes or messages you receive upon disconnect (if any): No disconnects, but horrendous lag. Stopping and zipping around.
- Type of connection (wired or wireless): Wireless
- Other programs running while the game is playing (if any): No
- Frequency at which disconnect occurs: Constantly
- Where you are booted to after disconnect (Desktop, Start Screen, Character Select): No disconnection, but noticeable in Quarrymill and in the Palace of the Dead in particular

Target Name: 204.2.229.9
IP: 204.2.229.9
Date/Time: 1/6/2018 11:46:50 PM - 1/6/2018 11:56:50 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 600 0 0.33 79.25 1.71 SYNOLOGYROUTER [192.168.1.1]
2 600 0 3.71 104.06 8.66 10.82.8.1 [10.82.8.1]
3 600 0 3.70 53.78 8.98 ip68-4-11-194.oc.oc.cox.net [68.4.11.194]
4 600 0 4.85 28.11 10.40 ip68-4-11-16.oc.oc.cox.net [68.4.11.16]
5 600 0 7.48 130.17 14.30 68.1.1.63 [68.1.1.63]
6 600 0 7.09 57.89 14.57 ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 600 0 16.19 45.41 23.12 ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 600 0 9.16 31.85 14.87 ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 600 6 31.92 55.99 37.15 ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 600 8 32.19 58.09 38.06 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 600 10 34.25 66.63 40.83 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 600 12 35.64 60.32 41.65 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 600 9 35.58 57.83 40.47 204.2.229.242 [204.2.229.242]
14 600 6 34.38 157.97 41.46 204.2.229.9 [204.2.229.9]

Here's another because shouting in to the wind is fun.

Code:

Computing statistics for 400 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Lapis [192.168.1.54] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% RT-AC68U-5570 [192.168.1.1] 0/ 100 = 0% | 2 10ms 0/ 100 = 0% 0/ 100 = 0% 96.120.28.53 0/ 100 = 0% | 3 10ms 0/ 100 = 0% 0/ 100 = 0% te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 0/ 100 = 0% | 4 10ms 0/ 100 = 0% 0/ 100 = 0% 68.85.183.142 0/ 100 = 0% | 5 12ms 0/ 100 = 0% 0/ 100 = 0% be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 0/ 100 = 0% | 6 12ms 0/ 100 = 0% 0/ 100 = 0% be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 0/ 100 = 0% | 7 12ms 0/ 100 = 0% 0/ 100 = 0% be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 0/ 100 = 0% | 8 14ms 0/ 100 = 0% 0/ 100 = 0% ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 0/ 100 = 0% | 9 12ms 0/ 100 = 0% 0/ 100 = 0% ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111] 0/ 100 = 0% | 10 16ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213] 0/ 100 = 0% | 11 131ms 5/ 100 = 5% 5/ 100 = 5% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 0/ 100 = 0% | 12 81ms 0/ 100 = 0% 0/ 100 = 0% ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 0/ 100 = 0% | 13 180ms 11/ 100 = 11% 11/ 100 = 11% ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58] 0/ 100 = 0% | 14 180ms 8/ 100 = 8% 8/ 100 = 8% xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 0/ 100 = 0% | 15 77ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.242 2/ 100 = 2% | 16 176ms 2/ 100 = 2% 0/ 100 = 0% 204.2.229.97 Trace complete.

I've just got off the phone with COX, and its confirmed an issue with ntt.net's infrastructure -- quite possibly, they have a specific route they use for COX customers only, which is the one affected and why it seems only we're getting impacted.

I'd recommend everyone who's with COX call this number and relay your packet loss, as well.

First confirm that it's on their end (CMD trace route or use Ping Plotter to 204.2.229.9 to check results), and not something else.

If that's the problem for you too, do the following:

- Call 1-800-234-3993 (COX Hotline, select tech support in the directory).
- When an agent picks up, state that you're reporting packet loss along a specific route and that you'd like to speak to a Tier II agent. (Tier I can't help you)
- You should get transferred immediately, but might have a long wait time.
- Relay your situation to the Tier II agent, and provide him your evidence. He should understand quickly. He should open a ticket number for you for the investigation, after several questions.

Other ISP customers should do the same thing but with their appropriate hotline.

Edit: Valid steps, but their network team got back -- Still NTT confirmed, but they won't contact directly. Square Enix should reach out to them directly, since they are the direct customer for NTT. :(

Quote:

Originally Posted by Ariellendera

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.

A ticket number for what? If I call Comcast and tell them "I'm having problems connecting to Final Fantasy XIV" they're going to tell me, quite correctly, that there's nothing wrong with their network. I've shown lots of data on this point. Comcast isn't at fault here. As much as I despise them and wish them ill, they actually aren't the problem here.

I also have this issue. Cox ISP, in Orange County CA. Usually from 6pm to midnight, I have really terrible packet losses and the occasional disconnect. During the weekends, it can start as early as 3pm. The game is practically unplayable when the packet losses occur. During dungeons and raids, the game goes from playable to a total stand still every 5-15 seconds for 1-10 seconds.

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

Quote:

Originally Posted by 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

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.

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.

Quote:

Originally Posted by Ariellendera

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.

Quote:

Originally Posted by 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.

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!

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.

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.

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.

Quote:

Originally Posted by Bluefve

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.

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

Quote:

Originally Posted by Bluefve

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!

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.

Quote:

Originally Posted by 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.

I would like to encourage you to create your own thread, so we can assist you directly.

Thank you.

[NA] Horrible Lag

Before the mods are like check with your ISP thats been done multiple times before this happened, we have no packet loss or lag on our end. When we were in dungeon parties the other members said they were lagging too. My boyfriend and I bought a month of subscription to play and we have barely gotten to play with it due to the lag. The lag makes it impossible to heal and do boss mechanics. Is there any fix soon? If not can we get another month of subscription? Cause at this rate we are both going to waste a month of not being able to play.

Hello cosmicrobot, Thank you for posting on the Final Fantasy XIV Technical Support Forums.

We are monitoring and collecting information for these type of issues and escalating them. I would like to get some details regarding your specific issue.

Please provide:

- When it started occurring
- Platform (PC, PS4, Mac)
- Any error codes or messages you receive (if any)
- Type of connection (wired or wireless)
- Other programs running while the game is playing (if any)
- Frequency

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

When it started occurring
We started playing on Dec 26 and tried playing since last weekend but every time we did dungeons or played it would lag too bad

Platform (PC, PS4, Mac)
PC

Any error codes or messages you receive (if any)
No error messages and it wouldn't show the symbol next to our names when we usually lagged

Type of connection (wired or wireless)
Ethernet for my boyfriend and wireless for me, we use the same network

Other programs running while the game is playing (if any)
no other programs running

Frequency
every time we log in to play usually in the evening

Significant packet loss from 4pm - 12am pst for the last 3 weeks

Quote:

Originally Posted by Ariellendera

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.

This issue has NOT subsided for me. It has been ongoing for over 3 weeks now, and current game content is unplayable. I also have Cox as my ISP, and on contacting them and being passed to tier 2 support, I told them I'm specifically having a problem with packet loss regarding a game a play. The technician actually said to me, 'Let me guess, is this Final Fantasy 14?' He told me also that this is something Square Enix will have to address with NTT. On calling Square Enix support I was very upset to be told that this issue is not being reported by other people, when obviously there is 8 pages of forum complaints from the last few weeks. Even though I pointed out that I was getting packet loss once I hit the ntt.net network, the technician told me i should refresh my dns, update the firmware on my router, and other irrelevant and unhelpful things that I have already tried.

Cox cannot do anything to contact NTT since they have no affiliation with them. Hopefully this has already happened, but since ntt is a direct provider for Square Enix (as is made obvious by several posts on this thread which resolved the server IP's to ntt.net), I'm once again asking Square Enix to get your engineers to contact ntt.net to get them to investigate and fix this issue.

This is a list of all of the ip's which I have seen packet loss from on doing tracerts over the last few days:
ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
204.2.229.242
ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]

Here are some of my tracert and ping test results. I'm seeing anywhere from 5-20% packet loss:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 18 ms 8 ms 8 ms 10.7.82.1
3 8 ms 7 ms 9 ms 68.4.15.32
4 12 ms 11 ms 15 ms ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 15 ms 16 ms 14 ms 68.1.1.63
6 15 ms 14 ms 21 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 37 ms 42 ms * ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 30 ms 31 ms * ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 * 46 ms 39 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 38 ms * 39 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 39 ms 37 ms * ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 42 ms 45 ms 45 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 25 ms * 26 ms 204.2.229.242
14 42 ms 42 ms 42 ms 204.2.229.9

Ping statistics for 204.2.229.9:
Packets: Sent = 179, Received = 167, Lost = 12 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 51ms, Average = 39ms

~8:30 pm pst
Packets: Sent = 210, Received = 186, Lost = 24 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 63ms, Average = 44ms

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:

https://img2.finalfantasyxiv.com/acc...3d25036a89.jpg

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

Also:

Quote:

Originally Posted by Ariellendera

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.

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.

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:

https://img2.finalfantasyxiv.com/acc...93237c0fea.jpg

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.

Quote:

Originally Posted by 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:

https://img2.finalfantasyxiv.com/acc...93237c0fea.jpg

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:

Quote:

Originally Posted by Einmimiria

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!

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.