Heads up! Someone using the name AO3_Status_ (note the second underscore) is impersonating this account and attempting to scam AO3 users out of money. Please block and report this account. (And please note that the real donation form is currently down due to a DDoS.)
We've temporarily disabled the ability to request a new account invitation as a preventative measure due to a spam attack. Apologies for the inconvenience! We'll let you know when it's back.
We're still working to mitigate the DDoS attacks. In the meantime, you may receive various error messages or encounter display issues with the site layout.
The Archive recorded 68.6 million page views on Sunday, which is a new weekend high. 🥳 448 million page views for the whole week, which is 150 million more than the same time last year. (Are you all okay?)
We're trying a new approach to defend against the ongoing DDoS attack, so you may see error messages that say "429" instead of "Retry later." (429 is the error code for too many requests.)
We do not condone anti-Muslim sentiments under any circumstances. Additionally, to reiterate: cybersecurity experts believe the group claiming responsibility is lying about their affiliation and reasons for attacking websites. View the group's statements with skepticism.
A group presenting themselves as a collective of religiously and politically motivated hackers has claimed responsibility for the attack. Experts do not believe they are honest about their motivation, so we urge caution in believing any reasoning they provide for targeting AO3.
Very sorry we can't give you your fanwork fix right now, or a time estimate for when AO3 will be back. Welcome to all our new followers, and sorry we had to meet like this. 😬 Please stick around for the happier updates! 🌸
It looks like the Archive is under a DDoS attack causing the servers to fall over. Our volunteer sysadmins are working on countermeasures. Please be patient with us, we'll be back!
We apologize for any distress caused, and we'll do our best to be back soon! As we're running on volunteer power, we can't always act on server hiccups as quickly as we'd like. Thank you for your patience! 🫶
We're pleased to announce that, in the coming days, we'll be rolling out the first part of our blocking and muting features: the ability to block specific logged-in users from commenting on your works and replying to your comments.
Due to an influx of abusive spam comments, we've temporarily turned off the ability to leave comments while logged out. We apologize for the inconvenience, and hope to have guest comments back on soon!
A DDOS attack is when an attacker attempts to knock a site offline by overwhelming it with requests:
Data is not compromised in a DDOS attack, so there is no need to change your password at this time.
As part of our efforts to help keep the site up, you might find that you get "Retry later" errors more often when searching or filtering works or bookmarks. Don't worry, just go a little slower, or try again in a few minutes! These are temporary measures.
This is a periodic friendly reminder that AO3 does not have an app and is always free to use!
If you run into issues with an unofficial app, our Support team unfortunately cannot help -- please contact the app's creator or support team instead.
We're really sorry this happened just as everyone was getting to the good part. 😔 It might be another couple of hours until all the servers are back in business, so please continue not to panic, and thank you for your words of support so far!
To complement our blocking feature (which prevents users from commenting on your works), we'll be rolling out a new muting tool, which hides content by users you specify. 🤐
Check out all the details:
The Archive is slipping into something a little more comfortable (maintenance mode) to let the stressed servers relax for a bit. It might take a few hours until they're ready for company again. Very sorry!
Doing the gentlest possible thing to help out our database server: taking the Archive down for a bit. No need to panic, we'll be back as soon as we can!
We're working to keep things running as smoothly as possible, but our databases are currently struggling to synchronize. This process is disrupted every time subscription emails go out, so you can expect brief periods of slowness or downtime once an hour for the time being.
We have also temporarily disabled the Policy Questions & Abuse Reports page due to this spam attack -- again, our apologies for the inconvenience, and for the alarming error message it currently displays!
Still poking around and waiting for more sysadmins to be awake at this time. Thank you for hanging in there! (Please rest assured that no particular work update broke the site, although we agree that *would* be hilarious.)
While we're in maintenance mode, the Archive will be inaccessible. Unfortunately, we can't say exactly when we'll be back, but are guessing at least 3-4 hours. Please bear with us!
We're pleased to announce that, in the coming days, we'll be rolling out the first part of our blocking and muting features: the ability to block specific logged-in users from commenting on your works and replying to your comments.
We're aware of ongoing issues such as Cloudflare error pages and intermittent slowness and downtime. We're working to mitigate these problems -- thank you for your patience!
Now back online: the ability to request an invite, the support form, and the abuse report form.
We will continue to closely monitor the situation and will let you know about any other temporary measures we might take.
To complement our blocking feature (which prevents users from commenting on your works), we'll be rolling out a new muting tool, which hides content by users you specify. 🤐
Check out all the details:
We're back for now, but still working on getting all servers back on track. There might be more downtime later, so download your current reading material if you can. Thank you so much for your patience!
We had to restart a database, so the site will continue to be slow or non-responsive as it recovers. Please be gentle with the Archive, and stand by for further updates.
And we're back! 🥳 Everyone give our volunteer sysadmin james_ some love and then:
Happy reading! Goodnight! Sorry about capitalism and/or schoolwork! Have a nice lunch break! 🫶
If you get a comment on your work about looking like it was generated by AI, please mark as spam! No need to report it to us. You can also turn off guest comments on your work. AO3 admins will never communicate with you by guest comments.
Sincere apologies, we're still not sure what's happening and will need to wait a little longer for reinforcements. If it's close to your bedtime, the Archive will be back in the morning! 🛌🌝✨ Otherwise, carry on in the replies and be kind to each other. 🌻
The Archive is back! We're currently running on 2 database servers instead of our usual 3, so things may continue to be a bit slow. We'll keep you updated on progress!
If your history isn't updating, don't despair! We have a fix in the works, but it may be a few days before it's ready. If all goes well, no data will be lost.
Delayed emails have been sent out and the Archive is back! Thank you so much to our sysadmin james_ for interrupting his sleep to work on and monitor the situation.
Around 5am UTC (midnight on the US East Coast) enough people paused their fanwork consumption, however briefly, to cause a dent in our traffic graph. 🎊🍀🥂
Happy new year to all of you, and thank you for all your support! ❤️
🚨 We'll be rolling out a code change that limits the total number of tags on a work. Once this change is in effect, you can't post a new work with more than 75 tags. Editing an older work that goes over the limit will require you to remove some.
Details:
You might notice some inaccuracies when sorting and searching by number of bookmarks, comments, or kudos. We'll let you know when this is fixed -- should be later this week!
It was a gnarly little project, but good news! Histories should be updating as usual, and so should work bookmark, comment, and kudos counts. Thanks for bearing with us!
AO3 is seeing a dramatic increase in traffic due to current events. 📈 We're taking immediate measures to make sure the Archive stays online, but there will be changes to logged out users' experience and to the way hits are counted. Details:
Today we come to you with fun facts rather than downtime notice! The Archive database is currently 693GB in size, and the total word count for AO3's nearly 5 million works is 32,056,015,255.
PDFs look a little different now as the result of a security change! 📔 New fonts and different page break placement as well as increased file sizes are the most notable changes.
Spam in your comments? First: don't follow the link! But do use the "Spam" button on the comment to report it. (No need to send in a separate support or abuse report! And please don't mark it as spam in your email, or your provider might start thinking all AO3 emails are spam.)
Work is ongoing. Maybe if you're thinking you should be asleep right now, take it as a gentle reminder from the AO3 to go to sleep. ❤️ Otherwise, sorry for the inconvenience!
Downtime starts in a few minutes, a little later than planned. It'll be brief, so no need to panic (about this particular issue, anyway). We'll let you know when we're done! :wrench:
We've restarted things and the Archive seems to be loading again! 🎉 But please be gentle; we're still looking into the cause and aren't yet confident the site will remain up.