AO3 Is Back After a 17-Day Security Shutdown, but the Fan Fiction Archive Still Can't Rule Out That Its User Database Was Taken
Archive of Our Own returned early on Sunday with icons, imports and most download formats switched off. Its nonprofit operator says no works or drafts were lost and it has hired a security firm, but it won't say what happened and is telling users to change their passwords.
Published
Last updated / Fact-checked on

Illustrative photo of an e-book on a tablet. It does not show Archive of Our Own.
Archive of Our Own, the fan fiction archive, is back online after 17 days offline following a security incident. The site returned on Sunday, Nov. 15, with several features still switched off, its operator, the nonprofit Organization for Transformative Works, said on its status page. The Verge and The Cut also reported the return.
"AO3 is now up!" the group wrote in an update stamped 08:00 UTC, which is midnight Pacific time. It said it had turned some features off so it could bring the site back before the four-week mark it had warned about.
The organization also repeated a warning it has given since the start. It has "no reason to believe that the user database was compromised," it said, but "we cannot rule out that possibility."
At a glance
| Item | Detail | Source |
|---|---|---|
| Down | Oct. 29, 2026 | OTW status page, The Verge |
| Back | Nov. 15, 2026, 17 days later | OTW status page, The Cut |
| Data deleted | None, including drafts | OTW |
| User database | No evidence it was taken; cannot be ruled out | OTW |
| Data held | Username, email, IP address, hashed password | OTW, Oct. 30 update |
| Still off | Icons, external work importing, non-HTML downloads | OTW |
| Draft deadline | Normal 30-day draft deletion resumes Nov. 29 | OTW |
| Outside help | A security firm is reviewing the incident | OTW |
What happened, as far as anyone has said
The site went down on Oct. 29. Its status page first called it maintenance, at 07:13 UTC that day, and said the work would take at least 12 hours. Later that day the organization said restoring service would take around two weeks and possibly up to four.
At 01:27 UTC on Oct. 30, which was still the evening of Oct. 29 in California, the organization explained why. "Earlier today, we detected evidence of a security incident on AO3," it wrote. It said it was in the early stages of working out the scope.
That update laid out what could be at risk. The AO3 database holds account information that may include a username, email address, IP address and a hashed version of the user's password. Hashing scrambles a password so it cannot easily be turned back into the original. The organization said it uses industry-standard methods, but it also warned that "no hashing method can fully protect a weak or reused password from being cracked." AO3 does not collect real names, and donor information is kept in a completely separate system that is never linked to AO3, so neither was exposed, it said.
What the organization has not said is just as important. It has not described the type of incident, who was responsible, how they got in or how many accounts could be affected. In Sunday's update it said that because this is a security incident, it will not share details of the fixes it is making. It did say it has brought in a security firm to review the incident and examine the site to help prevent future problems.
A partial return
AO3 is not fully back yet. Icons across the site, including user and collection icons, are not being shown, though the organization said none have been deleted. Importing works from outside sites is unavailable. Works can only be downloaded as HTML for now. The organization said all of these features will return.
Visitors may also have to wait before the site loads. The group said this delay is intentional, to handle the surge of returning users, and that anyone who sees the downtime page should refresh and try again.
Drafts get a two-week reprieve
For many writers, the biggest worry was unfinished work. AO3 normally deletes drafts after 30 days. The organization said on Nov. 6 that it was working to stop drafts from being deleted while the site was down. On Sunday it confirmed that draft deletion had been paused successfully and that no drafts were lost.
It will stay paused for two more weeks. From Nov. 29, normal deletion returns, and any draft 30 days old or more will be deleted. The organization warned that the deletion date shown at the top of each draft will still show 30 days from creation, not the new deadline. It recommended that users save a copy of their drafts or publish them soon.
The Nov. 6 update also explained a puzzle for some users. Notification emails, such as subscription updates and kudos alerts, that were queued before the site went down had been released during the restoration work. The organization said those emails were real and not a cause for concern.
What users should do now
The organization's advice is simple. Consider changing your AO3 password and make sure the email address on your account is current. If you used your AO3 password anywhere else, change it on those sites too.
That last step matters most. Hashed passwords are hard to reverse, but anyone holding a stolen database can still guess at them, and weak ones fall first. Short or reused passwords can be cracked, and then tried on email, banking and social media accounts. Anyone who reused an AO3 password should treat those other accounts as the real risk.
Why it matters
AO3 relies on volunteers. In Sunday's update the organization thanked users for their patience "as our volunteers work hard to return AO3 to its full functionality." A volunteer-run community archive faces the same kinds of security threats as commercial platforms.
The organization handled several things well. It said early that the database could not be ruled safe, explained what data it holds, separated donor data from user accounts, protected drafts and kept to its estimate. But users still don't know the most important facts: how the attackers got in and whether any data left the site. Until the security review reports, the safest assumption is the one the organization itself suggests: act as if your AO3 password may be known.
What to watch
Watch for the outside security firm's findings and whether the organization publishes them. Watch for icons, imports and other download formats to return, and for whether the site stays up or has to go offline again during recovery, which the organization warned in October could happen. Writers with drafts should note the Nov. 29 deadline.
How we reported this
DailyMech read every update on the Organization for Transformative Works status page for this outage, plus reports from The Verge and The Cut, in full. Times on the status page are in UTC and are converted to Pacific time here. The organization has not disclosed the cause or scale of the incident, and DailyMech does not guess at it. DailyMech contacted no one for this article.
Published November 15, 2026. Facts checked against the cited sources by DailyMech's AI writer.
Sources
- AO3 Down for Maintenance (incident updates, Oct. 29 to Nov. 15, 2026), Organization for Transformative Works status page (fully read).
- AO3 is back after 17 days., Terrence O'Brien, The Verge, Nov. 15, 2026 (fully read).
- Fan Fiction Site AO3 Is Back After a 'Security Incident', Sam Reed, The Cut, Nov. 15, 2026 (fully read).
DailyMech used AI tools to research and draft this article. Facts were checked against the cited sources by DailyMech's AI writer, not by a human editor.