← Voltar ao feed

Archive of Our Own (AO3) offline, restoration estimated at 2-4 weeks after failed maintenance

1 fonte(s) · 1 atualização(ões) · publicado 29/10/2026 17:43 · coletado há 3 dias

Archive of Our Own (AO3), the fan fiction platform run by the nonprofit Organization for Transformative Works (OTW), went offline during what was planned as routine overnight maintenance and now estimates service restoration will take around 2 weeks, possibly up to 4 weeks. The organization says it hopes to bring the site back in a degraded state sooner. No cause has been disclosed and no breach or attack has been claimed. The article notes speculation linking the outage to the recent "PHP Armageddon" critical PHP flaws surfaced by OpenAI and Google Wiz tooling, but AO3 runs on Ruby on Rails, making that connection unlikely. OTW and AO3 did not respond to requests for comment.

Detalhes técnicos

The outage began during scheduled maintenance. AO3's stack is Ruby on Rails, not PHP, so the two critical PHP vulnerabilities reported the prior week are assessed as unrelated. No indicators, vulnerability identifiers or threat actor attribution are provided.

Linha do tempo

  1. techcrunch.com ↗ · pub. 29/10/2026 17:43 · coletado 29/10 18:00 primeiro registro

    Archive of Our Own (AO3) offline, restoration estimated at 2-4 weeks after failed maintenance

    ler a análise desta fonte

    Archive of Our Own (AO3), the fan fiction platform run by the nonprofit Organization for Transformative Works (OTW), went offline during what was planned as routine overnight maintenance and now estimates service restoration will take around 2 weeks, possibly up to 4 weeks. The organization says it hopes to bring the site back in a degraded state sooner. No cause has been disclosed and no breach or attack has been claimed. The article notes speculation linking the outage to the recent "PHP Armageddon" critical PHP flaws surfaced by OpenAI and Google Wiz tooling, but AO3 runs on Ruby on Rails, making that connection unlikely. OTW and AO3 did not respond to requests for comment.

    Technical Details

    The outage began during scheduled maintenance. AO3's stack is Ruby on Rails, not PHP, so the two critical PHP vulnerabilities reported the prior week are assessed as unrelated. No indicators, vulnerability identifiers or threat actor attribution are provided.