1. Home
  2. Companies
  3. AOL
  4. Seattle
AOL

AOL Outage Report in Seattle, Washington

Service-wide status: AOL

No problems detected

If you are having issues, please submit a report below.

Full Outage Map
  • AOL generated 0 outage signals in the last 24 hours around Seattle, including 0 direct reports.

AOL (America Online) is an internet portal as well as an internet service provider. As an ISP, AOL offers dial up internet through its AOL Advantage plans.

Problems in the last 24 hours in Seattle, Washington

AOL signals over the past 24 hours, with local activity from Seattle, Washington and nearby areas. The dashed baseline applies to service-wide activity, not to local outage confirmation.

  • Service-wide signals
  • Service-wide baseline

At the moment, we haven't detected any problems at AOL. Are you experiencing issues or an outage? Leave a message in the comments section!

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

AOL Issues Reports Near Seattle, Washington

Latest outage, problems and issue reports in Seattle and nearby locations:

  • lihcaS
    Sachil.eth (@lihcaS) reported from Redmond, Washington

    Overheard at work - one employee explaining to another employee what AOL is because they'd never heard of it. Then having to pause to explain the acronym AOL. Please, my knees and back can't take anymore.

  • Romestantc
    Charles M. Romestant (@Romestantc) reported from Seattle, Washington

    @VictorJServin @benedictevans For this second one apple does bring a solution with Apple TV. All in one place. Plus now the new smart tv app will help. Content it just parallels what we have with services. You had AOL, now you have fb Twitter insta etc...

  • bppalmer
    Binah Palmer (@bppalmer) reported from Seattle, Washington

    @finchfrii 1! Never had an AOL acct…

  • DonnaHo50584821
    Donna Houston (@DonnaHo50584821) reported from Grace, Washington

    @joangreeneaz @AOC It must have been a terrible experience for AOL! She knew about this a week before. Did she tell Pelosi? Why not? Pelosi had 6 messages regarding the riot. Did she stop the police from acting? She was the final word. Did she stop the police, guard etc from protecting the capital

  • film_girl
    Christina Warren (@film_girl) reported from Seattle, Washington

    Anyway, we both used that AOL account until BellSouth started up its ISP service in the fall of 1996. The password wasn’t changed and the account was active until sometime in 1998 when the county finally did an audit and canceled it.

  • Seattle_JC
    @Seattle_JC (@Seattle_JC) reported from Seattle, Washington

    @finchfrii Somehow, I never had an AOL account.

  • shortproof
    Jason Short (@shortproof) reported from Kenmore, Washington

    My father in law (86) tried to send an email for the first time in a while (his words). His AOL email stopped working. I had to explain that it was a service and he probably stopped it a long time ago.

  • NaFun
    Name cannot be blank (@NaFun) reported from Seattle, Washington

    @Slate Because he's targeting people that only recently dropped the mass email fwds from their aol accounts and they're used to bad graphics.

  • 508LauraMarie
    Laura Marie Rivera (@508LauraMarie) reported from Seattle, Washington

    @michaelharriot I can email you from the AOL account that I will never give up!

  • drbrain
    Eric Hodel (@drbrain) reported from Seattle, Washington

    @srbaker Given the examples of XMPP and the AOL messenger protocol before it we all knew this was never going to work anyhow

  • hoyty
    Hoyty (@hoyty) reported from Sammamish, Washington

    @cmwdotme @supersat Never seen a BlackBerry RIM950 with AOL branding. Was that used by people who worked for AOL or something?

  • crtr0
    Carter thinks #BlackLivesMatter (@crtr0) reported from Seattle, Washington

    @kirillzubovsky I never had an AOL email, I assume I'm on the BCC. This email should be triggering a dozen different hueristics.

  • Gerald95051
    Gerald O'Patrick (@Gerald95051) reported from Redmond, Washington

    @mmasnick @DevinCow Really ancient history. We gave away free Prodigy trial offer kits at Global Village Communication 30 years ago and the most common customer reaction was “why would anyone want this?” Or “I have a Mac. I use AOL.” Now I feel old. Get off my lawn, kid.

  • AdamEtchey
    Adam Etchey (@AdamEtchey) reported from Sammamish, Washington

    I once pretended to be a female with an AOL account around the time I wrote: "I want to meet the Aliens." "You never can tell about people can you?" ;; I want to meet my family, is my final conclusion. ;;

AOL Issues Reports

Latest outage, problems and issue reports in social media:

  • JCA_BelAir
    Rock Hard & Spew Facts (@JCA_BelAir) reported

    @jamusp Yeah, but their servers are all still running Win2K Server and Bob lost the database passwords when AOL took them over That's really why they won't change it--Vivian in the Mail Room has them written down on a PostIt stuck to the backside of the plotter printer, but don't tell anyone. It's hilarious watching Bob grumble and act like he's not still looking for it every morning while he tries to make his coffee last him until lunch since they caught him using a 2nd K-cup but he only bought into one share of the employee coffee pool Bob's a douche. He also manages their social media accounts, btw. Just sayin'

  • deebyman
    Deeby🇺🇸 (@deebyman) reported

    @MapQuest Who ******** uses Mapquest still, they must use AOL also

  • katiwa_4
    LKA (@katiwa_4) reported

    Someone decided the Adams Arcade lights are not working… with Ngong road matatus flying like they have no breaks … Aol yawa.

  • invalidkicks
    lnvalid.eth (@invalidkicks) reported

    @MapQuest Is this like AOL? wtf is a Mapquest

  • DaniilBuilds
    Daniil (@DaniilBuilds) reported

    AOL and Time Warner didn’t just pay for what the two companies were worth in January 2000. They paid for what they believed the two companies could become together. The announced merger was valued at roughly $350B, with AOL shareholders expected to own about 55% of the combined company. The logic was easy to understand: combine AOL’s internet business with Time Warner’s media assets and create value neither could generate alone. But there was a financial problem hiding inside that logic. Future synergies are uncertain. The merger closed in January 2001. SEC disclosures later put the acquisition cost at approximately $147B. Then came the accounting reckoning. In 2002, the combined company reported a $98.7B net loss, including a $54.2B goodwill impairment. That $54.2B was non-cash. It did not mean the company suddenly paid out $54.2B in cash. It meant the value previously assigned to acquired goodwill could no longer be supported at the same level. That distinction matters. When you pay upfront for future synergies, you are effectively putting a price on value that still depends on execution. If the synergies arrive, the premium can make sense. If they don’t, shareholders can end up carrying the cost. The most expensive synergy is the one you pay for before you prove it exists.

  • tb_can
    AlexB (@tb_can) reported

    I was a senior in highschool and was talking to a girl a year younger than me. One time she spent the night and I turned my computer on and hacked the company her dad owned. I found her dad's signature in the payroll files and pointed it out to her. You could tell she was uneasy about it but fascinated at the same time. By the time I graduated I had received three letters from AOL asking me not to hack their ****.

  • Babobooey
    Billszmafia (@Babobooey) reported

    @fekdaoui @bot mine barely made it past set up before shutting me down for 7 days. "Bot credits" according to Grok. Grok Bot is is still in AOL dialup stage. Needs work and some tweaks badly. Save you money

  • Manservant_H
    Augusto's Air-Taxi Service (@Manservant_H) reported

    @MapQuest Holy crap, I need to see if my AOL address still works

  • Paul__Walsh
    Paul Walsh (@Paul__Walsh) reported

    People keep asking why Apple allowed OpenAI to build a ChatGPT integration for Messages. Do get to the point, I don’t think Apple anticipated a company using the permissions required by ChatGPT specifically to read, analyse and store people’s Messages when the Messages app includes iMessage and not just SMS. The entire point of iMessage is that it’s rich media *and* end to end encrypted. The permissions OpenAI needs exist for legitimate software, and Apple warns people before granting them. Backup software needs Full Disk Access to back up protected files. Security software needs it to inspect files for malicious activity. Disk utilities need it to search, recover and manage protected files. It’s similar to WebView. It gave developers a way to display parts of an app that could change without requiring a new app release and App Store review, such as terms of service, privacy policies and other remotely hosted content. In 2014, I predicted developers would eventually use WebView across every major app, with some apps built almost entirely inside it. I also warned this would create a security problem because WebView had no protection against dangerous links or malicious code typically found on webpages. Developers could make a WebView look identical to the native app, so people wouldn’t know whether they were using the app itself or interacting with a website. Today, in-app security is a multibillion dollar industry because it’s obvious that opening links inside an app might not be as safe as it should be. Most predictions, especially in the context of digital risk, are not believed by a lot of people. But they become obvious eventually. Today, I’m saying OpenAI’s ChatGPT integration with Apple Messages is more dangerous for some people than almost anything else on the market. Of course someone can take screenshots and send them to the FBI, repeat something they were told, or deliberately share a private conversation. That completely misses the point. None of those things is equivalent to giving an AI service automated access to read, analyse and store entire message histories involving everyone someone communicates with. Comparing deliberate human disclosure with automated access at scale ignores the capability that makes this fundamentally different. And why it removes the main benefit of end to end encryption. I can’t comprehend how security professionals can defend anything that undermines the purpose of end to end encryption by saying "but encryption isn’t broken". Protecting messages while they’re being transmitted means very little if an agent can systematically read, analyse and store them before they’re sent or after they’re received. Apple permissions have legitimate purposes. This particular use of them is the problem. During the early 2000s, I advocated for browser extensions. During the mid to late 2000s, before the first iPhone when mobile web didn't exist, I advocated for mobile web instead of WAP. In 2015, I advocated for chatbot integrations across messaging platforms and business tools. I’m a developer advocate, an open standards advocate, child safety advocate, and privacy advocate. I co-founded 2 W3C initiatives, including the Mobile Web Initiative, where I was tasked with rewriting Tim Berners-Lee’s vision of "One Web". And was a significant contributor to 8 technical specifications, including the Web Content Accessibility Guidelines 2.0. I care about humanity. I don’t advocate for one thing in isolation from everything else. I’m a technical expert in specific areas with OSINT skills and 30 years across web, telecom, and mobile. 💡 I consider every stakeholder affected by open standards, technology, and legislation. Sometimes convenience justifies a privacy tradeoff. Sometimes privacy should take priority over security, and sometimes security should take priority over privacy. None of these should be treated as an absolute regardless of the consequences. In 2017, the PKI Consortium asked me to advise them privately and write about the impact DV SSL certificates and HTTPS Everywhere were having on anti phishing security. I faced fierce criticism from privacy advocates who argued that the connection should be encrypted even if the person on the other end was an impersonator. Those were their words. If you care, search for "Insecure Elephant in the Room". The fundamental reasons phishing works were the same when I was impersonated in 1996 when phishing was first discovered on the AOL network, the same when I wrote about it in 2017, and the same today. Now I have to argue with some security professionals defending something that undermines the purpose of end to end encryption. They need to look beyond the mechanics of software and encryption. Technology is an enabler. We need to consider human behaviour, how people will actually use a capability, and what happens when that behaviour occurs at scale. Also, the potential intent that goes beyond a website or privacy statement. I’ve faced this repeatedly over the years. Today, when I argue that government policies and age verification introduced in the name of online child safety and preventing child exploitation are actually surveillance measures, child safety advocates accuse me of not caring about children. This isn’t rocket science. Add AI to everything, even if you’re willing to accept the risks to yourself. But please don’t add AI in ways that undermine another person’s right to privacy or, depending on the context, their personal safety. Some people's lives depend on their ability to rely on end to end encryption. We're not talking about SMS. 💡Criticising the technology used to pursue an objective doesn’t mean opposing the objective.

  • nt570
    Sakshi (@nt570) reported

    @ANI bad adverstisement for AOL

Recent AOL reports in Seattle, Washington

Latest available direct user reports from this city and nearby areas. These are individual observations, not confirmed incidents or a complete outage history.

  • Seattle: E-mail
  • Seattle: E-mail

AOL detected incident history

These records describe service-wide increases in reported problems. They do not confirm an outage at every address. Recorded end times describe our detection window, not a provider-confirmed repair.

  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    Detection ended: (16 minutes)
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    Detection ended: (14 minutes)
  • Detected:
    Detection ended: (4 minutes)