Error 9002 and constant connectivity issues with NA Data Centre

[Shizzle]

For the past 4 days have been experiencing poor connectivity with the NA data servers making playing unplayable disconnects every 2minutes in raid/dungeon and while out crafting in the world and latency showing as more than 2K and error 90002's. Now while I may suspect it could be a issue from my ISP's end due to extremely poor weather from flooding over weekend I am able to watch Netflix and the like without issues it seems to connecting to NA data servers that is causing grief.

Name of ISP : Optus Australia
Ref number from ISP - TBA on hold with my ISP for past 20minutes
State/Country : NSW/ Australia
Date/time when issue started : 3/6/2016 2100hrs AEST - 1100hrs GMT
Frequency: Constantly for past 4days upon login
Content played during the issues: Raids/Roulettes open world combat and crafting
Aether Data centre/ Server Faerie

Ping and tracert attached

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\***\****>ping 199.91.189.30

Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=665ms TTL=48
Reply from 199.91.189.30: bytes=32 time=279ms TTL=48
Reply from 199.91.189.30: bytes=32 time=283ms TTL=48
Reply from 199.91.189.30: bytes=32 time=285ms TTL=48

Ping statistics for 199.91.189.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 279ms, Maximum = 665ms, Average = 378ms

C:\***\*****>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 16 ms 16 ms 16 ms bla2.bng.optusnet.com.au [198.142.65.146]
3 * * * Request timed out.
4 16 ms 15 ms 59 ms 198.142.250.169
5 16 ms 15 ms 15 ms 198.142.139.112
6 15 ms 16 ms 15 ms 198.142.139.128
7 168 ms 180 ms 212 ms 203.208.174.149
8 201 ms 191 ms 220 ms 203.208.149.250
9 177 ms 199 ms 208 ms 203.208.149.254
10 217 ms 215 ms 217 ms 203.208.183.38
11 298 ms 308 ms 287 ms if-ae-8-2.tcore2.DT8-Dallas.as6453.net [66.110.57.81]
12 404 ms 292 ms 291 ms if-ae-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
13 291 ms 290 ms 292 ms if-ae-23-2.tcore2.CT8-Chicago.as6453.net [64.86.79.120]
14 291 ms 292 ms 292 ms if-ae-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
15 293 ms 294 ms 298 ms 66.198.96.50
16 288 ms 281 ms 282 ms 192.34.76.2
17 269 ms 268 ms 276 ms 199.91.189.234
18 * 285 ms 282 ms 199.91.189.30

Trace complete.

I'm usually averaging a ping of a constant 150ms to 250 ms usually when the connection is fine.

[VraeliaValkyria]

Been getting the same. So much freaking lag lately. And so many 90ks. This lag needs to be fixed. ; ;

Leviathan server. Primal data center. NA.

[Draconis21]

I have also been getting this problem. Can't stay connected for even 30secs. I am Central Queensland, Australia.

Coeurl server, Aether data center, NA

I am with EscapeNet. Not sure if they use optus or telstra. Course its my friends account and he hasn't been playing for a while.

[luckei]

The same has been happening to me for the last three days (working fine before that). Also in NSW, Australia with Optus. I thought it might be the weather as well, but my ping is fine and I've not had issues playing Overwatch or streaming, etc.

Sometimes I can sit in the goblet and craft fine, or practice on striking dummies fine and it only lags for around five seconds every 5-10mins or so. But other times I get a 90002 error within a few minutes. I always have an issue with dungeons/instances though.

Since 4th of June I've been disconnected 100% from every instance within a few minutes of getting in (sometimes instantly). The odd thing is when I ping, it shows a stable 235~275 (which is usual) even while I'm in the middle of being disconnected and frozen in game (not so usual). There might be one or two packets lost out of fifty, but with how I'm disconnecting it really should be higher than that?

Aether data centre, Balmung.

[Setharius]

Hey guys,
Qld Townsville here with Optus also. I've spent all day working this out and arguing with Optus. What I can tell you is that the issue isn't with SE, it's entirely with Optus. I used a program called pingplotter to watch the connection from australia to NA FF14 servers. The issue is this, turns out, Optus uses their own interconnect to North America via Singapore. The packet loss fluctuates between 0% and 20% (from what I've seen) from 203.208.183.38 (owned by singtel) to 66.110.57.81 (and consquently subsequent hops that follow after until the destination). Now here's the problem for all of us Optus customers. This is part of Optus's infrastructure, for some reason they think it's a great idea to route our data through singapore first then to america instead of routing it from sydney to america. They claim there is nothing they can do about it but also don't believe it warrants having the contract cancelled. TIO has stated that there is a possibility they are right based on the grounds that it's an infrastructure problem in singapore. I've submitted my complaint and they have 10 days to respond, so I'll keep things posted if anything changes. But yeah...

TLDR: Optus's shitty infrastructure is the blame, not SE

[Saraphin]

I don't know about that, i'm in the US on an NA server and i was getting massive lag spikes for no apparent reason. Two days ago, i couldn't go 3-4 steps in game without disconnecting. i checked my ping and everything, not that i saved it, stupid me, but the last few days have been very laggy. a bunch of us were in Limsa and all of a sudden Red Pokeballs of disconnect everywhere for all but like 3-4 people.

I could guess some of your issues may be related to Optus, but...i honestly am not sure if that's fully the reason. many people in the South East part of the US have been having this problem.

[SionicMatrix]

I'm with Optus as well here in Melbourne and I've been getting the same errors. Can confirm that the problems started around the same time as OP's. I'd log in and everything would be fine for 30 seconds, then everything freezes and 90002 happens. Really hope this problem is fixed sometime soon ;;
Behemoth - Primal Data Centre

[Melona]

NSW, also with Optus and having the same problems, on Coeurl/Aether. The game is pretty much unplayable as it is. Different error code as of today though; now I'm getting 90006's.
Really hope this gets fixed soon! Was looking forward to playing the new patch.

[TKNItachi]

Country: Singapore
Internet service provider: myrepublic
Server: primal/Excalibur
Problem: while I was able to download 3.3 with no issue, I keep getting disconnected after about 30 seconds with massive latency as well. 90006 error keeps appearing at the point of disconnect. Please help! Really want to play 3.3. Thanks

[Valenaria]

Brisbane, Queensland
Optus

Behemoth, Balmung, Cactaur

I have had issues for the last week so severe that as I sit here tonight after downloading the patch, I can not even stay connected long enough for my bars to populate, let alone move. I did put a ticket in with Support earlier this week, and that was by sheer luck, as it would disconnect me before I could write out more than the bare minimum.

I have had rubber banding so badly in dungeons, it threw me out several times during them and I was lucky to complete, until yesterday when nothing could be done at all. People in the dungeons were reporting the same issues, lag spikes, and they were in different countries... notably, US and Australia.

This issue happens often before a patch for me, though never this bad, so I thought it would clear after the 3.3 patch. This time, it has become completely unplayable after the patch.

Yesterday, I was receiving the versioning errors in the 20000's, also 90002 and 90006 errors, and for the first time ever an authentication error, being thrown to lobby and often desktop. I use the token. Today, the errors have changed to consistent 90006 errors.

I have tried all the suggested things from the forums, save re installing. I did play Guild Wars 2 last evening with no problems at all, and I play a North American Server there.

Thank you for any light you can shed on this problem. There is naught I can do at this point but wait and hope.