Emergency Maintenance: 24 August

At the following time, we will be performing emergency maintenance. During this period, the Worlds listed below will be unavailable.

As we previously announced on the “Regarding the Instance-Related Issues (Aug. 24)” announcement, we will be conducting maintenance to address the issue wherein players are unable to access instances.

While we previously stated that we will be optimizing the servers prior to the emergency maintenance, we will require additional time to also implement counter measures to decrease the load on the servers.

While we estimate the time frame of the maintenance to be around two and a half hours, we will do our best to complete the maintenance as soon as possible.

We sincerely apologize for any inconvenience this may cause and thank you for your understanding.

[Date & Time]
Aug. 24, 2013 from 3:00 p.m. to 5:30 p.m. (PDT)

* The completion time may be subject to change.

[Affected Worlds]
North American/European Data Center Worlds
- Adamantoise
- Balmung
- Behemoth
- Cactuar
- Cerberus
- Coeurl
- Diabolos
- Excalibur
- Exodus
- Faerie
- Gilgamesh
- Goblin
- Hyperion
- Lamia
- Leviathan
- Malboro
- Midgardsormr
- Moogle
- Odin
- Phoenix
- Ragnarok
- Sargatanas
- Shiva
- Siren
- Ultros

Updated:

Hello, this is FINAL FANTASY XIV: A Realm Reborn Producer and Director, Yoshida.

Thank you for your cooperation on the multiple maintenance correspondence.

With the 2 maintenance that was implemented with the NA/EU Data Center, we have resolved the 90000 error origin and corresponding characters. For the few reports that have been sent after the maintenance, it seems like it is a separate issue, and we will be working on them individually. Thank you for your cooperation with the maintenance.

And we are also currently working on the an even better way to optimize the heavy load of simultaneous access, heavy load on matching and the matching server features for Duty Finder.

Since it is hard to implement them during peak hours and that it might make the matters worse, we are carefully deciding when to do it.

So on August 25th from 12midnight to 3:00 a.m. PDT, we will be implementing a maintenance to optimize the NA/EU Data Centers. At the same time, we will be implementing all the fixes done for the NA/EU Data Centers to the JP Data Center, so a maintenance will be done on the JP Data Centers to get a smoother optimization.

We apologize for the inconvenience that this is causing everyone, but we please ask for continued cooperation for an overall stable environment. The Development and Support Team will continue to work hard for smoother play to our customers, and we thank you for understanding and for your cooperation.

New Update for August 25th:

Emergency Maintenance has defeated me this weekend!

I have not been able to login to a NA server today  :(

I have been able to create characters and play on a Japanese server.

lol, keegan that is hilarious!

Anyway to those that are having issues logging in, I made a new character (Takahashi Subaru) and rolled on the Jap server Fenrir if anyone is looking to run. Figured this was the easiest way to actually make use of early access since I can't get on Excalibur and I've been trying all weekend =p

4 PM Update for August 25th:

Someone needs to get a real network infrastructure team on SE staff because apparently SE's current people don't have a clue what they are doing.

Hope they get all this sorted out before next weekend.  While it was irritating not being able to play this evening, I definitely got my fill this weekend and once in game it runs very well.

Nothing but 1017 errors for me. I'm destined not to play on Excalibur - not that Behemoth is doing me any favors.

Attention: Servers in NA/EU will be going offline.

We will be performing maintenance at the following date and time in order to address login issues being experienced on Worlds hosted on the North American and European datacenter.During this period, players will be unable to log in to the Worlds listed below.

We apologize for any inconvenience this may cause and thank you for your patience.

[Date & Time]
Aug. 25, 2013 from 9:00 p.m. to 10:30 p.m. (PDT)

* The completion time may be subject to change.

[Affected Worlds] - Adamantoise
- Balmung
- Behemoth
- Cactuar
- Cerberus
- Coeurl
- Diabolos
- Excalibur
- Exodus
- Faerie
- Gilgamesh
- Goblin
- Hyperion
- Lamia
- Leviathan
- Malboro
- Midgardsormr
- Moogle
- Odin
- Phoenix
- Ragnarok
- Sargatanas
- Shiva
- Siren
- Ultros

Servers back up.

New round of 1017s. Square Enix has no idea what the hell they are doing. At this rate, the game will be dead before it even starts, just like 1.0.

So 10.36 Pacific Servers back up, maintenance over and .... no change still 1017 error : /  

ETA: 12am Pacific ... I'm innnn!!!!!

1017 isn't an error, its just a code.  It means that the server queue is flagged as full and denying your connection.  Since they are intentionally limiting the amount of logins to address high server loads (by setting a lower maximum queue limit), I'm afraid that a lot of people are going to see it.

Excalibur just has too many people trying to log into it and I hate to say it, but if its a problem for folks, they may want to consider playing on another server.  That's pretty much what Square Enix is trying to force players to do.  Unfortunately, that's not an option for Legacy players, so hopefully they get front of queue preference and if not, they should.

It is a problem for anyone who like myself has tried to log in for the last 12 hours, but I am not going to roll on another server because I believe it will get sorted out, and I am in now playing anyway.

@sekker as long as we're on Excalibur,  Marrra and I are there.  I'd happily move but only together.  I hope others can make it on too :-( 

I really don't mind waiting in a queue. Repeatedly clicking into 1017 errors is not acceptable. Put us in a four hour queue if that is what it takes, but forcing users to click over and over is entirely unprofessional and should be criminal considering they are happy to take our money, yet not provide a reasonable means to play even on a crowded server. Queues and AFK timeouts are apparently something SE doesn't know how to implement appropriately.

Just to be clear, I am not suggesting or condoning any sort of server switching.  Not at all.  

They want people to move off of high pop servers and on to the lower pop servers.  These log-in frustrations (small queue resulting in World Full 1017) appear to be a part of their tactic:  Players can either choose to remain on high pop servers and deal with the "temporary" frustrations, or they can voluntarily decide to change their home server to a lower population server.

I'm just saying that it is what it is, just a matter of fact, that's all.