Frequent 90002 Error

[Raist]

Most likely an issue at the exchanges between the ISP's that have to work together to get you to Ormuco (SE's ISP). There are known issues concerning routing in general for North America. Much of it has been at the heart of the Net Neutrality debate. Level3 and TATA have been pushing for the FCC to step up their game in the US for years now...but the ISP's just don't want to upgrade their exchanges--even when someone else has even offered to pony up the $$ for the hardware. Level3 not only offered to buy some of the $10,000 port cards for one ISP, but also to install and wire them up...and they STILL refused to upgrade.

Hard to say for certain without some tracert's to look at...but it should be pretty easy to spot if you run them (that link is to an article from Blizzard about it). Getting those reports to your ISP's Tier3 support should help get the ball rolling to clean up the routes a bit. You usually fair better going after them over the web than the phone, so if they have a support portal or twitter/facebook accounts you may get more active support there. You can check the downdetector site to see if they track your ISP--if they do, they usually have links to online support options you can try.

Alternatively, you can try using a VPN/Proxy to route yourself through different regions to see if you can get a cleaner path. Note they don't always pick the best route when they auto-configure--most will have a way for you to pick different locations for your tunnel. I found with some I tested last year that I did a bit better sometimes exiting here in the US rather than exiting in Montreal. IF you do try a VPN and it clears things up for you--you NEED to get in touch with your ISP, as that is pretty much proof positive your ISP has issues with the route(s) they are assigning you.

[NocX7]

Another patch and the problem still persists.I still get the 90002 error every 20-30 minutes.I love this game so far but no other MMO has this problem for me.

I pay for access to this game and that is getting blocked by this error happening so frequently.Can someone from SE finally say something on this matter and not just silently collect data on their 18 page sticky thread that has helped nobody so far?