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

A TWC customer here.

Here is the info when I rant he tracert.

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 41 ms 31 ms 28 ms cpe-71-74-224-1.neo.res.rr.com [71.74.224.1]
3 12 ms * 11 ms gig4-2.lornoh1-rtr1.neo.rr.com [24.164.104.73]
4 18 ms 16 ms * network-184-059-246-106.neo.rr.com [184.59.246.1
06]
5 19 ms * 34 ms network-065-029-001-032.midwest.rr.com [65.29.1.
32]
6 43 ms * 33 ms 107.14.19.58
7 * * 27 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
8 66 ms * 55 ms te0-7-0-10.ccr21.iad02.atlas.cogentco.com [154.5
4.10.193]
9 60 ms 90 ms 101 ms be2042.ccr21.dca01.atlas.cogentco.com [154.54.26
.125]
10 66 ms 88 ms * te0-0-0-8.ccr21.jfk02.atlas.cogentco.com [154.54
.42.18]
11 75 ms 89 ms 73 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.
50]
12 49 ms 46 ms * 38.122.42.34
13 45 ms 63 ms 45 ms 10.2.2.1
14 108 ms 45 ms 62 ms 192.34.76.2
15 46 ms 67 ms 62 ms 199.91.189.234
16 49 ms 47 ms 53 ms 199.91.189.74

Trace complete.


Last night was playing fine only errored 90000 twice once every 6 hours or so. but most of the time its r0 every 10 mins, and today its every 30 seconds..

I called TWC and they claim nothing is wrong, even had them reset my modem from their end and still same old problems.

So far we have: Power cycled and hard reset our modem and router multiple times, DHCP Reset for all computers on the network, called Cox Cable and they insist they can find nothing wrong. Bypassing our router is not an option as our home is run from a smart-box type nerve center. This ONLY started after the last patch just after release. No problems before then, even during beta.

Unplayable. I did a tracert and out of 13 hops 3 to 4 random hops times out.

Quote:

---

Originally Posted by desertw0lf

So far we have: Power cycled and hard reset our modem and router multiple times, DHCP Reset for all computers on the network, called Cox Cable and they insist they can find nothing wrong. Bypassing our router is not an option as our home is run from a smart-box type nerve center. This ONLY started after the last patch just after release. No problems before then, even during beta.

---

Same for me, it started after the server upgrades. It's not stable for everyone, SE.

Seriously, anyone have any ideas? My partner and I cannot play because of the COMPLETELY random E90K's. We even had our cable internet company come out and check the lines, give us a brand new modem, the whole shebang.

Our modem signals are +/- 1.5 from 0dB which are in the optimal range.
Signal to noise ratios are optimal.

We have opened the ports suggested by SE for playing two accounts on two PCs through a router.

Nothing running in the background.

Tracert today:

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

1 1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 33 ms 7 ms 10.89.0.1
3 9 ms 9 ms 9 ms 24-234-16-101.ptp.lvcm.net [24.234.16.101]
4 11 ms 10 ms 10 ms 24-234-6-241.ptp.lvcm.net [24.234.6.241]
5 9 ms 22 ms 9 ms 24-234-6-222.ptp.lvcm.net [24.234.6.222]
6 31 ms 57 ms 22 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
7 15 ms 22 ms 20 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 102 ms 96 ms 99 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 104 ms 103 ms 113 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 115 ms 104 ms 127 ms 192.34.76.2
11 112 ms 109 ms 103 ms 199.91.189.234
12 95 ms 102 ms 105 ms 199.91.189.74

Trace complete.

We played FINE for FOUR HOURS and then we did Garuda and would 90k REPEATEDLY. Obviously this has to do with the instance servers. They are NOT fixed. This issue ONLY started occurring after the previous patch. We literally did not have the 90K issues that others did during beta.

It's gotten to the point with the 90k DC's that my roommate and I will not be playing beyond the inital month unless they fix the issue. It's incredibly frustrating.

Can't even login... get 90k on the initial loading screen...

Been happening since Launch day for me.

Routenverfolgung zu neolobby02.ffxiv.com [199.91.189.74] über maximal 30 Abschni
tte:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.1.1]
2 41 ms 41 ms 41 ms 217.0.118.44
3 57 ms 55 ms 54 ms 87.186.240.246
4 43 ms 42 ms 43 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.22]
5 43 ms 43 ms 43 ms 80.157.130.78
6 148 ms 150 ms 150 ms if-9-2.tcore1.FNM-Frankfurt.as6453.net [195.219.
50.42]
7 147 ms 148 ms 146 ms if-6-3.tcore1.AV2-Amsterdam.as6453.net [195.219.
194.77]
8 138 ms 133 ms 138 ms if-2-2.tcore2.av2-amsterdam.as6453.net [195.219.
194.6]
9 134 ms 133 ms 133 ms if-8-2.tcore2.L78-London.as6453.net [80.231.131.
5]
10 133 ms 135 ms 133 ms if-20-2.tcore2.nyy-newyork.as6453.net [216.6.99.
13]
11 159 ms 133 ms 154 ms if-5-2.tcore2.mtt-montreal.as6453.net [216.6.99.
30]
12 133 ms 152 ms 132 ms if-0-2.tcore1.mtt-montreal.as6453.net [216.6.115
.89]
13 136 ms 132 ms 155 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
14 146 ms 148 ms 146 ms 66.198.96.50
15 134 ms 134 ms 134 ms 192.34.76.2
16 135 ms 135 ms 135 ms 199.91.189.234
17 134 ms 133 ms 133 ms neolobby02.ffxiv.com [199.91.189.74]

BUMP square enix fix your SHIT Fixit!!!!!

Comcast here, and I just started to experience this today. Here are the logs I have.


1 27 ms 27 ms 19 ms 68.38.144.1
2 10 ms 12 ms 13 ms xe-10-3-0-32767-sur01.avenel.nj.panjde.comcast.n
et [68.85.129.89]
3 12 ms 13 ms 13 ms ae-4-0-ar03.plainfield.nj.panjde.comcast.net [68
.85.62.9]
4 18 ms 18 ms 16 ms pos-3-7-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.95.173]
5 18 ms 38 ms 19 ms pos-1-3-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.190]
6 32 ms 29 ms 30 ms ix-8-0-1-0.tcore1.NTO-NewYork.as6453.net [209.58
.26.141]
7 37 ms 45 ms 39 ms if-5-5.tcore1.NYY-NewYork.as6453.net [216.6.90.5
]
8 38 ms 37 ms 42 ms if-11-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
1]
9 37 ms 43 ms 36 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226
.13]
10 37 ms 39 ms 37 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
11 41 ms 37 ms 39 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
12 * 56 ms 54 ms 66.198.96.50
13 60 ms 71 ms 56 ms 192.34.76.2
14 58 ms 57 ms 60 ms 199.91.189.234
15 58 ms 59 ms 58 ms 199.91.189.74

Trace complete.

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further try to discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

Good Luck!