Skip to main content

Is Archive of Our Own Down?

No — Archive of Our Own is up

Reachable from all 8 checked regions

Average response time: 135ms

Last checked · checks run every 6 hours

Official status page: https://www.otwstatus.org

Archive of Our Own uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
114ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

56-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 24 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
208ms
DNS 118ms TCP 2ms TLS 19ms TTFB 207ms
iad
99ms
DNS 61ms TCP 5ms TLS 10ms TTFB 98ms
jnb
200ms
DNS 177ms TCP 0ms TLS 5ms TTFB 199ms
lax
254ms
DNS 149ms TCP 28ms TLS 33ms TTFB 251ms
lhr
93ms
DNS 60ms TCP 2ms TLS 8ms TTFB 92ms
nrt
34ms
DNS 12ms TCP 1ms TLS 7ms TTFB 33ms
ord
96ms
DNS 8ms TCP 16ms TLS 22ms TTFB 95ms
sin
99ms
DNS 72ms TCP 1ms TLS 7ms TTFB 98ms

What Archive of Our Own does

Archive of Our Own, usually shortened to AO3, is a non-commercial fan fiction archive run by the Organization for Transformative Works, a volunteer non-profit. It hosts millions of works with a detailed tagging and filtering system, and takes no advertising, funding itself through donation drives instead. Readers and writers treat it as the default home for fan writing.

What an outage looks like

AO3 outages usually show as Error 502 or 503 pages rather than a clean message, or as pages that load slowly and then time out. A separate and more common problem is a Retry Later message, which is a per-IP rate limit rather than an outage. Forced logouts reading session expired or auth error are a known ongoing issue AO3 documents itself.

What to do about it

The Organization for Transformative Works publishes a status page at otwstatus.org covering Archive of Our Own alongside Fanlore and its other projects. AO3 also posts updates on Bluesky at status.archiveofourown.org, on Tumblr as ao3org and on Twitter as AO3_Status. If you are seeing Retry Later, AO3's own advice is to slow down: the block is temporary per IP and clears after a few minutes.

Is it down for everyone, or just you?

If this page says Archive of Our Own is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Archive of Our Own outage FAQ

Is AO3 down or am I being rate limited?
They look different. A real outage returns a 502 or 503 error page or fails to load at all, and the Organization for Transformative Works will normally flag it on otwstatus.org. A Retry Later message is AO3's rate limiter, triggered when one IP address makes a large number of requests in a single minute. AO3 says the block is temporary and allows requests again after a few minutes.
Why do I keep getting logged out of AO3?
AO3 lists recurrent forced logouts as a current known issue, separate from any outage. If you get a session expired or auth error message, AO3's guidance is to log back in from the Login page rather than the pop-up form in the top corner, then reopen the page you were viewing instead of refreshing the tab that failed. It has been happening since September 2024.
Will I lose a work I was posting when AO3 goes down?
Anything already saved stays saved, but text sitting unsubmitted in the editor when a request fails is not stored on AO3's side. Drafting long works elsewhere and pasting them in avoids the problem. AO3 notes that formatting from Google Drive and some word processors does not survive the paste into its rich text editor, so check the result before posting.
Does an AO3 outage stop subscription emails?
Notification emails come from do-not-reply@archiveofourown.org and can be delayed when the site is struggling. AO3 also notes that missing notifications are often not an AO3 fault at all: they are frequently caught by spam filters or blocked by the receiving provider. Adding that address to your contacts, and checking the junk or Social folder, resolves most reports.

How we measure this

  • We request Archive of Our Own's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Archive of Our Own publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Archive of Our Own goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required