This has been going on since I returned to the game in early may. I have played on and off since 1.0 and never previously had this issue. I've seen multiple post here and there however none of their fixes have worked for me (opening ports, changing UPnP from 1 to 0, trace routing and finding the parts not responding, one post changing a few things in I.E.).
I tried trace routes 3x however I did not see any glaring issues. My GF plays from the same connection and had 0 90002 issues until the launch of shadowbringers and now about every hour we 90002. This was annoying but it's made worse with the fact that there is no grace period before you have to go through the queue again.
Trace routes (all about an hour apart)
Quote:
C:\Users\Seyon> tracert 204.2.229.10
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 2 ms 4 ms 1 ms 192.168.0.1
2 12 ms 13 ms 13 ms 10.104.240.1
3 12 ms 11 ms 14 ms ten-0-5-1-5.orld26-ser2.bhn.net [72.31.216.240]
4 26 ms 29 ms 29 ms bundle-ether26.orld31-car2.bhn.net [72.31.195.62]
5 24 ms 16 ms 19 ms 72-31-220-138.net.bhntampa.com [72.31.220.138]
6 16 ms 19 ms 19 ms 72-31-188-176.net.bhntampa.com [72.31.188.176]
7 20 ms 21 ms 24 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
8 24 ms 31 ms 27 ms 66.109.5.131
9 34 ms 29 ms 29 ms ix-ae-48-0.tcore1.mln-miami.as6453.net [66.110.9.246]
10 22 ms 26 ms 21 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
11 104 ms 101 ms 104 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
12 41 ms 34 ms 36 ms ae-6.r20.miamfl02.us.bb.gin.ntt.net [129.250.3.141]
13 47 ms 54 ms 49 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
14 168 ms 106 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 106 ms 109 ms 109 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 115 ms 106 ms 109 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 126 ms 111 ms 106 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 112 ms 109 ms 109 ms 204.2.229.234
19 112 ms 109 ms 104 ms 204.2.229.10
Trace complete.
C:\Users\Seyon>tracert 204.2.229.10
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 3 ms 1 ms 4 ms 192.168.0.1
2 12 ms 16 ms 12 ms 10.104.240.1
3 13 ms 29 ms 24 ms ten-0-5-1-5.orld26-ser2.bhn.net [72.31.216.240]
4 25 ms 19 ms 32 ms bundle-ether26.orld31-car2.bhn.net [72.31.195.62]
5 24 ms 19 ms 19 ms 72-31-220-138.net.bhntampa.com [72.31.220.138]
6 25 ms 19 ms 19 ms 72-31-188-176.net.bhntampa.com [72.31.188.176]
7 24 ms 23 ms 24 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
8 25 ms 26 ms 26 ms 66.109.5.131
9 27 ms 29 ms 34 ms ix-ae-48-0.tcore1.mln-miami.as6453.net [66.110.9.246]
10 85 ms 34 ms 29 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
11 99 ms 106 ms 99 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
12 31 ms 37 ms 31 ms ae-6.r20.miamfl02.us.bb.gin.ntt.net [129.250.3.141]
13 48 ms 48 ms 58 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
14 105 ms 106 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 205 ms 109 ms 109 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 116 ms 109 ms 104 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 106 ms 109 ms 109 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 176 ms 119 ms 106 ms 204.2.229.234
19 112 ms 109 ms 112 ms 204.2.229.10
Trace complete.
C:\Users\Seyon>tracert 204.2.229.10
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.0.1
2 11 ms 12 ms 10 ms 10.104.240.1
3 24 ms 15 ms 12 ms ten-0-5-1-5.orld26-ser2.bhn.net [72.31.216.240]
4 16 ms 23 ms 20 ms bundle-ether26.orld31-car2.bhn.net [72.31.195.62]
5 18 ms 27 ms 15 ms 72-31-220-138.net.bhntampa.com [72.31.220.138]
6 22 ms 19 ms 19 ms 72-31-188-176.net.bhntampa.com [72.31.188.176]
7 22 ms 34 ms 19 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
8 26 ms 34 ms 27 ms 66.109.5.131
9 35 ms 26 ms 29 ms ix-ae-48-0.tcore1.mln-miami.as6453.net [66.110.9.246]
10 21 ms 24 ms 34 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
11 102 ms 104 ms 102 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
12 49 ms 36 ms 49 ms ae-6.r20.miamfl02.us.bb.gin.ntt.net [129.250.3.141]
13 46 ms 49 ms 52 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
14 121 ms 107 ms 106 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 114 ms 109 ms 109 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 105 ms 110 ms 112 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 112 ms 109 ms 109 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 110 ms 114 ms * 204.2.229.234
19 107 ms 109 ms 112 ms 204.2.229.10
Trace complete.
90002 errors constantly
Printable View
-
07-25-2019, 09:53 AMxyaie90002 errors constantly
-
07-26-2019, 08:35 AMEinmimiria
Good afternoon and thank you for posting on the Final Fantasy XIV Technical Support Forums.
According to your trace route, it looks like you are running into some instability along the way to the server. Unfortunately, it's difficult to tell exactly what is causing this. However, if you have tried the other troubleshooting, the issue may stem from outside of your home network. In this case, I'd recommend contacting your ISP and making a report with them.
We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV! -
07-26-2019, 12:39 PMxyaieThank you for your response. I contacted them and they did not have an idea what is causing my problem. Are you able to see anything specific I can bring up to them? I see where it jumps up into the hundreds, however I dont see any errors or drops like I saw on other people's trace routes. If there is an identifiable spot that is causing the problem possibly I can use a VPN to route around it?Quote:
Originally Posted by Einmimiria
-
07-27-2019, 08:22 AMEinmimiria
Thank you for the reply xyaie.
By instability, I was referring to the return times on your trace route. There are some that vary greatly (some go from 100ms to 160ms then back to 100ms, for example). Any place you see an asterisk (*) indicates a packet that didn't return at all. There are a few of these in your trace route.
Unfortunately, It's difficult to determine exactly where the issue is since this instability can happen anywhere between your PC and the node you are trace routing.
Other players have found success using a VPN because it take you along a different route. However, this isn't a guaranteed outcome.
Thank you for visiting the Final Fantasy XIV Technical Support Forums.