Posted by (@AO3_Status)
Getting Error 500 when posting a work to a series? Check that your work has all required elements including Fandom and Warning.
We are in no way affiliated with @Photobucket -- this is a change to their ToS that affected users across the web.
If you see a work with an image telling you to upgrade your account, that's @Photobucket, not us!
Things appear to have settled and we're back!
We're experiencing some issues and are looking into the cause of our downtime.
The Archive is now running on Rails 4.2, with further upgrades in the works. Issues in the previous deploy have been resolved as well.
And we're back! Keeping an eye on the servers, just in case.
The Archive will be down for our code deploy for about 15 minutes, starting now. We'll let you know when we're back!
Starting at 9:00 UTC (~1 hour from now), #AO3 will be down for 15 minutes while we deploy a new & improved version of our Rails 4.2 upgrade.
Done reverting! Expect some slowness & errors while the servers warm up.
We will investigate the earlier editing problems in the meantime!
We have to revert the Rails upgrade. :( There will be 15 minutes of downtime in about 30 minutes.
We're aware of issues with editing a work/chapter. New works/chapters not affected. Please hold off on editing while we investigate!
Getting reports of Error 500 pages showing up where they shouldn't. Apologies! We're looking into it now.
#AO3 is out of maintenance and running on Rails 4.2!
The Archive is down while we take a third (and hopefully last!) shot at deploying. We're aiming to be back in 10 minutes.
We'll be going into maintenance mode in 30mins, but we now expect the downtime to last only about 10mins.
At 10:00 UTC (about 2hrs 15mins from now) we'll go into maintenance mode for about one hour to make sure the deploy goes smoothly.
We've run into another similar caching issue (it's always caching!) and will have to deploy later. We'll let you know when we start!
We've resolved the issue with our earlier deploy attempt more quickly than anticipated and are about to deploy!
The 502s are over, but we've changed plans -- we expect to deploy Rails 4.2 on Monday. Will keep you posted!