AO3 outage sparks fanfiction scramble as readers rush to mirror sites and authors push back

Archive of Our Own went offline on Oct. 29 after a security incident, and the shutdown quickly turned into more than a routine platform outage. As the volunteer-run fanfiction archive faced an estimated restoration window of up to four weeks, readers began circulating saved stories through Google Drive libraries and mirror sites, while writers objected to reposts made without permission.

What happened to AO3?

Archive of Our Own, the fan work archive known as AO3, went dark on Oct. 29 after what the site described as a security incident. According to WIRED and Indiatimes, the outage forced the platform offline long enough to prompt a status update warning that restoration could take around two weeks and possibly as long as four.

Indiatimes reported that AO3 Status said no works, bookmarks or kudos were deleted. WIRED likewise said the site would remain offline for up to four weeks. For a platform hosting more than 18.8 million fan works, even a temporary blackout immediately rippled through readers, writers and fandom communities that rely on the archive as a central home for fic, meta and other fan-created work.

The core fear was not just inconvenience. In a community built around author control, attribution and trust, a security incident raises obvious questions about access, preservation and whether outside actors can use the disruption to move works elsewhere without consent.

Why the outage mattered

The outage hit a platform that many readers treat as the default fanfiction library, but which authors often see as a carefully governed archive rather than a free-for-all repository. AO3 was built in part after earlier conflicts over takedowns and censorship on older platforms such as Fanfiction.net and LiveJournal, according to the background provided in the fact sheet. That history explains why any disruption at AO3 tends to trigger a fast, emotional response.

For readers, the immediate issue was access. For authors, the bigger concern was control. WIRED reported that some writers objected when their works were reposted to mirror sites without permission. Others were worried about security risks, malware and AI scraping, which have become recurring anxieties for online writers and artists more broadly.

The situation also illustrated a familiar tension in online fandom: when a major archive goes offline, some users try to preserve access by copying material into shared drives or alternate sites. What looks like backup behavior to one group can feel like a violation to another. That divide, which surfaced sharply during this outage, is central to how fan communities manage their own norms.

How did fans respond?

Readers and preservation-minded fans moved quickly. WIRED reported that some began transferring saved stories into shared Google Drive libraries while AO3 remained inaccessible. At the same time, mirror sites and alternative archives appeared to benefit from the scramble, though that surge came with a backlash from authors who said their work was being reposted without consent.

Avery, a fanfiction writer who told WIRED she had been writing for about six years, found some of her stories on mirror sites she had never used herself. She asked two of those sites to remove her works, and they complied. Her reaction captured the split in the community: a desire to preserve stories balanced against the insistence that permission still matters, even in an outage.

“To me it’s a security risk”

That line, from Avery, summed up why some writers saw the fan-driven copy-and-share response as more than a harmless workaround. The risk, in their view, is not only that works are moved without consent. It is also that once text is spread across drives and mirrors, authors lose track of where it lives, who can access it and whether it can be used in ways they never agreed to.

There was also a practical twist: one of the more visible preservation projects, Archive Salvation, reportedly became a target itself. WIRED said the Archive Salvation Google Drive drew criticism, then was hacked and became inaccessible. A moderator later said the project offered removal requests for authors, showing how quickly a well-intentioned workaround can become a new point of failure.

What is the backlash over reposted fanfiction?

The backlash is about authorship, consent and control. Fanfiction communities often rely on informal sharing norms, but those norms do not erase the fact that many writers want to decide where their work appears and under what conditions. When stories are reposted to mirror sites without permission, authors can see it as a loss of agency rather than a form of preservation.

That concern became more urgent because the outage made users desperate for access. In that kind of environment, some fans may assume that saving a story for others is an act of goodwill. But authors who never agreed to reposting see a different reality: their text can be copied into places they did not choose, stripped of context and detached from the archive structure where they published it.

WIRED also reported that AI scraping fears were part of the conversation. For writers already worried about automated harvesting of their work, a sudden surge of mirror sites and shared drives can look less like community care and more like another route for unauthorized reuse.

What alternatives surfaced during the outage?

Several alternatives appeared or gained visibility, but not all were viewed the same way. Some were more structured than others, and that difference mattered. Squidgeworld, according to WIRED, has an operator who says it removes works posted without author permission. That policy stands in contrast to more ad hoc drive-based sharing, which can be harder to moderate.

Ellipsus also drew attention. WIRED reported that the platform saw new sign-ups rise by more than 500% after the outage began. The company says it gives authors control over access and interaction settings, and it added an export-to-AO3 button for fanfiction users. That feature suggests the platform is trying to position itself not merely as a replacement, but as a flexible companion for writers who want to move between archives without losing control of their work.

Allegra Rosenberg, an Ellipsus employee and writer, framed the appeal in terms that go directly to the heart of the outage fallout:

“We know that people want a space to not only write but share new writing, in a way that feels safe for them”

That statement helps explain why alternate platforms benefited from the disruption. The outage did not just create a problem; it also exposed demand for systems that can balance sharing with tighter author controls.

How did the community’s preservation efforts go wrong?

Some of the preservation efforts became controversies of their own. WIRED reported that the Archive Salvation Google Drive, which collected fanfic libraries, drew criticism and was later hacked, leaving it inaccessible. The project’s moderators said it offered removal requests for authors, but that reassurance did not stop the backlash.

Riley, who was associated with the cataloging effort, also faced heavy criticism. According to WIRED, Riley deleted a Google doc cataloging fanfic drives after the backlash and made their X account private. Riley also has more than 90,000 followers across X and Instagram, which helps explain why their posts attracted attention so quickly.

That sequence matters because it shows how quickly a communal workaround can become a public relations crisis. Once a list of drives is circulating, people may see it as a directory for preservation, a map to inaccessible stories or an invitation to repost. The same document can be read in incompatible ways by different parts of the fandom.

By the numbers

The outage and response can be summarized in a few key figures from the fact sheet:

Background: why AO3 matters so much

Archive of Our Own is more than a repository. It is a volunteer-run fanfiction archive built to host and share fan works in a space shaped by community expectations and author control. That makes it different from generic file storage or social platforms where written work can be copied, reposted or buried in a feed with little oversight.

The fact sheet notes that AO3 grew out of older disputes over takedowns and censorship on sites like Fanfiction.net and LiveJournal. That historical context explains why users often see AO3 as a hard-won solution to a longstanding problem: where can fandom write, archive and preserve works without constantly fearing removal?

That history also helps explain the emotional force of the current outage. If AO3 is the place that exists because earlier platforms failed writers, then a prolonged shutdown feels, to many users, like a reminder that even the best-known archive is not immune to disruption.

The story also fits a wider pattern online. AI scraping fears have made many creators more sensitive to how their work is stored and shared. In a setting like AO3, where fan works are already based on a culture of remix and transformation, the line between acceptable use and misuse can be especially contested.

What WIRED and Indiatimes reported — and where they differ

The two outlets shared the same core outline but emphasized slightly different details. WIRED focused heavily on the fan community response: mirror sites, Google Drive libraries, author objections and the rise of alternative platforms such as Ellipsus. Indiatimes highlighted the status update angle, noting that AO3 Status said restoration could take around two weeks and up to four weeks.

Both outlets agreed on the central facts: the site went dark after a security incident, no works or bookmarks were said to be deleted, and the outage prompted a wave of off-platform activity. The difference lies in emphasis. WIRED framed the event as a story about fandom norms and creator backlash. Indiatimes presented it more as a status-and-recovery update with an eye on the outage window.

That distinction is useful because it shows how the same event can be read through different lenses. One is operational. The other is cultural. In this case, the cultural lens may be the more revealing one, because the biggest argument was not just about whether AO3 would return, but about what should happen to fan works while it was gone.

What happens next?

The immediate question is whether AO3 comes back sooner than the four-week window suggested by WIRED and the status update cited by Indiatimes. The fact sheet does not identify the cause of the security incident, and it is still unclear whether any user data was exposed. That means the restoration timeline, and the technical scope of the incident, remain the main things to watch.

There are also community questions that will outlast the outage itself:

• How many mirror or drive copies of authors’ works will remain online after the archive returns?
• Will more authors issue takedown requests to third-party libraries and mirrors?
• Will alternative platforms keep the new users they gained during the outage?
• Will the backlash push fandom communities toward stricter norms around reposting and preservation?

If AO3 comes back quickly, the scramble may fade. But the arguments about authorship, access and security are likely to stay. The outage offered a stress test for fandom’s informal infrastructure, and the results were mixed: readers wanted backup access, authors wanted control, and the gap between those priorities created the backlash.

For now, the outage has revealed something that is easy to miss when AO3 is functioning normally. The archive is not just a website with millions of works. It is a social contract, and when the site went dark, that contract came under pressure from every direction at once.

Key points at a glance

• AO3 went offline on Oct. 29 after a security incident.
• AO3 Status said restoration could take around two weeks and up to four weeks.
• WIRED reported that readers moved saved stories into shared Google Drive libraries during the outage.
• Some authors objected to reposts on mirror sites without permission.
• Ellipsus said new sign-ups rose more than 500% after the outage began.

Why it matters

This is bigger than one archive going offline. AO3 sits at the center of a large, creator-driven ecosystem, so a security incident there affects how millions of fan works are accessed, copied and preserved. The outage also exposed a deeper fault line in online culture: the tension between convenience for readers and control for authors.

That tension matters for the broader web too. If communities normalize reposting during outages, creators may become less willing to share work publicly. If platforms cannot offer safer export, access and permission settings, users will keep improvising with tools that may create new problems of their own. AO3’s outage showed both the demand for preservation and the cost of handling it informally.

Open questions to watch

1. Will AO3 restore service before the outer edge of the four-week estimate?
2. Will the site explain what caused the security incident?
3. Will any user data exposure be confirmed or ruled out?
4. Will mirror sites and Google Drive libraries remain active after AO3 returns?
5. Will the surge around Ellipsus and other alternatives last beyond the outage?