Regarding Reports on Recent Connection Problems with the NA Data Center

Having same issues on LichEU just random DCs with 90002 while running instances, and this has only started occuring within the last week or so

Just for fun

Code:

Tracing route to 204.2.229.97 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms RT-AC68U-5570 [192.168.1.1] 2 9 ms 9 ms 8 ms 96.120.28.53 3 10 ms 9 ms 8 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 4 8 ms 9 ms 8 ms 68.85.183.142 5 18 ms 10 ms 26 ms be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 6 12 ms 18 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 7 11 ms 9 ms 16 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 8 11 ms 20 ms 20 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 9 185 ms 186 ms 189 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111] 10 20 ms 11 ms 18 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213] 11 156 ms * 197 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 12 155 ms 170 ms 171 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 13 189 ms 189 ms 186 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 14 187 ms 190 ms 189 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 15 166 ms 158 ms 147 ms 204.2.229.234 16 187 ms 184 ms 186 ms 204.2.229.97 Trace complete.

Wanted to get some last leveling roulettes done this evening before the patch knocks the game down for 24 hours (why on Earth does it take that long to apply a patch... whatever) but no, unplayable.. just like every night.

Greetings!

Thank you for the information you have been posting about the connection issues you are facing. We have been working on our side to escalate the data you are providing to help investigate the troubles and work towards a resolution. We have been informed that the team looking into these connection difficulties is currently in touch with the upstream ISP about the issue.

Thank you for your patience as we work on this, and we will continue to provide updates as we get them. In the meantime, we do appreciate if you can continue to submit the requested information, so we can continue to escalate the data to work towards resolving this.

LGM Enkrateia

Just wanted to update from my side seems about 2 days ago my lag/rubberbanding finally seemed to go away unfortunately because of the delay in waiting for fix i did not have enough time to properly play feast and lost out on getting the limited time gear. Glad i can play again but really disappointed on how long it took which causde me to miss out on stuff guess i will have to deal with it :/

Still lagging/rubber-banding occasionally. Got the boot with error 90006 once too. This has been the norm for me for a while, seems like it's not changed. Just giving the benefit of the doubt now since it's patch day and some friends of mine were lagging also. But I get the feeling my situation will not change after things settle down.

Got dced once during Omega tonight with 90002 ran pingplotter for around half hour and had some packet loss at the destination server around 1minute intervals but did not drop connection latency seems fine overall, will monitor the situation

Code:

Tracing route to 204.2.229.97 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms RT-AC68U-5570 [192.168.1.1] 2 10 ms 10 ms 9 ms 96.120.28.53 3 14 ms 10 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 4 9 ms 9 ms 9 ms 68.85.183.142 5 11 ms 12 ms 11 ms be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 6 12 ms 12 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 7 11 ms 10 ms 11 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 8 139 ms 144 ms 133 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 9 184 ms 188 ms 183 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111] 10 117 ms 163 ms 128 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213] 11 186 ms 182 ms 159 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 12 172 ms 180 ms 180 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 13 186 ms 187 ms 184 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 14 178 ms 183 ms 186 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 15 174 ms * * 204.2.229.234 16 196 ms 186 ms 181 ms 204.2.229.97 Trace complete.

Moar... Moar never changes.

Just came back to the game, Would very much like to play.

Just resubscribed. The experience so far hasn't been great.

ISP: Mediacom
Connection Issue: Lag and disconnections
Frequency: Lag always, disconnections frequent
Error Codes seen: 90006

Code:

Tracing route to 204.2.229.97 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.1 2 14 ms 21 ms 18 ms 173-30-136-1.client.mchsi.com [173.30.136.1] 3 26 ms 17 ms 24 ms 172.30.11.133 4 28 ms 29 ms 30 ms 68-66-73-66.client.mchsi.com [68.66.73.66] 5 31 ms 24 ms 30 ms po10.mplmn001er1.mchsi.com [68.66.72.70] 6 24 ms 28 ms 29 ms et-1-3-0.MPR1.MSP2.us.zip.zayo.com [208.185.141.241] 7 36 ms 31 ms 38 ms ae4.cr1.ord2.us.zip.zayo.com [64.125.30.62] 8 37 ms 145 ms 38 ms ae15.er1.ord7.us.zip.zayo.com [64.125.31.85] 9 36 ms 33 ms 38 ms ae11.er2.ord7.us.zip.zayo.com [64.125.21.218] 10 40 ms 34 ms 39 ms zayo-ntt.ord7.zip.zayo.com [64.125.12.86] 11 92 ms 101 ms * ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158] 12 32 ms 35 ms 39 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205] 13 86 ms 89 ms * ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 14 89 ms 89 ms 93 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27] 15 90 ms 99 ms 88 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57] 16 100 ms 94 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 17 92 ms * * 204.2.229.234 18 91 ms 94 ms 92 ms 204.2.229.97 Trace complete.

Had a rough night last night during O5S with rubber banding and disconnecting, I have Cox and live in Southern California. I rubber banded pretty much from 8 PST to midnight, 3-4 DC's during that time as well

https://i.imgur.com/ZM2cSPo.jpg

I CANNOT RAID. I CANNOT PLAY. Holy cow, this is so bad. Just in time for patch 4.2!

8:30pm CST, Chicago IL USA, Comcast, the usual.

Thanks....

https://imgur.com/ih5bO4F
https://i.imgur.com/ih5bO4F.png

-Fidelity Communications ISP Lawton, Oklahoma

-Disconnects in overworld and housing areas, latency and lag in instances and dungeons before disconnecting.

-Error Code 90002

Brand new set of problems for me after have played this game for close to 1300 hours. Never had a single DC before.

Here the Tracert 01 February 5:43pm EST Time
Tracing route to 204.2.229.10 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 11 ms 14 ms 10.170.169.54
3 11 ms 13 ms 12 ms 10.170.192.53
4 13 ms 11 ms 12 ms ppp-206-80-245-49.nas01.totftds.ext.distributel.net [206.80.245.49]
5 11 ms 12 ms 9 ms xe-2-0-0.cr0-mtl3.ip4.gtt.net [69.31.142.117]
6 22 ms 17 ms 21 ms xe-0-0-6.cr8-nyc3.ip4.gtt.net [89.149.129.21]
7 20 ms 19 ms 23 ms as2914.nyc34.ip4.gtt.net [199.229.229.190]
8 93 ms 92 ms 90 ms ae-6.r08.nycmny01.us.bb.gin.ntt.net [129.250.6.54]
9 22 ms * 18 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
10 90 ms 83 ms 81 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 80 ms 83 ms 82 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
12 93 ms 92 ms 92 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 95 ms 96 ms 96 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
14 96 ms 96 ms 94 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
15 96 ms 96 ms 94 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 95 ms * 96 ms 204.2.229.234
17 94 ms 97 ms 95 ms 204.2.229.10

Trace complete.

I hope Division 11 get double budget in 5.0 so we can get rid of NTT & SE get new provider who can have access central datacenter in NA if not then enjoy lost subs! Because NTT will do nothing until a rate of 10% + package lost on nodes/servers because #NTTpolicies (thanks Reddit)

https://i.imgur.com/QsZc53n.jpg

Still rubber banding. Still lagging. I'm very very livid right now.

Still in the same situation, but I guess I'll keep updating?

This is really sad, it's been 5 months that I've had these problems. Rubber-banding/Error 90006 etc.

Code:

|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | SkyRouter.Home - 0 | 127 | 127 | 0 | 0 | 5 | 0 | | No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 | | be365.pr2.hobir.isp.sky.com - 0 | 126 | 126 | 16 | 33 | 2016 | 18 | | 62.73.179.165 - 0 | 126 | 126 | 16 | 31 | 2015 | 16 | | ae-4.r24.londen12.uk.bb.gin.ntt.net - 0 | 126 | 126 | 15 | 32 | 2020 | 16 | | ae-5.r24.nycmny01.us.bb.gin.ntt.net - 33 | 55 | 37 | 92 | 92 | 98 | 94 | | ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 33 | 55 | 37 | 158 | 192 | 1353 | 159 | | ae-0.r21.sttlwa01.us.bb.gin.ntt.net - 26 | 63 | 47 | 158 | 163 | 355 | 159 | | ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 126 | 126 | 166 | 182 | 2165 | 166 | | ae-41.r02.snjsca04.us.bb.gin.ntt.net - 0 | 126 | 126 | 170 | 186 | 2179 | 170 | | ae-3.r00.scrmca02.us.bb.gin.ntt.net - 0 | 126 | 126 | 167 | 183 | 2173 | 168 | |xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 126 | 126 | 169 | 185 | 2170 | 170 | | 204.2.229.234 - 0 | 126 | 126 | 166 | 182 | 2168 | 167 | | 204.2.229.10 - 0 | 126 | 126 | 175 | 191 | 2174 | 176 | |________________________________________________|______|______|______|______|______|______|

I guess I'll post a Trace Route from Command Prompt? It makes no difference, it has less information too.

https://i.imgur.com/BuI5Ick.png

I've been having issues with this for months as well, wanna say since patch 4.1.
My ISP is Comcast and I live on the east coast. The connection issues and lag starts happening around 8pm est and lasts until around 1-2am for me.

Code:

Tracing route to 204.2.229.97 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.0.0.1 2 13 ms 16 ms 10 ms 96.120.66.161 3 10 ms 13 ms 13 ms 68.85.187.237 4 13 ms 13 ms 15 ms be-22-sur02.lowell.ma.boston.comcast.net [69.139.221.246] 5 17 ms 15 ms 14 ms be-21-ar01.needham.ma.boston.comcast.net [68.85.106.45] 6 25 ms 22 ms 24 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217] 7 20 ms 26 ms 18 ms be-10381-pe02.111eighthave.ny.ibone.comcast.net [68.86.86.250] 8 47 ms 54 ms 53 ms 50.242.151.70 9 190 ms 178 ms 168 ms ae-9.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.93] 10 114 ms 102 ms 102 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180] 11 98 ms 193 ms 162 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13] 12 163 ms 106 ms 101 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54] 13 180 ms 194 ms 186 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124] 14 211 ms * 232 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 15 175 ms 187 ms 176 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 16 * 223 ms 209 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 17 * 208 ms * 204.2.229.234 18 213 ms 224 ms 221 ms 204.2.229.97 Trace complete.

Any update on this?
2/16/20118 10:00pm EST

Code:

Tracing route to 204.2.229.9 over a maximum of 30 hops 1 1 ms 1 ms 1 ms [REDACTED] 2 31 ms 10 ms 8 ms [REDACTED] 3 12 ms 27 ms 12 ms [REDACTED] 4 11 ms 17 ms 10 ms [REDACTED] 5 13 ms 13 ms 41 ms ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 6 12 ms 12 ms 22 ms be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 7 15 ms 12 ms 11 ms be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 8 15 ms 17 ms 16 ms 50.242.151.58 9 19 ms 18 ms 15 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 10 16 ms 14 ms 10 ms ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 11 29 ms 31 ms 29 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 12 190 ms 184 ms 191 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 13 171 ms 189 ms 179 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 14 176 ms 191 ms 182 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 15 176 ms 185 ms 188 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 16 198 ms 200 ms * 204.2.229.234 17 191 ms 192 ms 188 ms 204.2.229.9 Trace complete.

Still there! 7:51 pst

Traceroute has started…

traceroute to 204.2.229.9 (204.2.229.9), 64 hops max, 72 byte packets
1 10.3.34.1 (10.3.34.1) 113.636 ms 14.784 ms 133.793 ms
2 192.168.64.2 (192.168.64.2) 19.992 ms 13.299 ms 140.556 ms
3 chi-b21-link.telia.net (62.115.146.250) 21.618 ms 16.407 ms 131.603 ms
4 ae-25.r08.chcgil09.us.bb.gin.ntt.net (129.250.8.61) 20.040 ms 109.532 ms 146.020 ms
5 ae-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.205) 15.027 ms 144.327 ms 40.258 ms
6 ae-5.r22.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 74.571 ms 69.442 ms 66.818 ms
7 ae-19.r01.snjsca04.us.bb.gin.ntt.net (129.250.3.27) 74.061 ms 72.232 ms 72.686 ms
8 ae-4.r00.scrmca02.us.bb.gin.ntt.net (129.250.7.57) 71.395 ms 76.274 ms 76.384 ms
9 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) 71.916 ms 75.117 ms 78.056 ms
10 204.2.229.234 (204.2.229.234) 76.495 ms 76.181 ms *
11 204.2.229.9 (204.2.229.9) 70.834 ms 72.718 ms 70.986 ms

Hi, this has been happening for about 3 weeks and I've done everything I can feasibly do. My ISP is Spectrum, I lag, disconnect and it happens pretty much all day long, no matter what I'm doing, I could be crafting, I could be flying, I'll just get a 90002, or an 90001, or even a lobby issue which is like 2002? This has gotten beyond annoying as I lose materials when I craft, drop my queue, or cause the party i'm in a dungeon with to lose their limit break. Please, fix this, it's gone on long enough.

Quote:

1 5 ms 3 ms 4 ms 192.168.1.1
2 18 ms 15 ms 17 ms 142.254.144.113
3 34 ms 42 ms 42 ms 24.29.2.209
4 18 ms 17 ms 19 ms be20.owchoh0201r.midwest.rr.com [65.29.38.20]
5 21 ms 24 ms 18 ms be14.dytnoh5501r.midwest.rr.com [65.29.33.212]
6 33 ms 30 ms 30 ms be28.clevohek01r.midwest.rr.com [65.29.1.46]
7 40 ms 38 ms 37 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 36 ms 37 ms 38 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 34 ms 33 ms 49 ms 0.ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
10 34 ms 35 ms 33 ms ix-ae-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
11 38 ms 39 ms 33 ms if-ae-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
12 36 ms 34 ms 33 ms 66.198.154.71
13 33 ms 34 ms 34 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 105 ms 109 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 107 ms 106 ms 108 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
16 107 ms 108 ms 107 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
17 108 ms 108 ms 108 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 110 ms * * 204.2.229.234
19 108 ms 107 ms 107 ms 204.2.229.9

Hello Everyone,

Thank you for your continued patience with the ongoing connection and latency issues regarding the NA data centers. We are still investigating the reported issues and are actively working with our teams to get a resolution.

We will continue to provide updates as we get them. In the meantime, we do appreciate if you can continue to submit the requested information, so we can continue to escalate the data to work towards resolving this.

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

Quote:

Originally Posted by cherrydew

I've been having issues with this for months as well, wanna say since patch 4.1.
My ISP is Comcast and I live on the east coast. The connection issues and lag starts happening around 8pm est and lasts until around 1-2am for me.

Code:

Tracing route to 204.2.229.97 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.0.0.1 2 13 ms 16 ms 10 ms 96.120.66.161 3 10 ms 13 ms 13 ms 68.85.187.237 4 13 ms 13 ms 15 ms be-22-sur02.lowell.ma.boston.comcast.net [69.139.221.246] 5 17 ms 15 ms 14 ms be-21-ar01.needham.ma.boston.comcast.net [68.85.106.45] 6 25 ms 22 ms 24 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217] 7 20 ms 26 ms 18 ms be-10381-pe02.111eighthave.ny.ibone.comcast.net [68.86.86.250] 8 47 ms 54 ms 53 ms 50.242.151.70 9 190 ms 178 ms 168 ms ae-9.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.93] 10 114 ms 102 ms 102 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180] 11 98 ms 193 ms 162 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13] 12 163 ms 106 ms 101 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54] 13 180 ms 194 ms 186 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124] 14 211 ms * 232 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 15 175 ms 187 ms 176 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 16 * 223 ms 209 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 17 * 208 ms * 204.2.229.234 18 213 ms 224 ms 221 ms 204.2.229.97 Trace complete.

I get something very similar, at almost the same times with the same isp. According to comcast the issues are on the ntt network, or later so there is nothing they can do.

Welp I thought my rubberbanding due to packet loss was fixed because i went couple weeks without anything but last 2 days packet loss has come back in full force and barely able to play game again

Was fine for about a week or so but the packet loss came back bad tonight. Completely unplayable for combat sadly.

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 router.asus.com [192.168.1.1]
2 6 ms 10 ms 7 ms 10.74.0.1
3 7 ms 7 ms 9 ms ip68-4-13-52.oc.oc.cox.net [68.4.13.52]
4 8 ms 7 ms 7 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 10 ms 9 ms 9 ms 68.1.1.167
6 28 ms 25 ms 27 ms ae-6.r01.lsanca20.us.bb.gin.ntt.net [168.143.229.57]
7 27 ms * 26 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
8 25 ms 27 ms 26 ms ae-2.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.238]
9 10 ms 9 ms 15 ms be3025.ccr41.lax04.atlas.cogentco.com [154.54.9.29]
10 13 ms 9 ms 9 ms be3360.ccr42.lax01.atlas.cogentco.com [154.54.25.149]
11 24 ms 21 ms 21 ms be2932.ccr32.phx01.atlas.cogentco.com [154.54.45.161]
12 30 ms 29 ms 29 ms be2930.ccr21.elp01.atlas.cogentco.com [154.54.42.78]
13 48 ms 52 ms 48 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
14 62 ms 59 ms 60 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129]
15 73 ms 76 ms 70 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
16 80 ms 77 ms 80 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
17 78 ms 78 ms 80 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
18 117 ms 109 ms 97 ms 38.122.8.210
19 166 ms 78 ms 80 ms nyser111-gw-1-x-nyser32-gw-1.net.columbia.edu [128.59.255.10]
20 79 ms 77 ms 79 ms phi-core-1-x-nyser111-gw-1.net.columbia.edu [128.59.255.13]
21 77 ms 77 ms 76 ms cc-wlan-1-x-phi-core-1.net.columbia.edu [128.59.255.226]
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.

Would changing worlds Fix this? has anyone tried transferring?

Quote:

Originally Posted by Hamilicar

Would changing worlds Fix this? has anyone tried transferring?

All NA servers are in the same physical space, so I doubt it.

Basically unplayable tonight. Got killed by 2 AoEs I was solidly out of in an expert. Had one boss attack telegraph and fire in less than a quarter second (the normal windup is around 2 seconds).

I'm not interested in hearing SE's weekly excuse of "we're still investigating." You've been saying that for months. Literally MONTHS. Has your investigation uncovered anything useful? Has your investigation made any forward progress on solving this problem experienced not only by me but by a large number of players across the Americas? The data is there. We've shown it to you time and time again. NTT can't handle it. Whether their network equipment simply isn't up to the task or they're throttling your service in some way, I don't know and I don't really care. What I care about is that I'm paying monthly for a game I routinely can't play when my friends are playing and that is not acceptable.

Quote:

Originally Posted by Hamilicar

Would changing worlds Fix this? has anyone tried transferring?

I happened to move to Ultros for 2 months from Excalibur. Ultros was no different, same issues with rubber-banding/lag and error 90006. I'm back on Excalibur now with the same exact problems I had previously.

I know that I'm going to hit the 6 months of lag and disconnects before this is fixed, if ever. The issue is in part to do with the network that SE currently uses provided by NTT.

1 1 ms 1 ms 1 ms 10.0.0.1
2 * 9 ms 9 ms 96.120.28.229
3 8 ms 9 ms 9 ms 68.87.204.37
4 8 ms 9 ms 8 ms 68.87.231.82
5 9 ms 10 ms 10 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 11 ms 10 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 9 ms 9 ms 9 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 22 ms 35 ms 16 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 64 ms 65 ms 64 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 10 ms 12 ms 10 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 61 ms 61 ms 62 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 64 ms 64 ms 65 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 65 ms 66 ms 66 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 65 ms 65 ms 68 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * 67 ms 66 ms 204.2.229.234
16 64 ms 71 ms 64 ms 204.2.229.106

Another one

1 9 ms 9 ms 8 ms 96.120.28.229
2 10 ms 9 ms 9 ms 96.120.28.229
3 23 ms 9 ms 8 ms 68.87.204.37
4 8 ms 9 ms 9 ms 68.87.231.82
5 11 ms 9 ms 12 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 10 ms 10 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 9 ms 9 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 11 ms 9 ms 10 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 64 ms 64 ms 65 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 10 ms 21 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 70 ms 61 ms 61 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 64 ms 65 ms 66 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 65 ms 65 ms 65 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 66 ms 66 ms 66 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * 65 ms * 204.2.229.234
16 66 ms 66 ms 64 ms 204.2.229.106

And another
1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 10 ms 8 ms 96.120.28.229
3 * 10 ms 10 ms 68.87.204.37
4 8 ms 8 ms 9 ms 68.87.231.82
5 10 ms * 19 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 12 ms 9 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 9 ms 9 ms 10 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 10 ms 10 ms 10 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 65 ms 65 ms 65 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 18 ms 18 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 62 ms 81 ms 65 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 64 ms 64 ms 65 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 65 ms 66 ms 65 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 66 ms 66 ms 66 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 64 ms * * 204.2.229.234
16 66 ms 65 ms 64 ms 204.2.229.106

Another one

1 1 ms 2 ms 1 ms 10.0.0.1
2 10 ms 9 ms 8 ms 96.120.28.229
3 9 ms 8 ms 8 ms 68.87.204.37
4 8 ms 9 ms 9 ms 68.87.231.82
5 10 ms 11 ms 12 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 11 ms 14 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 10 ms 9 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 9 ms 9 ms 9 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 64 ms 65 ms 65 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 9 ms 10 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 61 ms 61 ms 61 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 65 ms 73 ms 72 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 64 ms 85 ms 65 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 67 ms 65 ms 67 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 64 ms 65 ms 65 ms 204.2.229.234
16 64 ms 66 ms 64 ms 204.2.229.106

Recent test:
TIME: 9:35PM - 9:45PMCST 9/13/2018
The area seems very busy and populated at the moment. around limnsa lominsa market area. these tests were performed during gameplay.

1 2 ms 1 ms 1 ms 10.0.0.1
2 * 11 ms 9 ms 96.120.28.229
3 8 ms 9 ms 8 ms 68.87.204.37
4 8 ms 8 ms 10 ms 68.87.231.82
5 12 ms 11 ms 11 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 10 ms 11 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 11 ms * be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 12 ms 10 ms 9 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 186 ms 181 ms 171 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 10 ms 10 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 * * 185 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 185 ms 178 ms 178 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 115 ms * * ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 182 ms 182 ms 178 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * * * Request timed out.
16 118 ms 118 ms 107 ms 204.2.229.106

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 12 ms 9 ms 96.120.28.229
3 15 ms 8 ms 11 ms 68.87.204.37
4 9 ms 9 ms 10 ms 68.87.231.82
5 10 ms 10 ms 11 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 13 ms 13 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 17 ms 10 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 10 ms 10 ms 9 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 180 ms 177 ms 174 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 9 ms 38 ms 11 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 102 ms 102 ms 99 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 170 ms 166 ms 170 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 90 ms 90 ms 85 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 183 ms 180 ms 182 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 91 ms 102 ms 103 ms 204.2.229.234
16 93 ms 89 ms 91 ms 204.2.229.106

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 10 ms 9 ms 96.120.28.229
3 8 ms 9 ms 11 ms 68.87.204.37
4 8 ms 8 ms 9 ms 68.87.231.82
5 10 ms 10 ms 11 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 12 ms 11 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 18 ms 10 ms 17 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 12 ms 9 ms 9 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 172 ms 179 ms 169 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 19 ms 13 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 86 ms 188 ms 175 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 167 ms 173 ms 189 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 70 ms 72 ms 80 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 191 ms 184 ms 187 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * 70 ms 76 ms 204.2.229.234
16 94 ms 74 ms 78 ms 204.2.229.106

Trace complete.

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms 2 ms 3 ms 10.0.0.1
2 9 ms 10 ms 9 ms 96.120.28.229
3 9 ms 8 ms 8 ms 68.87.204.37
4 8 ms 9 ms 8 ms 68.87.231.82
5 11 ms 11 ms 14 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 11 ms 10 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 9 ms 16 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 10 ms 15 ms 10 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 183 ms 191 ms 172 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 10 ms 10 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 74 ms * 77 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 170 ms 169 ms 179 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 73 ms 70 ms 77 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 191 ms 183 ms 174 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * 84 ms 85 ms 204.2.229.234
16 67 ms 65 ms 66 ms 204.2.229.106

Trace complete.

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 9 ms 11 ms 8 ms 96.120.28.229
3 9 ms 9 ms 9 ms 68.87.204.37
4 8 ms 8 ms 8 ms 68.87.231.82
5 10 ms 10 ms 11 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 10 ms 11 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 * 11 ms 11 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 9 ms 9 ms 32 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 162 ms * 200 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 * 30 ms 11 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 68 ms 75 ms * ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 158 ms 164 ms 162 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 77 ms 82 ms 83 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 171 ms 179 ms 177 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 66 ms * 71 ms 204.2.229.234
16 67 ms 64 ms 65 ms 204.2.229.106

Trace complete.

Tracing route to 204.2.229.106 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 9 ms 10 ms 96.120.28.229
3 * 11 ms 10 ms 68.87.204.37
4 9 ms 15 ms 17 ms 68.87.231.82
5 11 ms 10 ms 9 ms be-163-ar01.area4.il.chicago.comcast.net [69.139.202.58]
6 10 ms 13 ms 11 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 12 ms 9 ms 10 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 9 ms 10 ms 10 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 177 ms 171 ms 176 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 10 ms 9 ms 10 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 64 ms 168 ms 170 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 151 ms 153 ms 161 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 80 ms 76 ms 72 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 169 ms 169 ms 185 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * * 68 ms 204.2.229.234
16 70 ms 66 ms 64 ms 204.2.229.106

Weekly Shaming Post on that San Jose Node!

02/13/2018 10:38 pm EST

Code:

1 1 ms 1 ms 1 ms [REDACTED] 2 10 ms 9 ms 8 ms [REDACTED] 3 12 ms 12 ms 11 ms [REDACTED] 4 11 ms 22 ms 10 ms [REDACTED] 5 13 ms 12 ms 10 ms ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 6 23 ms 19 ms 12 ms be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 7 12 ms 11 ms 10 ms be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 8 106 ms 105 ms 122 ms 50.242.151.58 9 118 ms 112 ms 104 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 10 107 ms 101 ms 116 ms ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 11 29 ms 29 ms 28 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 12 193 ms 185 ms 187 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 13 133 ms 125 ms 123 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 14 129 ms 126 ms 149 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 15 131 ms 129 ms 129 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 16 191 ms 193 ms * 204.2.229.234 17 146 ms 150 ms 136 ms 204.2.229.9

NA data center latency

Adding my traceroute as well, latency doubles on NTT nodes (highlighted).

Here is traceroute:

Code:

3 25ms 0/ 100 = 0% 0/ 100 = 0% tge7-4.gahgohcv01h.midwest.rr.com [24.164.98.1] 0/ 100 = 0% | 4 16ms 0/ 100 = 0% 0/ 100 = 0% be24.mcdnohbg01r.midwest.rr.com [24.33.103.96] 0/ 100 = 0% | 5 21ms 0/ 100 = 0% 0/ 100 = 0% be14.pltsohae01r.midwest.rr.com [65.29.1.87] 0/ 100 = 0% | 6 25ms 0/ 100 = 0% 0/ 100 = 0% be25.clmkohpe01r.midwest.rr.com [65.29.1.28] 0/ 100 = 0% | 7 35ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.252 0/ 100 = 0% | 8 36ms 0/ 100 = 0% 0/ 100 = 0% bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20] 0/ 100 = 0% | 9 31ms 0/ 100 = 0% 0/ 100 = 0% 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66] 0/ 100 = 0% | 10 32ms 0/ 100 = 0% 0/ 100 = 0% ix-ae-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.97] 0/ 100 = 0% | 11 32ms 0/ 100 = 0% 0/ 100 = 0% if-ae-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2] 0/ 100 = 0% | 12 34ms 0/ 100 = 0% 0/ 100 = 0% 64.86.78.18 0/ 100 = 0% | 13 32ms 0/ 100 = 0% 0/ 100 = 0% ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158] 0/ 100 = 0% | 14 33ms 0/ 100 = 0% 0/ 100 = 0% ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205] 0/ 100 = 0% | 15 89ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 0/ 100 = 0% | 16 81ms 0/ 100 = 0% 0/ 100 = 0% ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 0/ 100 = 0% | 17 94ms 0/ 100 = 0% 0/ 100 = 0% ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 0/ 100 = 0% | 18 95ms 0/ 100 = 0% 0/ 100 = 0% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 0/ 100 = 0% | 19 94ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.234 0/ 100 = 0% | 20 93ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.111

About a week ago, I logged on to FFXIV for the first time in a few months. I had upgraded to a new router; had no issues logging on or playing. We got a house and spent all night furnishing it. Fast forward to this past weekend and I started getting random 90006 disconnects every few minutes. Couldn't play; figured DDoS and quit for the night.

Now it's a couple of days later and I'm getting the same problems. I was able to log in and do Ananta dailies for about 5 minutes before getting kicked. Went to the forums; set up the proper port forwarding; came back and now it's 90006-ing me about 30 seconds after I log in, each time. Even after I disabled the port forwarding I did, nothing changed.

Not sure if it's a coincidence, but this has happened after 8 p.m. CST each night. After further testing, this happens anytime I'm logged in, day or night. I'm in Arkansas in the U.S., my ISP is Comcast, and I am including a traceroute I attempted to run -- not sure if I did it right. I play on PC.

https://farm5.staticflickr.com/4612/...0c29efd3_b.jpg

I've played more than 3,500 hours of FF over several years and I've never had this issue before. I know the new router seems like a red flag, but I've had zero issues playing any other game on PC or PS4, and I ran FFXIV perfectly the same night I replaced the router.

Hello everyone.

We would like to thank you for your continued patience with this problem. We are still looking into the issue of latency and disconnections from the North American Data Center. Unfortunately, the problems have not subsided, but rest assured that we are still collecting data from players and are escalating that information daily to be investigated. Additionally, we have been contacting customers individually for information that we cannot discuss in a public setting. If you receive an email to the address associated with your Square Enix account, please respond as soon as possible as this information is valuable to our investigation.
If you have not posted a trace route to this thread, please do so, preferably at the times of the day you would normally receive latency/disconnection errors. Again, we thank you for your understanding and we hope we can resolve this issue quickly.

Thank you for visiting the Final Fantasy XIV Technical Support Forum.

Quote:

Originally Posted by Ariellendera

We would like to thank you for your continued patience with this problem. We are still looking into the issue of latency and disconnections from the North American Data Center. Unfortunately, the problems have not subsided

Hoping the problem will just go away isn't working? Well maybe if you do it for another week.

I can't begin to tell you how sick and tired I am of hearing this nonsense as you continue to justify why your game doesn't function properly at certain times of the day and despite literally hundreds of players giving you all the data you ask for, you just can't seem to figure out what the problem could be.

I love FFXIV. I really do. It's a great game. But if I can't play it, I'm not going to continue paying for it. I don't think that's a super unreasonable position.

Seeing how "ae-5.a00.lsanca20.us.bb.gin.ntt.net" has constantly lagged out and added an extra 100+ latency to my connection, thus making it laggier for me to California from Hawaii than EASTERN CANADA used to be I'm not holding my breath.

Every day around 2-3 hours earlier as of this post my connection jumps by 100-150 latency and with some packet loss on occasion. This has been going on since early stormblood.

VPNs should not be reporting a 60%+ connection improvement to the servers. What is NTT doing?

Quote:

Originally Posted by Frent

About a week ago, I logged on to FFXIV for the first time in a few months. I had upgraded to a new router; had no issues logging on or playing. We got a house and spent all night furnishing it. Fast forward to this past weekend and I started getting random 90006 disconnects every few minutes. Couldn't play; figured DDoS and quit for the night.

Now it's a couple of days later and I'm getting the same problems. I was able to log in and do Ananta dailies for about 5 minutes before getting kicked. Went to the forums; set up the proper port forwarding; came back and now it's 90006-ing me about 30 seconds after I log in, each time. Even after I disabled the port forwarding I did, nothing changed.

Not sure if it's a coincidence, but this has happened after 8 p.m. CST each night. After further testing, this happens anytime I'm logged in, day or night. I'm in Arkansas in the U.S., my ISP is Comcast, and I am including a traceroute I attempted to run -- not sure if I did it right. I play on PC.

https://farm5.staticflickr.com/4612/...0c29efd3_b.jpg

I've played more than 3,500 hours of FF over several years and I've never had this issue before. I know the new router seems like a red flag, but I've had zero issues playing any other game on PC or PS4, and I ran FFXIV perfectly the same night I replaced the router.

Unfortunately, this is not the correct IP address. Please perform a trace route to 204.2.229.9 and post the report here. Thank you.

Quote:

Originally Posted by Callinon

Hoping the problem will just go away isn't working? Well maybe if you do it for another week.

I can't begin to tell you how sick and tired I am of hearing this nonsense as you continue to justify why your game doesn't function properly at certain times of the day and despite literally hundreds of players giving you all the data you ask for, you just can't seem to figure out what the problem could be.

I love FFXIV. I really do. It's a great game. But if I can't play it, I'm not going to continue paying for it. I don't think that's a super unreasonable position.

It is not unreasonable at all. However, the game and it's servers are functioning properly, the issue lies with how you are routed to them. This means a lot of things are out of our control and it will take time for us to find a solution. We apologize for the inconvenience and thank you for your patience.

Quote:

Originally Posted by Einmimiria

It is not unreasonable at all. However, the game and it's servers are functioning properly, the issue lies with how you are routed to them. This means a lot of things are out of our control and it will take time for us to find a solution. We apologize for the inconvenience and thank you for your patience.

True but server are in California...1 of the worst spot to have server for all NA players with questionable ISP. I mean yeah sure Montreal Server weren't great and all but table flip on us East Coaster Player to please The West is not great idea.Centralize it would be wiser esp how the game respond via client for GCD(abilities) & nodes landscape for Internet,bigger lobby which Sacramento don't have currently.I hope next time SE is taking notes for relocations esp for FFXIV.

Here the issues I have with your ISP SE:Congest Nodes,DDOS Attacks,Package Lost On Nodes.

Now You re Server SE:Why each time i check WinMTR i see package lost on Server Lobby like i see 1-7% on NTT nodes but 15-24% on lobby in a hour.

We all know we are stuck with the current ISP for FFXIV. Until NTT decide to fix issues which i highly doubt because repeal of Net Neutrality in USA (You might need pay them to fix it quicker) or you re higher boss give green lights to Yoshi P to change ISP & Data Centers.Until then complains will piles ups.

Quote:

Originally Posted by Einmimiria

Unfortunately, this is not the correct IP address. Please perform a trace route to 204.2.229.9 and post the report here. Thank you.

https://farm5.staticflickr.com/4721/...a95645d5_b.jpg traceroute2

Quote:

Originally Posted by Einmimiria

It is not unreasonable at all. However, the game and it's servers are functioning properly, the issue lies with how you are routed to them. This means a lot of things are out of our control and it will take time for us to find a solution. We apologize for the inconvenience and thank you for your patience.

You're right it is. Guess what though, it's not some wacky rural backbone run by some guy in Wyoming with his donkey and a big jug of booze. It's your ISP that's the problem. It's their infrastructure that can't handle your traffic at peak hours. And it's affecting EVERYBODY, not just me. There might be some routes actually ON the west coast that get around this issue, but most of the country doesn't live on the west coast. Actually most of the country lives over a thousand miles away from the west coast.

So the solution seems actually quite simple:
1: Serve notice to your ISP that they are not providing the level of service required by your customers and therefore are not providing the level of service required by your business.
2: (If they won't do anything about it, which at this point seems a safe assumption) MOVE.

I realize it's neither simple nor cheap to relocate this sort of thing. I really do understand that. But you also made this particular bed for yourselves. I and thousands of others begged you to locate your servers some where more central. You moved from the far east of the continent to the far west. This was not an improvement. It's a big continent. With non-amazing networking infrastructure. May I suggest that this time you actually listen and consider Illinois, Texas, or Nebraska? All of those states have excellent data center services. Illinois and Texas already have facilities that host WoW servers flawlessly. You can't cheap out on this again.

Yep also throwing in my utter disappointment with SE's response to this networking issue.

It seems to most of us that there is a problem with the NTT set of nodes. The fact that you're still "collecting" data is a bit baffling.

The wall of silence regarding this issue is intolerable.

Seriously, what is the actual issue and what are you doing about it?

FWIW, I hopped on with vain hope this morning about 7:30-7:45 CST and have had only one 90006 in the 30-45 minutes I've been online. Progress?

Update: This time I had a 90001 about 8:35 CST. Still, only two errors in an hour!
Update 2: No crashes at all in an hour since the 90001.
Update 3: No interruptions or disconnects since the 8:35 CST one!
Update 4: Still no disconnects since 8:35 this morning. Fingers crossed.
Update 5: I kept FFXIV up all day since the first time I logged in. Was worried about peak traffic but no issues tonight. Logged off safely at 10:00 CST.