// Contents

At 07:13 UTC on October 29, 2026, Archive of Our Own went dark. AO3 is the largest nonprofit fanfiction library online, with more than 18.4 million works. Fanfiction is what fans write about characters from someone else’s book, film or show, and the archive spans more than 82,900 fandoms. That night the archive’s operators disclosed a security incident and said the site would be back in two to four weeks.

Readers had nothing to read, and writers couldn’t reach their own work. On Sunday, November 1, a replacement turned up. A site called ao3.life promised to keep the archive “saved before it can slip away.” Its creator says he is a 17-year-old in India and that a swarm of AI agents did the building. Deleted and private works that had long since vanished from AO3 quickly surfaced on the clone. The site lasted about a day, and no court closed it. What did was 2,000 takedown requests from writers and a poll on the site itself, which its creator had technically won: 49% of voters were happy, 47% upset.

Forty virtual machines and a paywall for audio

The creator signs himself Ganesh. According to 404 Media, he said the site was filled by “a swarm of AI Agents controlling 40 virtual machines.” The outlet called the project “vibe coded”: a person describes what they want in plain language, and an AI model writes and runs the software.

An AI agent, in this case, is a program you hand a task in plain words, something like “take these archives and turn them into a site with narration.” Then it works on its own, writing the code and laying the stories out on pages. Forty virtual machines are, roughly, 40 computers doing that work at once. Ganesh says the whole thing took him about 40 hours, from the first step to the apology.

The clone itself was simple. Any story could be downloaded free as an EPUB, the standard e-reader format. Next to it sat an audiobook in an AI-generated voice: the first three minutes were free, the rest cost money. Authors were promised 91% of the revenue, with 9% kept for “narration and processing.”

To collect their share or remove a story, writers had to email from the address tied to their AO3 profile and leave a note on that profile. With AO3 down, nobody could open their profile. Moderators of the AO3 community on Reddit warned people not to email the site at all. On social media people called it phishing, though nobody produced evidence.

// One day of ao3.life

126,592unique visitors in the first 24 hours, according to its creator
2,000+takedown requests in a single day
11audiobooks actually sold, roughly
$200the whole site cost less than this to run, Ganesh says

That’s one sale for about every 11,500 visitors. As a business, the clone had failed before anyone shut it down.

Money is a sore point in fandom anyway. Fanfiction lives in a legal gray zone, because the characters belong to someone else. So AO3 bars authors from making money on their works, even though the OTW, the nonprofit that runs the archive, maintains that writers own the copyright to their own text. People have tried selling other people’s fanfic before: in 2024, 404 Media reported on Etsy sellers who bound it into books and charged up to $100. Those sellers had to bind each book one at a time. This time, a copy of 15 million stories went up over a weekend, complete with narration and a checkout.

Where the deleted drafts came from

The first alarm came from writers who found things on the clone that had long since vanished from AO3. Kotaku reported that old versions of works turned up there, along with deleted and private stories. One writer complained on Bluesky that works they had locked away from the public still showed up on ao3.life, and that they now had “0 control” over them.

Many fans assumed the clone was linked to the AO3 breach itself. Ganesh denies it. In an apology posted on ao3.life, he writes that he has no connection to AO3 or to whoever breached it, and that the stories came from public dumps. There were two main sources: an AO3 dataset on Hugging Face and a dump of files stored by a service called FicHub. Together they held about 29 million stories, roughly 15 million of them from AO3.

What those dumps are

In April 2025, a Hugging Face user called nyuuzyou posted a set of about 12.6 million AO3 works: full texts with titles, tags and warnings. The scraper stepped through every work address from 1 to 63,200,000. Fans spotted the upload almost immediately. They and the OTW filed takedown notices under the DMCA, a US copyright law, and access to the dataset was disabled for good.

FicHub is a free service that turns a link to a fanfic into an e-reader file. It keeps copies of the files it builds, which is why people sometimes use it to dig up works their authors deleted long ago.

That explains the drafts. Deleting a story from AO3 removes it from AO3, not from the copies someone already made. The Hugging Face dataset was shut down a year and a half ago, and over one weekend its contents became a site selling audiobooks. Ganesh admits the haul included drafts he didn’t know he had collected. He doesn’t explain how drafts and private works got into those dumps.

A deleted story lives on in other people’s copies: a crumpled page in the bin, its flat twin above it
A deleted story lives on in other people’s copies: a crumpled page in the bin, its flat twin above it

Strangers weren’t the only ones copying. While the archive was dark, 404 Media reported, some readers posted Google Drive links on Reddit and Discord to works they had downloaded over the years. To them, it felt like rescuing stories they loved. Plenty of writers were as alarmed and angry about that as about the clone: their work was spreading without permission again, only this time for free.

A near tie

On Monday, November 2, an apology replaced the archive on ao3.life. Ganesh writes that he handled more than 2,000 takedown requests. The site had burned through terabytes of bandwidth in a day. He describes the audiobooks as a way to keep it online, although by his account the whole thing never cost more than $200. “It was never my intention to hurt so many authors,” he writes.

The deciding factor, he says, was a poll on his own site asking whether it made people happy. Happy: 3,184. Sad: 3,057. His note doesn’t say what happened to the remaining 4% of votes. Happy won by just 127 votes. He shut the site down anyway: if nearly half the voters were unhappy, he decided, he was doing the wrong thing.

3,184 happy votes against 3,057 sad ones: the poll that made the creator shut the clone
3,184 happy votes against 3,057 sad ones: the poll that made the creator shut the clone

Writers buried the site in emails within a day. The OTW ran into the speed of lawyers: a moderator of the Reddit community passed along its word that the organization was taking action, but that the legal system moves much more slowly than life online. The OTW later filed a URS complaint (Uniform Rapid Suspension, a fast-track process for suspending a domain that infringes a trademark). According to Ganesh, the domain will go dark within 14 days. Other clones remain, such as fanfic.party, which promises not to sell narration or train AI on the stories. AO3 itself won’t be back before mid-November: on October 30, its status page promised at least two weeks of downtime, possibly four.

Ao3.life cost less than $200 and lasted a day. The dumps it was built from existed long before it, and shutting down the Hugging Face dataset a year and a half ago didn’t make them go away. Ganesh signed his apology “a 17 year old from India that thought they were doing something good.”