AO3’s outage could last weeks
Archive of Our Own is facing a shutdown measured in weeks, not hours. The fanfiction archive, run by the Organization for Transformative Works, said restoring service could take about two weeks and as long as four. For readers who rely on AO3, that’s a major interruption: the site is both a place to discover fiction and a personal library for works people may have bookmarked or followed. The more consequential question is what the security incident exposed, and the organization says it’s still assessing that.
The outage began with a maintenance notice estimating at least 12 hours of downtime. About 12 hours later, AO3’s status account said investigators had found evidence of a security incident and would keep the site offline while they examined its scope and addressed what they had found. In a later status update, shared on Bluesky and Tumblr, the organization gave the two to four week estimate. It said AO3 might return sooner in a degraded state, though temporary shutdowns could still happen during the response.
That distinction matters. A site that comes back in a limited form may restore some reading or browsing while parts of the service remain unavailable or unstable. The update doesn’t say what those limits might be, so users shouldn’t assume that an early return would mean every feature is working or that the investigation is complete. A partial recovery would be progress, but it could also bring a less predictable experience.
That timeline is a sharp change from the initial expectation of a short maintenance window. And yet the organization has offered little detail about the incident itself. In response to CNET, an OTW representative said the downtime was caused by a security incident whose scope was still being assessed, and ruled out a connection to a PHP security issue: AO3 runs on Ruby on Rails.
The limited public detail leaves basic questions unanswered, including what systems were affected and what investigators have been able to establish. That doesn’t show that more serious damage occurred; it shows that the organization hasn’t yet said enough to settle those questions. In security responses, early statements often describe what’s known and what remains under review. Here, the clearest public information is the service impact, the recovery estimate and the organization’s current assessment of user data.
The organization says no data has been deleted. It doesn’t believe user data was compromised, but can’t rule that out, so users should change their AO3 password if they use it elsewhere. Reusing passwords is a risk that basic password guidance has long warned against. Donor information, OTW says, is held in a separate database with no connection to AO3.
That separation is a specific reassurance about donor records, while the statement about user data remains qualified. The two points shouldn’t be blurred together: OTW says donor information is stored separately, and says it can’t rule out compromise of user data. For readers, changing a reused password is a practical step that doesn’t depend on knowing the full cause of the outage. It also helps contain the consequences if that password was exposed elsewhere.
A temporary return could help readers, but it wouldn’t mean the incident is resolved. If you’re an AO3 user, the practical advice is straightforward: use a unique password, and treat the recovery estimate as uncertain while investigators continue their work. This is more significant than it looks: a long outage can disrupt access to saved reading lists and ongoing reading habits, even when the underlying works haven’t been deleted. The archive’s statement says no data has been deleted, but readers still can’t reach the site while it’s offline.
Where readers can turn
While AO3 is unavailable, Wattpad and FanFiction offer places to read fan works in the meantime. Readers are also helping one another directly: the r/DeletedFanfiction Reddit community, Bluesky members and others have shared copies they downloaded earlier and gathered suggestions for alternatives. That community response may help readers find something to read, though it can’t guarantee access to every missing work.
Those options can provide a place to browse, but they won’t necessarily carry the same works, communities or reading history as AO3. A reader looking for a particular story may find a recommendation or a saved copy, or may find that neither is available. And this is the part most people overlook: reader-to-reader sharing can help with access, but it depends on someone having downloaded a work already and being able to share it.
What the recovery period means
The two to four week window gives users a planning estimate, not a firm return date. The possibility of an earlier degraded service and temporary shutdowns adds uncertainty to that estimate. For readers, the sensible approach is to check the organization’s status updates for changes, while making other reading plans in the meantime. For the organization, the challenge is to restore access while continuing to assess the incident; the public updates don’t yet explain how those steps will affect one another.
There’s a broader lesson in the disruption, though it shouldn’t be mistaken for a claim about what happened at AO3. Online archives can become central to how people find and revisit work, which makes extended downtime more than a brief inconvenience. If you’re working in this space, the episode is a reminder that service continuity and clear communication shape users’ trust during an incident. The details here remain limited. For now, readers have a recovery range, a password recommendation and an invitation to follow updates—not a confirmed account of the incident’s full scope.