If you are having 90002/90001/Disconnects please REPLY HERE!

To confirm the observations of many others, this seems to have a strong routing component.

I have been plagued by the 90006 error since around release.

Today I decided to do a little error tracking, so I ran two game clients simultaneously and set up repeated pings to two different sites, a Norwegian newspaper and 204.2.229.9 which I am given to understand is the entry IP for Aether datacenter.



Results as follow:


Ping statistics for 195.88.54.16:
Packets: Sent = 19131, Received = 19131, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 30ms, Average = 8ms


Ping statistics for 204.2.229.9:
Packets: Sent = 14811, Received = 14801, Lost = 10 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 230ms, Average = 179ms


Both game clients got 90006'ed at the same time, which is, stating the obvious, when all 10 packets were lost.



Reply from 204.2.229.9: bytes=32 time=230ms TTL=48
Request timed out.
Reply from 204.2.229.9: bytes=32 time=230ms TTL=48
Request timed out.
Reply from 204.2.229.9: bytes=32 time=230ms TTL=48
Reply from 204.2.229.9: bytes=32 time=230ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 204.2.229.9: bytes=32 time=230ms TTL=48
Reply from 204.2.229.9: bytes=32 time=230ms TTL=48




I have tried using a VPN client to circumvent NTT, since others have suggested one of their nodes might be the issue, but all the egress points I tested thus far met NTT on the last stretch, so I am assuming they have the last stretch towards the datacentre SE is in :/

After getting multiple 90006 disconnects over the past week and getting dumped back to a queue of 3000+, I have cancelled my subscription. I am sick of this crap. Maybe after SE finally gets around to fixing their network and get their ridiculous queues under control, I'll come back. Don't know. Don't care. I have better things to do than sit in a queue for hours on end.

I've had more 90006 errors than I could count.

Literally Tired of this - Please don't make me go back to playing another mmo =(

I'm having this issue too, Checked my router, and checked with the ISP, and checked with pingplotter, winmtr etc and nothing is showing any issues from my end to the server anyways and i'm getting the error 90006

getting 90k non-stop for the last 72h,decided to run PingPlotter on the servers themselves and the Primal Data Center and here's what I've got:

https://imgur.com/a/IwMoffs

all Ip addresses with packet loss are related to NTT/NTT America so yeah not my router and not my isp...

Honestly wondering what's wrong with 204.2.229.230

Guess what time it is. It's NTT is a terrible provider time. Had 4 of 8 FC members on drop or experience crazy lag at the same time. Decided to run a test again because maybe someday they will actually look into it.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Redacted for privacy - 0 | 61 | 61 | 0 | 1 | 8 | 1 |
| Redacted for Privacy - 0 | 60 | 60 | 8 | 13 | 22 | 13 |
| Redacted for Privacy - 0 | 60 | 60 | 9 | 14 | 22 | 19 |
| thyrmo-core1-bnd11.fidnet.com - 0 | 61 | 61 | 10 | 14 | 35 | 13 |
| wplnmo-core1-bnd10.fidnet.com - 0 | 61 | 61 | 10 | 15 | 27 | 15 |
| salmmo-core1-bnd4.fidnet.com - 0 | 61 | 61 | 12 | 18 | 26 | 24 |
| sllvmo-lcore2-bnd10.fidnet.com - 0 | 61 | 61 | 13 | 18 | 45 | 23 |
| 216-229-73-159.fidnet.com - 0 | 60 | 60 | 14 | 21 | 32 | 20 |
| 216-229-74-116.fidnet.com - 0 | 60 | 60 | 14 | 20 | 31 | 19 |
| 216-229-73-111.fidnet.com - 0 | 61 | 61 | 15 | 20 | 37 | 17 |
| stl-asr9010-bnd15.fidnet.com - 0 | 60 | 60 | 16 | 22 | 32 | 20 |
| 67-60-16-121.cpe.sparklight.net - 0 | 60 | 60 | 28 | 32 | 38 | 30 |
| 10.224.253.233 - 0 | 61 | 61 | 35 | 39 | 53 | 37 |
| chi-b23-link.ip.twelve99.net - 0 | 60 | 60 | 28 | 34 | 52 | 33 |
| ae-25.r08.chcgil09.us.bb.gin.ntt.net - 0 | 60 | 60 | 28 | 32 | 42 | 33 |
| ae-4.r23.chcgil09.us.bb.gin.ntt.net - 0 | 61 | 61 | 28 | 37 | 71 | 41 |
| ae-1.r24.snjsca04.us.bb.gin.ntt.net - 53 | 21 | 10 | 0 | 106 | 138 | 87 |
| ae-4.r00.scrmca02.us.bb.gin.ntt.net - 46 | 22 | 12 | 85 | 112 | 147 | 85 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 46 | 22 | 12 | 0 | 107 | 145 | 96 |
| 204.2.229.230 - 86 | 14 | 2 | 0 | 116 | 135 | 97 |
| 204.2.229.9 - 46 | 22 | 12 | 86 | 102 | 145 | 95 |

Quote:

---

Originally Posted by DarkDepravity

I have tried using a VPN client to circumvent NTT, since others have suggested one of their nodes might be the issue, but all the egress points I tested thus far met NTT on the last stretch, so I am assuming they have the last stretch towards the datacentre SE is in :/

---

NTT is their upstream provider. You might be able to avoid a node or two. Perhaps finding a tunnel in L.A or Sacremento might get past the big failure which is the San Jose jump. The real screwed up thing is in their letter yesterday they legit said they have no good examples of this error "Reported Occurrences of Error 90002/90006 During Cutscenes" "but there is not much information and we haven't found any problems so far.". Which is complete B.S. because they do have examples. NTT via consumer contact even acknowledged that they saw issues with the device in question but that their customer (SE) needed to contact them.

Can we please get a response? The disconnections have been unbearable this morning.

So not even being connected to FFXIV for 3 minutes, people were warping around and I DC'd. After three, minutes. So I decided to download Pingplotter like everyone had suggested.

https://media.discordapp.net/attachm...75/unknown.png