got dc (error 9000) then errors 2002/6001/5006 trying to reconnect to the Aether data center. Tracert shows there is an issue with on of level 3's routers in Montreal. SE needs to get this escalated through their NOC, but we can report this to our ISP's also.

try running this test and past your results to help SE get this taken care of

to run this test on windows
1. open your start menu
2 in the search box type "CMD"
3. open the command prompt
4. in the command window type "tracert x.x.x.x" where x.x.x.x is your server's ip address

Servers and address on the Aether data center:
Adamantoise: 199.91.189.30
Balmung: 199.91.189.30
Cactuar: 199.91.189.23
Coeurl: 199.91.189.27
Faerie: 199.91.189.30
Gilgamesh: 199.91.189.57
Goblin: 199.91.189.26
Mateus: 199.91.189.22
Sargatanas: 199.91.189.33
Siren: 199.91.189.29
Zalera: 199.91.189.57

Here's part of a bad trace:
9 87 ms 87 ms 85 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
10 80 ms 76 ms 74 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]
11 * * * Request timed out.
12 80 ms 81 ms 78 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 * 93 ms 121 ms 192.34.76.10


and here's part of a good trace:
9 * * 82 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
10 76 ms 79 ms 74 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]
11 73 ms 74 ms 77 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
12 102 ms 88 ms 84 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 86 ms 96 ms 91 ms 192.34.76.10

Due to the dynamic nature of routing, it may take multiple attempts to get the bad result to show.