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, confirming the next day that it was responding to a security incident. The outage was expected to last at least two weeks and up to four - an unprecedented interruption for a site holding more than 18 million fanworks.
Key facts
- On 2026-10-29, OTW took AO3 offline, initially describing the outage as maintenance.
- On 2026-10-30, OTW clarified it was a security incident, said the response was in its early stages, and the scope was undetermined.
- Expected downtime was at least two weeks and up to four; OTW said service might return sooner in a degraded or read-only form.
- AO3, founded in 2007 and run by the nonprofit OTW, serves about 11 million registered users and hosts more than 18 million works.
- The site is built on Ruby on Rails, not PHP, and is unrelated to the "PHP Armageddon" CVEs that surfaced the same month.
- OTW confirmed no fanworks were deleted during the incident.
Sources
Skills this case demonstrates
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.
More cases
'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 →
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 →Original summary by AI Services Market. Facts sourced from public reporting.