ao3 Security Shutdown: the outage that took 18 million fanworks offline
On October 29, 2026, the Organization for Transformative Works took ao3 offline for what it first called maintenance, confirming a day later that it was a security incident. With roughly 11 million users waiting on an outage expected to last two to four weeks, the shutdown became a stress test for one of the internet's largest fan archives - and a reminder that no platform is permanent.
Skills for ao3
Three original skills built from this outage: one for writers who want offline copies of their work, one for site admins who need a crisis communication plan before they need it, and one for communities that must move in an orderly way when their platform goes dark.
Docs
Fanworks Offline Backup Plan
A calm, repeatable ritual for keeping your stories, bookmarks, and reading lists safe outside any single platform.
Security
Incident Response Runbook Writer
A communication runbook for the first 24 hours of a security incident: who speaks, what to say, and what to withhold.
Social
Community Migration Kit
An orderly migration plan for when your community's platform goes dark: pick a destination, move together, keep a home base.
Case studies: ao3
Real-world case studies. Original summaries by AI Services Market — each links to the skills it demonstrates.
The Night the Archive Went Dark
On October 29, 2026, the Organization for Transformative Works took the Archive of Our Own offline for what it first called maintenance, con…
Read case → 2
'Survival Guides' and the Great Migration
With no timeline for a fix, readers organized themselves: shared Google Docs circulated with downloaded stories so people could keep reading…
Read case → 3
Change Your Password: The Data Advisory
OTW warned that the incident may have exposed usernames, email addresses, IP addresses, and hashed passwords, and advised users to change th…
Read case →ao3: questions, answered
Facts first — and the skill each question points to.
What is ao3?
The Archive of Our Own is a nonprofit, fan-run library of fanfiction and other fanworks, operated by the Organization for Transformative Works since 2007. It serves about 11 million registered users and hosts more than 18 million works. Fanworks Offline Backup Plan helps writers keep their own copies of what they publish there.
When will ao3 be back online?
OTW said the outage would last at least two weeks and up to four from the October 29, 2026 shutdown, with a possible earlier return in a degraded or read-only mode. That timeline comes from OTW's early response, when the scope was still undetermined - it is a statement, not a guarantee. Incident Response Runbook Writer
Was my user data exposed?
OTW warned that usernames, email addresses, IP addresses, and hashed passwords may have been exposed. The organization said it did not believe the user database had been stolen but could not rule it out, and advised users to change their passwords. If you reused your password elsewhere, change it there too.
Were any stories deleted?
No. OTW confirmed no fanworks were deleted during the incident, and that bookmarks, kudos, and published works were safe. The loss readers felt was access, not content - which is exactly why Fanworks Offline Backup Plan exists.
How could people keep reading during the outage?
Fans organized shared Google Docs of downloaded stories, circulated as informal "survival guides," so reading could continue without the site. Some writers and readers also began migrating to other platforms, including Inkitt. Community Migration Kit covers how a community moves in an orderly way when its platform goes dark.
Is the outage related to the PHP Armageddon security flaws?
No. The Archive of Our Own is built on Ruby on Rails, not PHP, so it is unrelated to those CVEs. The timing was a coincidence, and it confused some readers because both stories broke in the same month.
Should I move my stories to another platform?
Some writers did move to platforms such as Inkitt rather than wait out the outage, but moving is a decision with trade-offs - audience, archiving features, and moderation all differ. Community Migration Kit walks through choosing one destination and moving together. Whatever you decide, keep your own copies: Fanworks Offline Backup Plan.
What should site admins learn from how OTW communicated?
OTW first called the outage maintenance on October 29 and clarified it was a security incident on October 30 - a one-day gap that became part of the story. The lesson is to name the unknown honestly from the start: say what happened, what you do not know, and when the next update comes. Incident Response Runbook Writer turns that lesson into a fill-in-the-blanks template.
How do I back up my AO3 library right now?
Start with an inventory: your published works, drafts, bookmarks, and reading lists. Download each story with its metadata in a durable format like HTML, save bookmarks as an export or a table, and verify the copies open offline. Fanworks Offline Backup Plan gives you the full ritual and worksheet.
What happens if the site comes back read-only?
OTW said service might return sooner in a degraded or read-only form, which would let people read but not post new works or comments. A read-only return makes local copies even more important for writers who need to keep working. Fanworks Offline Backup Plan keeps your writing life independent of the site's status.
Inspired by the AO3 security shutdown (October 2026). Summaries are our own; facts from public reporting.