Why Is AO3 Still Having Problems? Archive of Our Own Returns in a Limited State — Nov. 16, 2026

Checked: November 16, 2026, at 12:17 UTC (7:17 a.m. Eastern Standard Time in Toronto; Canada spans multiple time zones).

Archive of Our Own (AO3) is no longer completely offline, but readers may still encounter slow pages, intermittent errors, or features that do not work. The Organization for Transformative Works (OTW), the nonprofit that operates the archive, restored access on November 15 after a security incident forced the site offline on October 29. The return is a limited one: user and collection icons are hidden, importing works from external sites is unavailable, and downloads are currently limited to HTML. OTW says these restrictions are temporary and that recovery work is continuing.

The practical answer to “Why is AO3 down?” is therefore that the platform is in a staged recovery after a security incident—not that a new, fully confirmed outage has taken the entire archive offline again. OTW’s latest restoration notice, posted November 15 at 08:00 UTC, says the site is back but may load slowly because traffic is being managed deliberately. The latest indexed view of the official status page lists AO3 as experiencing “Degraded Performance.” Readers should check the official status page before assuming that an error on their device means the archive has gone down for everyone.

Key Takeaways

  • AO3 returned on November 15, 2026, after roughly 17 days offline following a security incident.
  • The site is available in a reduced state: icons are hidden, external work imports are disabled, and work downloads are limited to HTML.
  • OTW says no works, bookmarks, kudos, or drafts were deleted during the shutdown; automatic draft deletion is paused until November 29.
  • OTW cannot rule out user-database exposure, recommends updating AO3 account details and changing reused passwords, and is working with a security firm.

Is AO3 down right now, or has it come back?

OTW announced on November 15 that AO3 was back online earlier than the four-week recovery window previously discussed. The status update was published at 08:00 UTC; the official AO3 Status account also posted the restoration notice on Bluesky at 08:28:58 UTC that day. The service did not return with every feature enabled. OTW deliberately brought the archive back in a reduced configuration so users could regain access while technical and security work continued.

That distinction matters when checking reports on November 16. A reader may be able to open a work while another sees a temporary-unavailability page or a slow response. OTW says high traffic can cause delays and that this throttling is intentional to manage demand. The official status page’s component label is more useful than a single failed page load: it currently has an indexed status of “Degraded Performance,” rather than a clean indication that every part of AO3 is fully restored.

For the most reliable updates, use the OTW Status Page and its incident history. You can also follow the official AO3 Status account on Bluesky. Third-party outage trackers and social posts can help show whether other readers are reporting problems, but they are not substitutes for OTW’s own notices.

Why did AO3 go offline in October?

The shutdown began on October 29, 2026. OTW’s status history records an initial maintenance notice at 07:13 UTC, followed by an update at 09:03 UTC saying maintenance was in progress and expected to take at least 12 hours. At 17:41 UTC, the status page said the maintenance would take longer. On October 30, OTW published a fuller explanation: it had detected evidence of a security incident and would keep AO3 offline while investigating and addressing the issue.

OTW initially estimated that restoration would take at least two weeks and could take up to four. The organization did not publish technical details about the incident or identify a specific vulnerability or attacker. It has also said it would not disclose the details of the mitigating changes being made while the security review is underway. Readers should therefore be wary of posts claiming to know exactly how the incident happened unless those claims are backed by an official statement or independently verified reporting.

OTW has partnered with an external security firm to review the incident and analyze the site. That is a confirmed part of the recovery process. The organization has not, however, announced a complete forensic account or a final report describing the cause. The fact that AO3 is available again does not mean the investigation is finished or that every security question has been resolved.

OTW’s October 30 explanation is available in its official update on the AO3 downtime. The Associated Press report on AO3’s return also summarizes the shutdown and the platform’s limited reopening.

Which AO3 features are still unavailable?

OTW says several features were temporarily switched off to bring the archive back sooner. The limitations announced with the November 15 restoration include:

  • User and collection icons: icons are not currently displayed. OTW stresses that they have not been deleted; they are simply hidden while the site is in its reduced state.
  • External work importing: importing works from other websites is unavailable for now.
  • Download formats: works can currently be downloaded in HTML format only. Readers who normally use another format should not assume those options have returned.
  • Page-loading delays: high traffic may slow the site. OTW says this is an intentional measure to help manage the volume of requests.

OTW says the disabled features are expected to be restored, but it has not provided a firm public timetable for each one. A feature-by-feature return schedule should not be inferred from the fact that the main archive is accessible.

Are AO3 works, bookmarks, and drafts safe?

OTW says no AO3 data was deleted during the outage. That includes users’ published works, bookmarks, and kudos. It also says draft deletion was successfully paused, so no drafts were deleted while the archive was offline. This is reassuring for writers returning to unfinished work, but it is not a reason to leave drafts unreviewed.

Automatic draft deletion is scheduled to return to normal beginning November 29, 2026. From that date, drafts that are 30 days old will again be deleted under AO3’s usual process. OTW warns that the deletion date displayed at the top of an individual draft will still reflect 30 days after its original creation date; it will not show the temporary extension. The organization recommends reviewing drafts and saving a personal copy or publishing them as soon as possible. If a draft matters to you, make a separate backup rather than relying on the date displayed on the draft page.

There is a separate account-security question. OTW says it has no reason to believe the user database was compromised, but it cannot rule out that possibility. The database may contain usernames, email addresses, IP addresses, and hashed passwords. OTW says it does not collect users’ real names and that donor information is stored in a separate system that is not linked to AO3.

As a precaution, OTW recommends considering a password change, making sure the email address on the account is current, and changing passwords on other websites where the same password was reused. Use a unique password for each service. Do not follow password-reset links from unsolicited messages or enter account details on unofficial “AO3 recovery” pages. Go directly to the archive or OTW’s official channels instead.

What should readers do if AO3 will not load?

If the archive gives you a downtime page or takes unusually long to respond, OTW’s advice is to refresh and try again. Because the organization says it is deliberately managing traffic, repeatedly reloading the page in quick succession is unlikely to help. A calmer sequence is more useful:

  1. Check the official OTW status page for the AO3 component and the latest incident update.
  2. Check the AO3 Status account on Bluesky for a timestamped announcement.
  3. Wait briefly, then refresh once. If the page still fails, try again later rather than continuously sending requests.
  4. If the status page shows the archive is operational but your browser still fails, try a private window or another browser, and check whether other websites load normally. These checks can help identify a local browser or connection issue; they do not diagnose AO3’s servers.
  5. When you can sign in, review unfinished drafts, save copies of important material, confirm your account email, and update any reused password.

Do not treat unofficial mirrors, reposted copies, or social-media links as a replacement for the archive. Authors retain control over their work, and a story being unavailable does not give others permission to upload it elsewhere. If you want to keep a copy of a work, use the download options the author and AO3 make available, and respect the creator’s preferences.

When will AO3 be fully restored?

OTW has not announced a date when every feature will return. Its November 15 notice says the archive is back earlier than the original maximum estimate, but with some functions disabled and traffic controls in place. The organization says recovery work is ongoing and that the unavailable features will be restored. The external security review is also part of the process.

For readers, the next useful milestones are the return of icons, the reopening of external work importing, and the restoration of additional download formats. For writers, November 29 is the most urgent date because normal draft deletion is due to resume. Until OTW posts a more detailed timetable, treat full restoration as work in progress rather than a confirmed date.

Frequently Asked Questions

Is AO3 completely back online?

No. AO3 returned on November 15, 2026, but OTW says it is operating with some features disabled and may load slowly. Its status page’s latest indexed component status is “Degraded Performance.”

Were AO3 stories or drafts deleted during the outage?

OTW says no works, bookmarks, kudos, or drafts were deleted during the shutdown. Draft deletion is paused until November 29, when the normal rule for drafts that are 30 days old is scheduled to resume.

Should I change my AO3 password?

OTW recommends considering a password change, confirming that the email address on the account is current, and changing any passwords reused on other sites. The organization says it has no reason to believe the user database was compromised, but cannot rule it out.

Sources: Organization for Transformative Works Status Page; OTW incident history and November 15 restoration notice; Organization for Transformative Works, “Update on AO3 Downtime,” October 30, 2026; AO3 Status on Bluesky; Associated Press, report on AO3’s return, November 16, 2026.

Leave a Comment

NHS Cancer Sponge Test: NICE Draft Backs Wider Access for Persistent Acid Reflux — Nov. 16, 2026

NICE has proposed wider NHS use of Cytosponge and EndoSign for selected people with persistent acid reflux and risk factors. The guidance is still in draft form.

How the Coles Cyber Incident Happened and What Systems May Be Affected (17 November 2026)

How the Coles Cyber Incident Happened and What Systems May Be Affected (17 November 2026)

Coles is investigating a cyber security incident but says it has found no evidence so far that customer, team or supplier data was compromised or removed. Here is what is known, what remains unclear and what shoppers can do.

Mike Vrabel’s Munich Beer Celebration: The Pregame Moment Revisited After Patriots’ Loss | Nov. 16, 2026

Mike Vrabel’s Munich Beer Celebration: The Pregame Moment Revisited After Patriots’ Loss | Nov. 16, 2026

Mike Vrabel’s Munich beer-hall celebration happened before the Patriots’ Nov. 15 game, not after it. Here’s what followed the 35-10 loss to Detroit.

Coles Cyber Security Incident: What Shoppers Should Do Now | Nov. 17

Coles Cyber Security Incident: What Shoppers Should Do Now | Nov. 17

Coles says it has found no evidence customer data was compromised so far. See what Australian shoppers should check, how to avoid scams and where to get updates.

Steelers vs. Bengals Tactical Breakdown: Why Pittsburgh Couldnt Contain Joe Burrow | Nov. 16, 2026

Steelers vs. Bengals Tactical Breakdown: Why Pittsburgh Couldnt Contain Joe Burrow | Nov. 16, 2026

Joe Burrow threw for 409 yards and four touchdowns as Cincinnati beat Pittsburgh 38–18. See why the Steelers' pressure plan failed and how the Bengals exploited it.

Coles Cyber Attack: What Shoppers Need to Know as Investigation Continues — November 16, 2026

Coles Cyber Attack: What Shoppers Need to Know as Investigation Continues — November 16, 2026

Coles is investigating a cybersecurity incident but says it has found no evidence that customer, team or supplier data was compromised or removed. Here’s what shoppers should know now.

How the Swallowable Sponge Test Checks for Early Esophageal Cancer Signs | Nov. 16, 2026

How the Swallowable Sponge Test Checks for Early Esophageal Cancer Signs | Nov. 16, 2026

Learn how the NHS capsule sponge test collects esophageal cells, what a result can show, who may be offered it in the UK, and why it does not replace endoscopy.

NHS Sponge Test: What It Could Mean for Indigestion and Endoscopy Waits | November 16, 2026

NHS Sponge Test: What It Could Mean for Indigestion and Endoscopy Waits | November 16, 2026

The NHS capsule sponge pilot reduced endoscopy demand for routine reflux referrals. Here is what the evidence means for patients with persistent indigestion—and what it does not promise.

Drake Maye Injury Update: Significant Lower-Leg Injury Reported, Diagnosis Still Pending — Nov. 16, 2026

Drake Maye Injury Update: Significant Lower-Leg Injury Reported, Diagnosis Still Pending — Nov. 16, 2026

Drake Maye left the Patriots’ Nov. 15 loss to Detroit with an ankle injury. Here’s what the team has confirmed, what NFL Network reports, and what remains unknown.

Fernando Mendoza’s First NFL Start: TD Spark, 21–13 Loss | Nov. 16

Fernando Mendoza’s First NFL Start: TD Spark, 21–13 Loss | Nov. 16

Fernando Mendoza scored his first NFL touchdown in his first Raiders start, but Seattle’s defense and second-half surge handed Las Vegas a 21–13 loss.