Illustration: AO3 confirms security incident; return could take up to a month
AO3 · Breach

AO3 confirms security incident; return could take up to a month

· 1 min read

The OTW confirmed in a status report that the Archive of Our Own outage stems from a security incident, after staff found evidence of a breach. The entire site was taken offline for investigation and cleanup; restoration is expected to take about two weeks, possibly up to a month, and OTW says it expects no data loss. The organization ruled out any link to this week's PHP patch wave since AO3 runs on Ruby on Rails; users should wait for the official return.

WhatsApp LinkedIn X
MediumBreachNo software to update
In this article
  1. What happened
  2. Why it matters
  3. What to do
  4. For the technical team
  5. Timeline
  6. Sources

What happened

The OTW, the nonprofit that runs Archive of Our Own (AO3), confirmed the site is down due to a security incident. Staff found evidence of a breach and chose to take everything offline for investigation and cleanup. Restoration is expected to take about two weeks, possibly up to a month; OTW says it expects no data loss.

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Why it matters

A massive fanfiction site is fully inaccessible for weeks, with no short-term return date. Writers and readers lose the platform, its community and story discovery; part of the community is moving to other sites. OTW says it expects no data loss.

What to do

Wait for the official return while monitoring OTW status reports, and keep local copies of critical content. For companies, the case is a rare example of a full response: taking everything offline for weeks to investigate and clean completely.

For the technical team

Affected
AO3 (Archive of Our Own) AO3, plataforma de publicação de fanfics; site inteiro colocado offline por 2 a 4 semanas · AO3 (Archive of Our Own), entire site.
Exploitation
Breach details were not disclosed. OTW confirmed the security incident in an updated status report on Friday morning; a post on X describes the action as a response to evidence of a breach that was found.
Fix
No software fix applicable. Restoration estimated at about two weeks, possibly up to a month; OTW says it expects no data loss.
Vector
Not detailed in the sources. OTW found evidence of a breach and took the entire site offline for investigation and full cleanup. An OTW representative told CNET the incident is not related to the PHP security issue, as the Archive uses Ruby on Rails.
More details
Timeline per 404 Media: the site went down Wednesday night; on Thursday OTW announced maintenance with a two-week to one-month estimate; on Friday morning it confirmed the security incident in a status report. OTW is entirely volunteer-run. Authors report moving to Space Battles, Sufficient Velocity and fanfiction.net during the outage.

Timeline

  1. OTW officially confirmed the outage is due to a security incident and ruled out any link to the PHP patching wave.

  2. First report: breach evidence leads AO3 to take the entire site offline for weeks.

Sources 2 sources

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how. After signing up you get the full feed.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click