Skip to main content

Is AOL Down?

No — AOL is up

Reachable from all 8 checked regions

Average response time: 831ms

Last checked · checks run every 6 hours

Official status page: https://status.aol.com

AOL uptime

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

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

30-day history

70-day clean streak
Sep 14: 100.00% uptime, 31 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, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 24 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, 31 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 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, 31 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, 24 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.

ams
772ms
DNS 82ms TCP 21ms TLS 23ms TTFB 576ms
arn
1195ms
DNS 125ms TCP 1ms TLS 3ms TTFB 1014ms
cdg
820ms
DNS 65ms TCP 1ms TLS 3ms TTFB 630ms
ord
520ms
DNS 169ms TCP 1ms TLS 3ms TTFB 415ms
sin
1033ms
DNS 184ms TCP 1ms TLS 4ms TTFB 759ms
sjc
618ms
DNS 122ms TCP 1ms TLS 4ms TTFB 503ms
syd
1058ms
DNS 223ms TCP 0ms TLS 3ms TTFB 921ms
yyz
638ms
DNS 145ms TCP 8ms TLS 11ms TTFB 463ms

What AOL does

AOL runs one of the oldest consumer email services still in wide use, alongside a news and content portal at aol.com. Many of the accounts on it are two decades old and are still the address their owner gives to a bank, a doctor or a landlord. Its status page tracks the portal, email, login and customer care as four separate services.

What an outage looks like

Mail stops loading in the browser, either as a spinner that never resolves or a page that reloads to itself. Sending appears to succeed while messages never arrive. Sign-in fails independently of mail: the password page accepts credentials and returns to itself, or errors without explaining why. Third-party apps set up for IMAP start prompting for a password that worked an hour earlier.

What to do about it

Check status.aol.com, which reports AOL.com, Email, Login and Customer Care separately, so a sign-in incident and a mail incident do not look the same there. Mail addressed to you is normally queued and retried by the sending server for several days, so incoming messages are delayed rather than lost. Avoid resetting your password during a sign-in incident, because a reset that half-completes is harder to unpick than waiting.

Is it down for everyone, or just you?

If this page says AOL 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

Proton Mail
Proton Mail
Google Workspace
Google Workspace
Zoho
Zoho
SendGrid (Twilio)
SendGrid (Twilio)

AOL outage FAQ

Is AOL Mail down for everyone or just me?
The measurement above answers that from several regions at once, which separates a real outage from a problem on your own connection. If our probes reach AOL normally and status.aol.com reports nothing, the fault is closer to you: a DNS resolver, a corporate network, or a browser extension blocking the login flow. Trying a different network on a phone is the fastest way to confirm which of the two it is.
Why can I read mail on my phone but not on the website?
Because they are different paths into the same mailbox. The web client depends on the aol.com front end and its login service, while a phone app usually holds a long-lived token and talks to the mail servers over IMAP. An outage in the web front end therefore leaves an already-configured app working. The reverse also happens, and it is why the status page lists AOL.com and Email as separate components.
Will I lose email sent to me while AOL is down?
Almost never. When a receiving mail server is unreachable, the sending server holds the message and retries on a schedule, typically for four to five days before giving up. Messages sent during an outage generally arrive in a burst once service returns. What can genuinely be lost is a draft you were composing in the browser when the session dropped, so copy anything long out of the compose window first.
Does an AOL outage affect my third-party mail app?
It depends which component failed. If the mail servers themselves are unreachable, Outlook, Apple Mail and Thunderbird stop syncing and show a connection error. If only the web portal or its sign-in page is broken, apps holding an existing session keep working. An app that suddenly demands your password mid-outage is usually reacting to the authentication service, not to a changed password, so re-entering it repeatedly will not help.
How long do AOL outages usually last?
The history on this page is the better guide than any general figure, because it records what actually happened rather than what is typical. Consumer mail incidents tend to be measured in hours rather than days, and sign-in problems are often resolved faster than storage or delivery problems. The per-region table shows whether recovery arrived everywhere at once or rolled out gradually.

How we measure this

  • We request AOL'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 AOL 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 AOL 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