@status.archiveofourown.org
Site status updates for the Archive of Our Own, a Hugo Award-winning project of the Organization for Transformative Works (@transformativeworks.org)
@status.archiveofourown.org#AO3's July releases included the big switch to 1.0, filters for user Collections pages, and a fix for a bug that caused blank word counts! Find out more about those and other changes in our latest release notes post: ao3-news.org/v-1-4-0
@status.archiveofourown.orgThe planned #AO3 maintenance for August 21 has been canceled. It will be rescheduled for a later date.
@status.archiveofourown.org[update] Scheduled: #AO3 will be down for about 2 hours starting at 08:00 UTC on August 21.
@status.archiveofourown.orgIn June and early July, we updated the #AO3 Terms of Service FAQ and made improvements all around prompt memes and gift exchanges. We also improved skin previews and the AO3 admin area, along with a few other small fixes. Learn more at ao3.org/admin_posts/35936
@status.archiveofourown.orgIn May, updates to #AO3 focused on improving skins, collections, and gift exchanges, boosting performance across #AO3, and addressing several security issues. Read more at: ao3-news.org/v-0-9-481
@status.archiveofourown.orgWe have temporarily lifted the block preventing users from logging in to #AO3 with an insecure password. If you have been receiving the above message, please refer to our Tumblr post for information on what to do next: ao3-news.org/yu353wkr
@status.archiveofourown.orgIf you are receiving a warning that your #AO3 password has appeared in a data breach from another site and is no longer secure, you will need to change your password before you can log back in. Read more on our Tumblr: ao3-news.org/bdzc9e3b
@status.archiveofourown.org#AO3 has recently seen a wave of phishing comments claiming to be made by "AO3 Trust & Safety" notifying you that your account has been restricted. These claims are not true. Do not click on links in these comments or pay for verification. Read more at otw-news.org/5n972k6a
@status.archiveofourown.orgIn April, we deployed improvements to tag search and several security fixes. We also made some progress on making more parts of #AO3 translatable. And of course, AO3 officially exited open beta in April as well! Read more at: ao3-news.org/v-0-9-473
@status.archiveofourown.org#AO3's March code releases included a slew of collection, bookmark, and history bug fixes, as well as several improvements for site admins. Read more at ao3-news.org/v-0-9-468
@status.archiveofourown.org[update] Resolved: We have resolved the issue that was causing slowness. #AO3 should be back to functioning normally for all users! If you are still experiencing any issues past this point, please let us know. Thank you for your patience!
@status.archiveofourown.org[update] Monitoring: #AO3 is currently experiencing some slowness. We’ve resolved the issue and are monitoring. Some users on older devices may still encounter errors as we continue making adjustments.
@status.archiveofourown.org#AO3's February releases included new admin tools for our Support and Policy & Abuse teams, as well as a bunch of challenge and collection fixes and a host of small updates and improvements. We also upgraded to Rails 8 and Elasticsearch 9! Read more at ao3-news.org/v-0-9-461
@transformativeworks.orgReposted by @status.archiveofourown.org#AO3 is exiting open beta! Learn more about how far we've come since launching open beta, our future plans for improvement, and what you can do to contribute at otw-news.org/4w2dn3tc
@status.archiveofourown.orgTo improve account security, we now alert you if your #AO3 password matches a password known to be compromised on other sites. If you see this banner when logging in, please change your password. For more advice on protecting your account: otw-news.org/y8jnay3v
@status.archiveofourown.org#OTW Systems volunteers have published a postmortem about the issues behind the unplanned #AO3 downtime in early March. Check it out on AO3: ao3-news.org/2v2en3bf
@status.archiveofourown.org[update] Resolved: #AO3 and #Fanlore are back! Our data center says they have disabled the upstream provider that was causing the outage, but we are continuing to monitor the situation.
@status.archiveofourown.org[update] Investigating: #AO3 and #Fanlore are currently down. We are investigating.
@status.archiveofourown.org@status.archiveofourown.org[update] Resolved: The fix we applied 24 hours ago appears to be holding, so we are resolving this incident. We thank everyone for their patience!
