Regarding Reports on Recent Connection Problems with the NA Data Center

[ZekeLorand]

I thought it was just me. Glad we pay $13 for this trash servers and no official solutions or responses, amirite?

[Vech]

Platform: Windows PC
Connection: Wired
Internet Service Provider: Comcast
Server: Gilgamesh
US - West Virginia

Issues: For some background, I've played FFXIV on and off since ARR release and have NEVER experienced ANY lag (aside from DDOS) until they moved the servers from Montreal, Canada to somewhere in California. Stormblood has been a trying expansion for me since the rubber banding and constant disconnects have made me go from being a hardcore raider and pushing content to formally quitting my raid group because I cannot comfortably do mechanics.

When I first started to have issues I honestly thought it could have been on my end. I upgraded my router, modem, and went from 5ghz wireless to wired. When the problems persisted (ONLY IN FFXIV) I went to the forums and found that A LOT, and I mean A LOT of people were having the same major issues I was having. I got into posting tracerts and find target nodes that were dropping the packets. Hell, I even called my internet service provider to see if they could reroute my connection to the FFXIV servers. All of that was for naught. I still lagged. A few months ago I had to take a break due to the stress of trying to complete the current raid tier with unbearable lag. I came back last month to play the new content but alas, the lag is still there.

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms <1 ms <1 ms amplifi.lan [192.168.163.1]
2 8 ms 8 ms 9 ms 96.120.62.181
3 9 ms 8 ms 7 ms te-0-1-0-3-sur02.morgantown.wv.pitt.comcast.net [68.85.74.81]
4 12 ms 8 ms 8 ms 69.139.169.154
5 14 ms 13 ms 14 ms be-48-ar01.mckeesport.pa.pitt.comcast.net [69.139.169.145]
6 22 ms 20 ms 33 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
7 20 ms 20 ms 18 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
8 20 ms 19 ms 24 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
9 88 ms 87 ms 88 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
10 21 ms 21 ms 20 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
11 85 ms 85 ms 85 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 90 ms 89 ms 88 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 88 ms 89 ms 102 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 87 ms 92 ms 88 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 87 ms 88 ms 89 ms 204.2.229.234
16 87 ms 87 ms 95 ms 204.2.229.9

EDIT

A few minutes later:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 2 ms 1 ms amplifi.lan [192.168.163.1]
2 9 ms 16 ms 9 ms 96.120.62.181
3 9 ms 8 ms 9 ms te-0-1-0-3-sur02.morgantown.wv.pitt.comcast.net [68.85.74.81]
4 10 ms 19 ms 8 ms 69.139.169.154
5 13 ms 16 ms 14 ms be-48-ar01.mckeesport.pa.pitt.comcast.net [69.139.169.145]
6 21 ms 23 ms 22 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
7 21 ms 20 ms 20 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
8 36 ms 31 ms 31 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
9 88 ms 87 ms 88 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
10 23 ms 30 ms 19 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
11 85 ms 84 ms 102 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 98 ms 89 ms 88 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 88 ms 89 ms 89 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 95 ms 89 ms 95 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 88 ms 89 ms * 204.2.229.234
16 88 ms 96 ms 88 ms 204.2.229.9

[SempaiSama]

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 142.254.218.221 - 0 | 149 | 149 | 9 | 18 | 158 | 15 |

| agg63.mednny0201h.northeast.rr.com - 0 | 149 | 149 | 21 | 54 | 363 | 29 |

| agg20.riganyaa03r.northeast.rr.com - 0 | 149 | 149 | 21 | 143 | 877 | 37 |

| agg50.hnrtnyaf02r.northeast.rr.com - 0 | 149 | 149 | 14 | 23 | 130 | 17 |

| be28.albynyyf01r.northeast.rr.com - 0 | 149 | 149 | 22 | 34 | 159 | 26 |

|bu-ether16.nycmny837aw-bcr00.tbone.rr.com - 0 | 149 | 149 | 31 | 44 | 160 | 36 |

| unk-426d0577.adelphiacom.net - 0 | 149 | 149 | 29 | 46 | 160 | 35 |

| nyk-b6-link.telia.net - 0 | 149 | 149 | 29 | 40 | 144 | 31 |

| nyk-b5-link.telia.net - 0 | 149 | 149 | 28 | 39 | 143 | 31 |

| ae-6.r07.nycmny01.us.bb.gin.ntt.net - 0 | 149 | 149 | 29 | 40 | 160 | 36 |

| ae-2.r24.nycmny01.us.bb.gin.ntt.net - 0 | 149 | 149 | 29 | 40 | 145 | 31 |

| ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 0 | 149 | 149 | 83 | 96 | 226 | 89 |

| ae-8.r23.sttlwa01.us.bb.gin.ntt.net - 8 | 119 | 110 | 0 | 89 | 228 | 85 |

| ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 149 | 149 | 96 | 107 | 214 | 102 |

| ae-45.r01.snjsca04.us.bb.gin.ntt.net - 0 | 149 | 149 | 99 | 108 | 209 | 102 |

| ae-4.r00.scrmca02.us.bb.gin.ntt.net - 0 | 149 | 149 | 100 | 110 | 218 | 101 |

|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 149 | 149 | 99 | 107 | 234 | 101 |

| 204.2.229.234 - 31 | 68 | 47 | 99 | 107 | 160 | 104 |

| 204.2.229.9 - 0 | 149 | 149 | 99 | 107 | 208 | 99 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


NTT and your lobby server are dropping packets.

Your Lobby server especially. I am getting 90k disconnects every 2-3minutes.

[Aliron]

I've been getting a lot of lag in all areas

World: Excalibur
Platform: PS4
Nature of Latency: the recieving info listed in game can go as high as 10000+, seems to be incoming data overload interferes with all actions
Connection: Wired
Other Programs running: none
Everything tried: Restart system, restart modem, turned off all devices not in use

Performed tracert

1 <1 ms <1 ms <1 ms ControlPanel.Start.ca [192.168.1.1]
2 9 ms 9 ms 9 ms lns1-toronto1-lo0.net.start.ca [64.140.112.14]
3 9 ms 9 ms 9 ms core1-toronto1-te-5-17-11.net.start.ca [104.193.
64.225]
4 9 ms 10 ms 10 ms bdr1-toronto1-ae0-3.net.start.ca [64.140.112.96]

5 10 ms 9 ms 10 ms bdr1-toronto2-et-0-0-1-4.net.start.ca [64.140.11
2.77]
6 9 ms 9 ms 9 ms te0-9-1-16.ccr32.yyz02.atlas.cogentco.com [38.12
2.69.129]
7 17 ms 16 ms 17 ms be2994.ccr22.cle04.atlas.cogentco.com [154.54.31
.233]
8 28 ms 29 ms 28 ms be2890.ccr42.jfk02.atlas.cogentco.com [154.54.82
.246]
9 34 ms 29 ms 29 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84
.214]
10 560 ms 96 ms 58 ms 38.122.8.210
11 29 ms 29 ms 29 ms cc-core-1-x-nyser32-gw-1.net.columbia.edu [128.5
9.255.5]
12 * 37 ms 29 ms cc-wlan-1-x-cc-core-1.net.columbia.edu [128.59.2
55.78]
13 * * * Request timed out

[Callinon]

Very little point in continuing to post connection details in this thread. SE has already decided that it isn't their problem and they aren't going to do anything about it. If your game is in an unplayable state, my sincere recommendation is to simply unsubscribe. Maybe that will finally clue them in that this very much IS their problem.

Probably not though.

[Manuu]

World: Behemoth
Platform: PS4
Connection: Wired
ISP: Vivo
Brazil, Ceará.

I tried everything like restart system, restart modem, turned off all devices not in use

I have been on this for 3 days now.

[gumas]

sigh why? i finally found a game that perfectly fit my taste, then this stupid 90002 error

the worse part is its only happen inside dungeon/instance, thats it. i can perfectly play this game for 4 hours++ the moment i enter instance/dungeon i got 90002 error within 10-15 minutes, forget about raid iam having hard time just to finish story instance.

and no, forget about posting tracert, i've done it 2 months ago and all i got is "thankyou for posting your network info, we will blablabla" thats it, no solution nothing.

[Kerwin]

sigh why? i finally found a game that perfectly fit my taste, then this stupid 90002 error

the worse part is its only happen inside dungeon/instance, thats it. i can perfectly play this game for 4 hours++ the moment i enter instance/dungeon i got 90002 error within 10-15 minutes, forget about raid iam having hard time just to finish story instance.

and no, forget about posting tracert, i've done it 2 months ago and all i got is "thankyou for posting your network info, we will blablabla" thats it, no solution nothing.

The moderators cannot do much of anything in this situation. They don't have the power to change their providers. That comes from the higher ups at Square Enix.

Since NTT has not done anything to fix these problems there are only two options that would fix these issues.

1. Move the server location to avoid the problematic NTT nodes.
2. Find a different internet provider other than NTT to path their customer's traffic through.

Neither of which the moderators are capable of doing on their own.

[Callinon]

The moderators cannot do much of anything in this situation. They don't have the power to change their providers. That comes from the higher ups at Square Enix.

Since NTT has not done anything to fix these problems there are only two options that would fix these issues.

1. Move the server location to avoid the problematic NTT nodes.
2. Find a different internet provider other than NTT to path their customer's traffic through.

Neither of which the moderators are capable of doing on their own.

It's not a matter of the forum moderators doing something. Of course that's not their job.

It's a matter of SE passing the word down to them to be shared with us that they don't think they need to fix this. That's what happened. That's why this is going on.

[Thaeryden]

I'll add my 1.5 cents:

Almost EVERY evening since I started playing FFXIV, which was about 2 months ago now, has been riddled with high latency & all the usual good stuff that comes with it (transactions not working, rubberbanding, dying because if inaction during combat... etc etc etc).

Again, almost every single evening, DURING PRIME TIME HOURS. From about 7:30pm (eastern) until "who-fricken-knows-how-late-because-after-several-hours-I've-given-up-and-went-to-bed-AM o'clock in the morning". Awesome! During the day I have just SOOOO MUCH FUN getting to play with the whopping 2 or 3 ppl that are online in my FC, playing in ghost-town like zones, and in the evening when just about everyone-&-their-mothers are online... nobody does anything because the lag is horrible and eventually everyone just gives up and/or gets disconnected.

Why?

SE, our $13-$15 a month isn't for charity you know. So.... what gives?
-What are you doing about this issue in the right here and now? I'm sure everyone would very much like/appreciate some sort of news/update as to why we have crappy connections during prime time hours! Again, being a new player, I know I would!

Before I click to submit this, here's my tracert. This isn't the worst it got up to, but it did spring up to the 200 range almost instantly when it started. It was sitting at a nice 98ms or so and then like someone flipped a switch sometime between 10 & 10:30pm ...this happened:

(10:35pm Eastern)
Tracing route to 204.2.229.86 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 12 ms 10 ms 96.120.41.45
3 15 ms 10 ms 10 ms ae26-rur02.porthuron.mi.michigan.comcast.net [68.87.187.109]
4 13 ms 14 ms 16 ms be-79-ar02.pontiac.mi.michigan.comcast.net [69.139.255.77]
5 21 ms 21 ms 21 ms be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
6 19 ms 19 ms 21 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
7 20 ms 28 ms 20 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
8 168 ms 184 ms 173 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
9 27 ms 22 ms 20 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
10 172 ms 164 ms 174 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 208 ms 198 ms 198 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
12 195 ms 196 ms 196 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
13 191 ms 189 ms 182 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 * 145 ms 145 ms 204.2.229.234
15 194 ms * 197 ms 204.2.229.86

Trace complete.
***************************************************************
(11:45pm)
1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 8 ms 10 ms 96.120.41.45
3 10 ms 15 ms 11 ms ae26-rur02.porthuron.mi.michigan.comcast.net [68.87.187.109]
4 16 ms 13 ms 14 ms be-79-ar02.pontiac.mi.michigan.comcast.net [69.139.255.77]
5 24 ms 24 ms 20 ms be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
6 20 ms 21 ms 19 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
7 23 ms 20 ms 20 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
8 162 ms 182 ms 174 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
9 20 ms 19 ms 29 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
10 165 ms 172 ms 143 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 201 ms 199 ms 196 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
12 192 ms 194 ms 193 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
13 170 ms 180 ms 171 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 163 ms 176 ms 177 ms 204.2.229.234
15 194 ms 197 ms 191 ms 204.2.229.86

If this continues, I honestly don't see myself playing beyond what my current subscription covers, because I can't play/get anything done during prime time hours! There's hardly ANYONE online during the day... and in the evening/night hours when the bulk of players would normally be on... they aren't, because of lag. The only time I've ever seen a game with this poor of a population was because the game was simply dying and just not popular... but I've NEVER seen a game (until now) this empty because of consistent latency!