Repeated 90k error

Quote:

Originally Posted by Bluevann

At this point I highly doubt our ISPs are to blame. All the other internet services are working to me (youtube, movies in streaming, FFXI...), and clearly we're up to 9 pages of people having big issues (not the occasional DC, but the inability to play the game entirely or close to that). We all have different ISPs and locations, so the only factor we all share in common is the XIV lobby server. This is definitely an issue on SE's end, not ours.

Quote:

Originally Posted by Aelthar

Just a little update:

i've extended my previously expired trial of WTFAST by 14 days and IT SEEMS that the issue got fixed for me.

Clearly, this is not a solution, but a work around. But for who, like me, doesn't want to "waste" their gaming weekend can give this solution a shot, waiting that hopefully SE wakes up from their poorly professional PR slumber, to give us pointer whether this issue is client or server side.

Quote:

Originally Posted by Durin

I tried it using battleping, it fixed the issue, so i'd say it is safe to say it is a routing issue.

Just further proves the point I made earlier. If a VPN/Proxy service resolves the problem, then it is a problem in route to the servers. Things are the same at both your local and ending network segments--what you've changed is how your data is handled in route between the two.

Quote:

Originally Posted by Culfinrandir

Same problems this morning. It has nothing to do with my ISP or my computer, I can say that for certain before anyone pipes up. There's a fault at SE end. A trace shows I can get into iWeb (now Internap, they haven't updated their info in over a year since buyout), the hosting service for SE (they don't have their own). However, I can't get to the SE servers that run the game. Other Internap hosted sites are running.

If you are tracing to an iWeb address, then you aren't tracing to the FFXIV servers. It sounds like you are making the same mistake I see on here a lot and are tracing to the www.eidos.com web server (184.107.107176...go ahead and ping or do an nslookup on the URL if you don't believe me). That server is NOT connected to this game, is physically in a different section of Montreal, hosted on someone else's network (XIV is on Ormuco, and not iWeb), and you take a different route to get there. You need to test against the IP your client actually uses. For Canada, it should start with 199.

my route isnt via gtt but still get the DCs.
Traceroute has started…

traceroute to 199.91.189.38 (199.91.189.38), 64 hops max, 72 byte packets
1 skyrouter (192.168.1.1) 1.710 ms 1.514 ms 0.938 ms
2 * * *
3 02780820.bb.sky.com (2.120.8.32) 11.360 ms 8.805 ms 10.195 ms
4 ae51.edge6.london1.level3.net (212.113.9.53) 9.929 ms 10.486 ms 9.713 ms
5 ae-11-11.car2.montreal2.level3.net (4.69.141.1) 84.308 ms 84.837 ms *
6 ae-11-11.car2.montreal2.level3.net (4.69.141.1) 163.745 ms * *
7 ormuco-comm.car2.montreal2.level3.net (4.59.178.74) 89.656 ms 85.134 ms 84.976 ms
8 192.34.76.10 (192.34.76.10) 98.200 ms 99.242 ms 84.787 ms
9 * 199.91.189.242 (199.91.189.242) 87.584 ms 85.542 ms
10 199.91.189.38 (199.91.189.38) 85.322 ms 85.383 ms *

Quote:

Originally Posted by Valio

Location: Finland
ISP: Elisa
Server: Diabolos

Massive connection issues(error 90k, 2002) since roulette reset time yesterday. Game still unplayable. Did some traces and here is result while the connection seems stable.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 3 ms 3 ms 1 ms vanhel1.fi.elisa.net [88.114.80.1] 2 <1 ms <1 ms <1 ms ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50] 3 <1 ms <1 ms <1 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205] 4 <1 ms <1 ms <1 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250] 5 <1 ms <1 ms <1 ms ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19 1.153] 6 7 ms 7 ms 7 ms 213.192.184.201 7 7 ms 7 ms 7 ms ae1-103.stk10.ip4.gtt.net [141.136.97.153] 8 115 ms 115 ms 116 ms xe-9-0-0.mtl10.ip4.gtt.net [141.136.105.162] 9 115 ms 115 ms 116 ms ormuco-gw.ip4.gtt.net [216.221.156.110] 10 115 ms 115 ms 115 ms 192.34.76.2 11 116 ms 116 ms 116 ms 199.91.189.234 12 116 ms 116 ms 115 ms 199.91.189.38 Trace complete.

And here is some results when I notice massive lag right before 90k.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 9 ms 2 ms 2 ms vanhel1.fi.elisa.net [88.114.80.1] 2 1 ms <1 ms <1 ms ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50] 3 1 ms <1 ms <1 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205] 4 1 ms <1 ms <1 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250] 5 <1 ms <1 ms <1 ms ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19 1.153] 6 7 ms 7 ms 7 ms 213.192.184.201 7 7 ms 7 ms 7 ms ae1-103.stk10.ip4.gtt.net [141.136.97.153] 8 116 ms 116 ms 115 ms xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74] 9 * 116 ms * ormuco-gw.ip4.gtt.net [216.221.156.110] 10 116 ms 116 ms 116 ms 192.34.76.2 11 116 ms 116 ms 116 ms 199.91.189.234 12 * 117 ms * 199.91.189.38 13 116 ms * 116 ms 199.91.189.38 Trace complete. Tracing route to 199.91.189.38 over a maximum of 30 hops 1 6 ms 1 ms 1 ms vanhel1.fi.elisa.net [88.114.80.1] 2 1 ms <1 ms <1 ms ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50] 3 1 ms <1 ms <1 ms ae10.helpa-p1.fi.elisa.net [139.97.6.205] 4 <1 ms <1 ms <1 ms ae2.helpa-gw1.fi.elisa.net [139.97.6.250] 5 32 ms 31 ms 28 ms ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.19 1.153] 6 7 ms 8 ms 7 ms 213.192.184.201 7 7 ms 7 ms 7 ms ae1-103.stk10.ip4.gtt.net [141.136.97.153] 8 118 ms 169 ms * xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106] 9 118 ms 118 ms 118 ms ormuco-gw.ip4.gtt.net [216.221.156.110] 10 118 ms 118 ms 118 ms 192.34.76.2 11 133 ms 118 ms 122 ms 199.91.189.234 12 * 118 ms 118 ms 199.91.189.38 Trace complete.

And pathping results showing nasty packet loss.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 vanhel1.fi.elisa.net [88.114.80.1] 2 ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50] 3 ae10.helpa-p1.fi.elisa.net [139.97.6.205] 4 ae2.helpa-gw1.fi.elisa.net [139.97.6.250] 5 ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153] 6 213.192.184.201 7 ae1-103.stk10.ip4.gtt.net [141.136.97.153] 8 xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106] 9 ormuco-gw.ip4.gtt.net [216.221.156.110] 10 192.34.76.2 11 199.91.189.234 12 199.91.189.38 Computing statistics for 300 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 1 --- 100/ 100 =100% 100/ 100 =100% vanhel1.fi.elisa.net [88.114.80.1] 0/ 100 = 0% | 2 3ms 0/ 100 = 0% 0/ 100 = 0% ge3-0-0.vanhel-p1.fi.elisa.net [139.97.11.50] 0/ 100 = 0% | 3 6ms 0/ 100 = 0% 0/ 100 = 0% ae10.helpa-p1.fi.elisa.net [139.97.6.205] 0/ 100 = 0% | 4 3ms 0/ 100 = 0% 0/ 100 = 0% ae2.helpa-gw1.fi.elisa.net [139.97.6.250] 0/ 100 = 0% | 5 3ms 0/ 100 = 0% 0/ 100 = 0% ge0-1-3-500.bbr1.ldn1.uk.eunetip.net [213.192.191.153] 0/ 100 = 0% | 6 10ms 0/ 100 = 0% 0/ 100 = 0% 213.192.184.201 0/ 100 = 0% | 7 12ms 0/ 100 = 0% 0/ 100 = 0% ae1-103.stk10.ip4.gtt.net [141.136.97.153] 27/ 100 = 27% | 8 --- 100/ 100 =100% 73/ 100 = 73% xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106] 0/ 100 = 0% | 9 120ms 40/ 100 = 40% 13/ 100 = 13% ormuco-gw.ip4.gtt.net [216.221.156.110] 0/ 100 = 0% | 10 120ms 37/ 100 = 37% 10/ 100 = 10% 192.34.76.2 0/ 100 = 0% | 11 120ms 27/ 100 = 27% 0/ 100 = 0% 199.91.189.234 7/ 100 = 7% | 12 119ms 34/ 100 = 34% 0/ 100 = 0% 199.91.189.38 Trace complete.

Your issues appear to be with your ISP's routing partner, specifically right around where you are exiting their network at the exchange into Ormuco. Your ISP can actually resolve this for you (or at least make an honest effort). They can either notify their partner and try to get them to address the issue on their network, or they can switch you to an alternate routing partner to see if you get a more stable route.

Quote:

Originally Posted by ingouk

my route isnt via gtt but still get the DCs.
Traceroute has started…

traceroute to 199.91.189.38 (199.91.189.38), 64 hops max, 72 byte packets
1 skyrouter (192.168.1.1) 1.710 ms 1.514 ms 0.938 ms
2 * * *
3 02780820.bb.sky.com (2.120.8.32) 11.360 ms 8.805 ms 10.195 ms
4 ae51.edge6.london1.level3.net (212.113.9.53) 9.929 ms 10.486 ms 9.713 ms
5 ae-11-11.car2.montreal2.level3.net (4.69.141.1) 84.308 ms 84.837 ms *
6 ae-11-11.car2.montreal2.level3.net (4.69.141.1) 163.745 ms * *
7 ormuco-comm.car2.montreal2.level3.net (4.59.178.74) 89.656 ms 85.134 ms 84.976 ms
8 192.34.76.10 (192.34.76.10) 98.200 ms 99.242 ms 84.787 ms
9 * 199.91.189.242 (199.91.189.242) 87.584 ms 85.542 ms
10 199.91.189.38 (199.91.189.38) 85.322 ms 85.383 ms *

And like so many others, you have problems in route... Level3, what a surprise....

Quote:

Originally Posted by Raist

Just further proves the point I made earlier. If a VPN/Proxy service resolves the problem, then it is a problem in route to the servers. Things are the same at both your local and ending network segments--what you've changed is how your data is handled in route between the two.

If you are tracing to an iWeb address, then you aren't tracing to the FFXIV servers. It sounds like you are making the same mistake I see on here a lot and are tracing to the www.eidos.com web server (184.107.107176...go ahead and ping or do an nslookup on the URL if you don't believe me). That server is NOT connected to this game, is physically in a different section of Montreal, hosted on someone else's network (XIV is on Ormuco, and not iWeb), and you take a different route to get there. You need to test against the IP your client actually uses. For Canada, it should start with 199.

I traced the foreign IP of the TCP connection the ffxiv.exe process (PID 4760) on my windows machine has connected according to netstat -n -o:

Code:

Active Connections Proto Local Address Foreign Address State PID TCP 127.0.0.1:49810 127.0.0.1:49811 ESTABLISHED 2900 TCP 127.0.0.1:49811 127.0.0.1:49810 ESTABLISHED 2900 TCP 192.168.0.13:52629 195.145.147.91:80 TIME_WAIT 0 TCP 192.168.0.13:52630 195.145.147.91:80 TIME_WAIT 0 TCP 192.168.0.13:52637 173.194.113.97:80 TIME_WAIT 0 TCP 192.168.0.13:52638 173.194.113.97:80 TIME_WAIT 0 TCP 192.168.0.13:52639 173.194.113.97:80 TIME_WAIT 0 TCP 192.168.0.13:52646 62.159.74.59:80 TIME_WAIT 0 TCP 192.168.0.13:52647 62.159.74.59:80 TIME_WAIT 0 TCP 192.168.0.13:52652 62.159.74.8:80 TIME_WAIT 0 TCP 192.168.0.13:52659 199.91.189.106:54994 TIME_WAIT 0 TCP 192.168.0.13:52660 199.91.189.145:54992 ESTABLISHED 4760 TCP 192.168.0.13:52661 199.91.189.145:54992 ESTABLISHED 4760

The complete route was:

Code:

Host Information 1, -------------- ,192.168.0.253 2, -------------- ,217.0.117.77 3, -------------- ,87.190.188.202 4, -------------- ,217.239.48.170 5,xe-11-0-1.fra29.ip4.gtt.net,141.136.101.233 6,xe-4-2-0.mtl10.ip4.gtt.net,141.136.107.125 7,ormuco-gw.ip4.gtt.net,216.221.156.110 8, -------------- ,192.34.76.2 9, -------------- ,199.91.189.234 10, -------------- ,199.91.189.145

So I think the route I checked is actually the route to their data center servers.

Update: I now have massive packet loss on all hops starting in the gtt network up to the SE server IP.

Disconnecting all the time resulted in my losing my alexandrite map :mad:

Location: EU, Italy
ISP: Fastweb
Server: Ragnarok

error 9000 10sec after login!

playing since 3 months again, and yesterday i had my 90k error and then error 2002. today the same crap. other online games works fine. hope they fix it soon

Location: EU, Germany
ISP: Telecom
Server: Hyperion

At this rate I am beginning to lose interest in the game. Why pay a monthly sub when the game isn't playable lately? Its frustrating when your doing your dailies and get kicked off the server and then can't get back in due to lobby server error. :mad:

I too don't have any problems with other sites, games etc. Have a good and steady connection.

I have the same issue since today. Yesterday I played for hours and hours without any 90k in near sight. Just now I got 3 in a row and just get frustrated and did not log back in again (Server: Excalibur Country: Germany). Never had issues before.