AO3 fanfiction outage: ao3.life clone shut after 2,000 takedown requests

A copycat website called ao3.life, which reposted stories from the AO3 fanfiction archive while the real site was offline, went down on Monday, 2 November 2026, after authors sent more than 2,000 takedown requests in a single day, according to the site's creator. Archive of Our Own (AO3), the non-profit fanfiction library run by the Organization for Transformative Works (OTW), has itself been offline since Thursday, 29 October 2026, after what the OTW calls a security incident. The OTW expects the archive to stay down for at least two weeks and possibly up to four.

AO3 is one of the largest free libraries of fan-written fiction on the internet, with almost 19 million stories according to one technology publication. It is run by volunteers and funded by donations. When such a site goes dark, two risks appear at once: the security of the accounts behind it, and the work of its authors being copied by others while the original cannot answer.

The OTW has been careful in its wording. It has not said that data was stolen. It has said only that it does not currently believe the user database was taken, but cannot be sure. Hashed passwords are stored in scrambled form rather than as plain text, but the OTW noted that no hashing method can fully protect a weak password, or one that a user has reused on other sites. Its advice to users is to change the password on any other website where they used their AO3 password, to click only links from trusted sources, and to be wary of scam messages. The OTW also said AO3 does not collect real names, and that donor records are kept in a separate system that is not linked to the archive.

The clone episode shows how quickly an outage can be exploited. According to reports, ao3.life scraped stories from the web to fill its pages and was built with the help of AI agents running across 40 virtual machines. Authors objected that their work was being reposted and sold as audio without consent. The site's own takedown process added to the anger: it asked authors to prove ownership by writing from the email address linked to their AO3 account or by leaving a note on their AO3 profile, which nobody could do while AO3 was down. Some users warned that the process could be used to collect authors' identities.

An OTW representative also said the outage is not connected to a recently reported security flaw in PHP, a widely used web programming language, because the archive runs on a different framework, Ruby on Rails.

Peepals calculation: if the OTW's estimate of two to four weeks is counted from Thursday, 29 October, the archive would return between about Thursday, 12 November and Thursday, 26 November (29 October + 14 days = 12 November; + 28 days = 26 November). The clone's promise of 91% of audiobook profits to authors means it planned to keep 9% for itself (100% − 91% = 9%), on sales the authors never agreed to. Our calculation from the reported figures.

Short-term: AO3 readers and writers cannot reach the archive, and copy sites are reposting their work. Anyone who used their AO3 password elsewhere is advised to change it on those other sites now.

Long-term: the episode may push fan communities to keep their own backups and to ask more questions about how volunteer-run sites protect accounts. It also adds to the wider debate on AI tools being used to scrape and repackage creative work without consent.

Who is affected: AO3's registered users and readers worldwide, including Indian fans who write and read fan fiction in English, the authors whose works were copied, and the volunteers of the OTW.

What to watch next: the OTW's next update on the outage, and whether AO3 returns in a limited, read-only state, as the OTW has said it might.

Questions and Answers