Signs of trouble actually surfaced days before the official outage. Between October 23 and 24, users reported strange anomalies—unexpected email notifications and erratic search histories. By October 30, the OTW status team shattered any remaining optimism, announcing that service restoration would require two to four weeks. Major Philippine media outlets, including the Manila Bulletin, GMA News Online, Philstar, and ABS-CBN, quickly documented the impact on local authors and readers who suddenly found themselves locked out of a platform hosting over 18.4 million works across 82,900 fandoms.
The loss went beyond simply missing the latest chapter of a favorite story. Archive of Our Own functions as a massive, reader-built library; suddenly losing access meant years of curated bookmarks, saved drafts, and comment histories were floating in a precarious limbo. Recent PHP and TLS certificate vulnerabilities had already put the tech community on edge, and the OTW's own Fanlore wiki had previously faced temporary closures to patch similar flaws, making foundational security a prime suspect for the prolonged closure.
Are the stories actually safe? On November 6, the OTW confirmed that all stored works and user accounts remained intact during the security response, and pre-outage queued emails finally began releasing. Measures were also firmly in place to prevent saved drafts from being deleted. However, they could not fully rule out the possibility that the user database had been accessed.
Names, email addresses, IP addresses, and hashed passwords might have been exposed to the attackers. Anyone who used the same password on the archive as they do elsewhere needs to change it immediately to prevent cross-site credential stuffing.