Lag spike/90000 error DC victims -- Help gather data on the problem

[DiamonteZ]

was already a thread like this, they locked it and put it in resolved.
NOT Being Addressed/Currently Reviewing
but resolved.
It is not resolved.
Good luck, appears they don't care.

My thread was one of those.

[gl0ry]

Had to think of my own solution. I used a VPN in the past for wow when it had issues with time warner. Just tried one for ARR and it is AMAZING. 0 lag issues now.

I highly suggest anyone looking for an immediate fix to try out Battleping...

[BedDave]

Well, I don't have the mentioned hop on my trace but I have started having random disconnection problems after the September 3 server maintenance. I had no disconnection problems prior to that date, when I could connect to the server. My problem mostly manifests when doing dungeons where I get lag spikes where everyone stops moving for 10-15 seconds then everything updates and will be fine for a few more minutes where it will do it again. Sometimes the lag will last longer and that is normally when I will get disconnected.

In normal play, I do disconnect (mostly in primetime hours) but I don't have the lag spikes like I do in the dungeons.

Here is my tracert:

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 10.0.1.1
2 9 ms 10 ms 10 ms 10.234.0.1
3 11 ms 17 ms 10 ms 10.41.0.13
4 34 ms 28 ms 29 ms 10.41.0.6
5 25 ms 25 ms 26 ms 10.50.0.2
6 25 ms 25 ms 30 ms te0-0-0-14.ccr21.atl04.atlas.cogentco.com [38.122.46.113]
7 27 ms 33 ms 27 ms be2034.ccr21.atl01.atlas.cogentco.com [154.54.6.113]
8 31 ms 30 ms 34 ms te0-2-0-3.ccr21.dca01.atlas.cogentco.com [154.54.24.9]
9 52 ms 40 ms 37 ms te0-0-0-20.mpd21.jfk02.atlas.cogentco.com [154.54.26.178]
10 44 ms 45 ms 54 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 46 ms 49 ms 44 ms 38.122.42.34
12 * * * Request timed out.
13 46 ms 48 ms 52 ms 192.34.76.2
14 48 ms 45 ms 49 ms 199.91.189.234
15 49 ms 51 ms 58 ms 199.91.189.74

Trace complete.

[Miburo]

Bumping thread.

[Keeghan]

Right there with you with RCN, tiscali.net, and many, many 90000's.

[Shawnji]

So, I have no idea why or how, but my lag has gone away. After a week of it constantly, it has finally gone away. Both times I logged in today, I was lag free. The only thing I can think that I've done differently from some of you here is that I posted in the Technical Support section of the Japanese forums, in Japanese. I live in Japan, and my ISP is through OCN / NTT Flets Hikari, but I had contacted them and was told the problem was on Square-Enix's end, so I'm confused as to how this got worked out. I'm not sure what this means, but here it is. Make of it what you will. If the lag comes back or I get 90000 errors again, I'll be sure to post about it.

[SionDurant]

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 10.50.192.1
3 13 ms 10 ms 9 ms ten0-0-0-7.ORLD02-ser1.bhn.net [72.31.239.224]
4 12 ms 14 ms 20 ms ten0-0-0-7.orld01-ser1.bhn.net [72.31.194.58]
5 23 ms 21 ms 26 ms ten0-8-0-0.tamp20-CAR1.bhn.net [71.44.1.210]
6 21 ms 16 ms 21 ms 71.44.3.92
7 17 ms 15 ms 23 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66
.109.6.96]
8 41 ms 43 ms 42 ms ae-0-0.a1.pit75.tbone.rr.com [66.109.1.70]
9 40 ms 42 ms 41 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
10 41 ms 39 ms 41 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
11 62 ms 66 ms 62 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
12 62 ms 61 ms 69 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
13 62 ms 60 ms 62 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46
.217]
14 60 ms 58 ms 60 ms te0-7-0-4.ccr22.ord01.atlas.cogentco.com [154.54
.30.102]
15 75 ms * 81 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42
.6]
16 70 ms 70 ms 69 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
17 67 ms 68 ms 67 ms 38.122.42.34
18 * * * Request timed out.
19 66 ms 68 ms 65 ms 192.34.76.2
20 70 ms 66 ms 79 ms 199.91.189.234
21 65 ms 82 ms 65 ms 199.91.189.74

Trace complete.

[Brobotnik]

OK, I get this problem too. I'll point out again that while I can't play the game at all, my girlfriend plays on the same connection with no problems.

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 12 ms 10 ms 13 ms cpc22-stav14-2-0-gw.17-3.cable.virginmedia.com [
92.233.1.1]
2 16 ms 15 ms 16 ms aztw-core-2b-ae7-719.network.virginmedia.net [80
.1.243.217]
3 20 ms 19 ms 18 ms brhm-bb-1c-ae13-0.network.virginmedia.net [80.1.
240.177]
4 54 ms 19 ms 20 ms brhm-bb-1b-ae11-0.network.virginmedia.net [62.25
3.174.101]
5 42 ms 23 ms 25 ms teln-ic-1-ae0-0.network.virginmedia.net [212.43.
163.250]
6 22 ms 23 ms 23 ms m282-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.26
]
7 24 ms 27 ms 24 ms 154.54.72.194.bcube.co.uk [154.54.72.194]
8 30 ms 30 ms 29 ms te0-3-0-0.ccr22.lpl01.atlas.cogentco.com [154.54
.60.110]
9 29 ms 30 ms 28 ms te0-1-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.37.145]
10 100 ms 100 ms 99 ms te0-2-0-1.ccr21.ymq02.atlas.cogentco.com [154.54
.87.62]
11 100 ms 98 ms 99 ms 38.122.42.34
12 * * * Request timed out.
13 113 ms 98 ms 101 ms 192.34.76.2
14 127 ms 100 ms 98 ms 199.91.189.234
15 97 ms 98 ms 96 ms 199.91.189.74

Trace complete.

[Soulsa]

Started today for me and to be honest getting frustrated as hell because I have had every error being posted about this bloody game. This ISN'T a FTP THIS IS A PTP......

[Folsom]

Started today for me and to be honest getting frustrated as hell because I have had every error being posted about this bloody game. This ISN'T a FTP THIS IS A PTP......

This thread seems to be indicating that the problem may be arising from outside of SE. Being PTP instead of FTP does not enable SE to control the internet between you and them.