AO3 first went offline on the morning of Oct. 29 with a short maintenance notice, and the team initially expected the work to take 12 hours or a bit longer. Within hours, the estimate jumped to around two weeks and up to four. Later that day, the OTW explained why: it had found evidence of a security incident and was still working out how far it reached.
The OTW hasn’t said how the attackers got in. One theory that spread online linked the outage to the recently disclosed critical flaws in PHP, a programming language that powers a huge share of websites. That link looks unlikely, because AO3 runs on Ruby on Rails, a different toolkit for building websites.
Why so slow? AO3 has no paid staff. The OTW has zero employees and relies on a team of about 1,000 volunteers, plus donations. Rebecca Tushnet, an OTW founder who co-chairs its legal committee, said the team is being very careful and won’t restore anything until it is confident the problem has been patched. She called it the biggest outage since the archive opened to the public in November 2009.
It isn’t the first attack on the site. In July 2023, a group calling itself Anonymous Sudan knocked AO3 offline for 28 hours with a flood of junk traffic, known as a DDoS attack.