AO3 Is Down. Is Your Writing Safe? Here's What's Confirmed.

As of November 2, 2026. This one isn't rated: there's no confirmed AI connection, so there's nothing for the scale to measure.

Update, November 6, 2026: AO3 is still down, and OTW says its original estimate still holds. Here's the latest.

If you've spent years writing stories on Archive of Our Own, a headline saying the site could be gone for weeks is enough to make your stomach drop. Those uploads are late nights, unfinished chapters, favorite comments, and entire worlds built one sentence at a time.

So I'll start with the most reassuring thing available: the Organization for Transformative Works (OTW), which runs AO3, says "no AO3 data has been deleted. All your works, bookmarks, kudos, etc., are safe." The site being unavailable does not mean your writing has vanished.

There is a real security concern, though. Here's what deserves your attention, what's still unknown, and what you can do.

What happened

AO3 went offline on October 29, initially listed as maintenance. On October 30, OTW said it had "detected evidence of a security incident" that day and was still working out its scope.

OTW's current estimate is that AO3 will be down for at least two weeks and possibly up to four. It may come back sooner in a "degraded state," with some features missing or the site read-only, and it might have to go down again temporarily during recovery. That's an estimate, not a promised reopening date. As of November 2, OTW hasn't posted a newer update; it says the next one will come "when we have further information available."

Is my account information safe?

That part is less settled.

OTW says it doesn't currently believe the user database was stolen, but it can't rule that out yet. The database may contain your username, email address, IP address, and a hashed version of your password. (A hashed password is stored in a scrambled form instead of readable text.) OTW says it uses industry-standard hashing, but also that "no hashing method can fully protect a weak or reused password from being cracked."

Two pieces of good news: AO3 doesn't collect real names, so none could be exposed, and donor information is kept in an entirely separate system that OTW says wasn't exposed.

OTW's main recommendation: change your password on any other site where you used the same password as on AO3. You don't need to wait for AO3 to reopen to do that.

Was AI involved?

Nothing in OTW's official updates mentions AI. OTW has confirmed a security incident without naming a cause or an attacker.

I cover AI risk here, so that distinction matters to me. An unexplained outage isn't evidence of an AI attack, and putting AI in the headline would add anxiety without adding information. If investigators find a connection, I'll cover it.

What writers can do now

• Change any reused passwords. Start with the accounts that share your AO3 password, especially your email. Give each account its own strong password; a password manager makes that painless.
• Get updates from the source. Check the OTW status page and OTW's own posts instead of screenshots passing around social media.
• Be wary of "account recovery" messages. Don't hand your login to anyone promising special or early access to your stories.
• Gather the copies you already have. Check your writing software, computer, cloud folders, email attachments and old downloads. You may have more saved than you remember.
• Back up when access returns. Download your works and keep one copy on your own device and another somewhere separate. Make it a habit for future chapters too.

Your only copy of a novel deserves a better security plan than "please let this website keep working."

What you can probably ignore

"Everyone's stories have been erased." OTW says plainly that no AO3 data has been deleted.

"Everyone's account information was stolen." OTW says it doesn't currently believe the user database was taken. It can't rule it out yet, which is why the password advice above is worth following, but "might have been" isn't "was."

"This is fallout from the PHP security mess." OTW told CNET it isn't related, because AO3 runs on Ruby on Rails, not PHP.

"An AI did this." No official update says so, and no evidence has been published.

Be especially skeptical of anyone who turns any of these claims into a sales pitch.

The bottom line

The practical priorities are clear: fix reused passwords, follow official updates, and plan to back up your work once access returns.

You're allowed to be upset about losing access to something you love. But there's a real reason to take a breath: the people running the archive say your work is still there.

Know a writer worried about their stories? Send them this. A little clarity travels better than another apocalypse headline.

Bunker status: the shovel stays in the garage. The fanfic stays in the archive, and soon on your hard drive too.

Sources

1. Organization for Transformative Works, "Update on AO3 Downtime, October 30, 2026" (primary source). https://www.transformativeworks.org/update-on-ao3-downtime-october-30-2026/
2. OTW status page, AO3 incident updates from October 29 to 30, 2026. https://otwstatus.statuspage.io/
3. 404 Media, Samantha Cole, "'Wake Up Call:' Fanfiction Writers and Readers React to AO3 Outage," October 30, 2026 (includes OTW's statement to CNET that the outage is unrelated to the PHP issue). https://www.404media.co/ao3-down-outage-reactions/