19 Photos and videos
Pinned Tweet
1 Apr 2015
We love hearing from you, but if you need help/have questions, pls use bit.ly/ao3support. Recent code changes: bit.ly/ao3releases
1,234
430
14,015
May 19
#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
57
75
2,036
199,273
May 16
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!
May 16
#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.
For more updates, please refer to our statuspage: otwstatus.org/
37
252
4,742
296,897
May 16
#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.
For more updates, please refer to our statuspage: otwstatus.org/
72
416
7,657
526,281
Apr 11
#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
105
75
2,023
347,393
AO3 Status retweeted
#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
ALT AO3 Update
281
4,364
43,584
4,356,485
Mar 25
To 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
ALT Successful login banner on the Change Password page with an error message below it, reading 'Your password has appeared in a data breach from another site and is no longer secure. For your protection, please select a new, unique password.'
93
2,390
28,221
606,206
Mar 22
#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
44
263
4,946
446,463
Mar 17
#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.
Mar 17
#AO3 and #Fanlore are currently down. We are investigating. Please refer to our status page for more information: otwstatus.org/incidents/sbgg…
88
560
8,405
359,606
Mar 17
#AO3 and #Fanlore are currently down. We are investigating. Please refer to our status page for more information: otwstatus.org/incidents/sbgg…
536
1,150
15,313
1,847,317
Mar 16
In January, #AO3 made major improvements to our bookmark search, making it possible to sort and filter bookmarks by word count, and deployed several batches of fixes to strengthen site security and improve performance. Read more at ao3-news.org/v-0-9-456
236
656
17,522
416,116
Mar 4
The fix we applied 24 hours ago appears to be holding, so we are resolving this incident. We thank everyone for their patience!
For future status updates, please refer to otwstatus.org
509
2,846
62,486
726,492
Mar 3
We have made some adjustments based on recommendations from our database vendor and will continue to monitor their impact on system stability.
For updates, please refer to otwstatus.org
272
1,331
32,396
807,225
Mar 3
If you choose to post or update your works while AO3 is up, we strongly recommend making sure you have a backup of any text you are attempting to post.
For updates, please refer to otwstatus.org (2/2)
Mar 3
Following guidance from our vendor, we've brought #AO3 back online to help troubleshoot. We expect the site will go back down, although we don't know when that will happen. (1/2)
174
1,587
23,148
1,285,308
Mar 3
Following guidance from our vendor, we've brought #AO3 back online to help troubleshoot. We expect the site will go back down, although we don't know when that will happen. (1/2)
Mar 3
We do not currently have an estimated time for when we will be back up, but we expect it to be multiple hours at minimum. We apologize for the inconvenience and will update you when we know more. Refer to otwstatus.org for updates. (3/3)
295
2,496
36,649
3,094,013
Mar 3
We do not currently have an estimated time for when we will be back up, but we expect it to be multiple hours at minimum. We apologize for the inconvenience and will update you when we know more. Refer to otwstatus.org for updates. (3/3)
Mar 3
We're working with our vendor's support team to understand the cause and whether reverting or upgrading further will best resolve the issue without continuing the cycle of up and downtimes. (2/3)
1,312
3,001
44,962
4,115,962
Mar 3
We're working with our vendor's support team to understand the cause and whether reverting or upgrading further will best resolve the issue without continuing the cycle of up and downtimes. (2/3)
Mar 3
#AO3 is now fully down. After performing a software upgrade a few days ago, we've been unable to keep our server cluster healthy due to what we believe is a bug or issue with the new release of our database server software. (1/3)
88
956
20,987
2,096,770
Mar 3
#AO3 is now fully down. After performing a software upgrade a few days ago, we've been unable to keep our server cluster healthy due to what we believe is a bug or issue with the new release of our database server software. (1/3)
Mar 2
We are investigating reports of errors when trying to load AO3, including errors saying that AO3 is down, which seem to be related to the previous incident. We will update when we have more information!
2,389
11,869
174,186
10,292,010
Mar 2
We are investigating reports of errors when trying to load AO3, including errors saying that AO3 is down, which seem to be related to the previous incident. We will update when we have more information!
2,410
3,128
66,935
13,155,726
Mar 2
We have resolved the underlying issue, and #AO3 should be behaving as normal for all users again. Thank you for your patience!
Mar 2
#AO3 will remain down for at least several hours until we can consult our database vendor's support team and resolve the underlying issue. We're very sorry for the inconvenience.
Please refer to otwstatus.org for updates.
697
3,363
52,843
1,551,443
Mar 2
#AO3 will remain down for at least several hours until we can consult our database vendor's support team and resolve the underlying issue. We're very sorry for the inconvenience.
Please refer to otwstatus.org for updates.
2,503
5,278
77,212
6,448,698