Archive of Our Own could need around two weeks to restore service, with the disruption possibly lasting four weeks, according to OTW’s 29 October 2026 update at 17:41 UTC. There is no confirmed return date. The same notice leaves open an earlier return with reduced functionality, followed by further interruptions.

The outage began as a maintenance incident on 29 October. AO3’s official news account directed readers to its status page, where the estimate changed during the day. For readers and writers planning around access, the latest timestamp is more useful than treating every maintenance post as a separate promise.

Maintenance at 07:13 UTC, at least 12 hours estimated at 09:03, then around 2 weeks and possibly 4 weeks at 17:41. Earlier degraded access is only a possibility.
Official incident chronology on 29 October 2026. All update times are UTC; the possible partial return has no confirmed date. View full-size graphic ↗

What changed during 29 October

The incident log first reported maintenance at 07:13 UTC. At 09:03 UTC it estimated at least twelve hours, allowing for a longer interruption. The 17:41 UTC notice then gave the much longer two-to-four-week range. The twelve-hour figure therefore should not be used as the current countdown.

The latest update was posted at 17:41 GMT in the UK and 13:41 EDT on the US East Coast on 29 October. Those are the same moment, not different restoration schedules. The service-wide estimate applies to both audiences; the notice does not provide a country-specific rollout.

A partial return would not settle the incident

OTW says it hopes to reopen the site earlier in a degraded state and warns that temporary shutdowns could follow before the problem is fully resolved. A page becoming reachable would therefore be a reason to read the next status update, rather than proof that normal access had permanently returned.

The current incident notice does not disclose a root cause or establish whether any data has been lost. It also does not support a definite November reopening day. Assigning a calendar deadline to the estimated range would add a precision the official statement does not offer.

How to follow the change without relying on a countdown

Open the dated incident report in the sources below for the sequence of updates, then use its Current Status link to check the overall service state. AO3 News is a second official route to announcements. Keeping these links available makes it easier to distinguish a new estimate from a repost of an older one.

For work you are composing, saving a local copy is a practical precaution while access remains uncertain. Plan publication or reading sessions around a confirmed service update rather than an assumed return day. The useful next signals are an official notice of partial availability, any stated restrictions and eventual resolution; each answers a different question about reliability.

Sources & context

Forecasts and restoration estimates are dated projections. The official sources below govern subsequent changes; this article will be updated at the same URL.

AI assisted with drafting and editing. This article is part of our preview edition. Editorial standards & corrections →