Connection 90000 spam.

[This_is_Seager]

I have gotten connection 90000 7x in the last hour making it impossible to play

[FriendlyUncle]

I would try to ping your server, I'm on Chaos - Moogle. My fiance and I both had this same issue around 1230AM EST. Error 90000, dropped from server and unable to connect.

Ping tests failed on boot. Tracerts all show time outs just at ORMUCO Fiber Eidos ORMUC-SE

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XXXX>ping 199.91.189.60

Pinging 199.91.189.60 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 199.91.189.60:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\XXXX>tracert 199.91.189.60

Tracing route to 199.91.189.60 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 33 ms 21 ms 28 ms 174.59.126.1
3 18 ms 15 ms 15 ms te-0-6-0-0-sur01.chambersburg.pa.pitt.comcast.ne
t [68.85.42.29]
4 18 ms 20 ms 19 ms te-0-2-0-5-ar03.lowerpaxton.pa.pitt.comcast.net
[69.139.194.49]
5 23 ms 25 ms 26 ms be-1-ar03.pittsburgh.pa.pitt.comcast.net [68.85.
75.121]
6 32 ms 35 ms 33 ms he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.94.185]
7 33 ms 33 ms 33 ms ae12.edge1.NewYork2.level3.net [4.68.127.1]
8 41 ms 40 ms 39 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 39 ms 41 ms 40 ms ae-45-45.ebr2.NewYork1.Level3.net [4.69.141.21]

10 43 ms 39 ms 39 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
11 40 ms * 40 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

12 40 ms 40 ms 39 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
13 * * * Request timed out.
14 42 ms 41 ms 42 ms 192.34.76.2
15 41 ms 41 ms 41 ms 199.91.189.234
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


It's possible its running silent and won't give me replies but I think it's no coincidence people around getting DC issues. I personally haven't been able to reconnect to Moogle since but can still reach my home server Hyperion without an issue.

[FriendlyUncle]

Suggest going to http://www.arrstatus.com/

Find your server and get the IP, do a ping and tracert on it and give the info to SE support.