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 :/
