AOL outages and service status in Bream, England

Problems in the last 24 hours in Bream, England

The chart below shows the number of AOL reports we have received in the last 24 hours from users in Bream, England and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

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 Bream, England

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

• 
  C Jones (@cejonesy) reported 7 minutes ago from Monmouth, Wales

  @AOLSupportHelp think my account has been hacked. I cant verify account as it has an old number. Please help

AOL Issues Reports

Latest outage, problems and issue reports in social media:

• 
  xnx (@xnx_material) reported 3 minutes ago

  @cabletvs so truee and then fully turning to dust when they've never heard the AOL dial up sound bee-doo-bee-bedowedowedowedo-kshhhhhh

• 
  NaughtyL1beral (@NaughtyL1beral) reported 3 minutes ago

  @DawnMartel5224 @SenMikeLee think ya mean AWOL toots. AOL is a dialup service.. remember? you've got mail? ring a bell? you righties. it'd be funny if our nation weren't falling apart bc of you nutjobs following a felon and adjudicated ******

• 
  Yossi Hasson (@yossihasson) reported 3 minutes ago

  Then on 1 December 1996, AOL went flat rate. $19.95. Unlimited. Average usage went from 7 hours a month to 23. The network collapsed. Customers sued. States opened investigations. The CEO had to publicly ask 8 million people to please use the internet less.

• 
  Christine (@arcticlady63) reported 3 minutes ago

  @Matt_Pinner 19 Never had an AOL address

• 
  Aremu Azeez (@aremz04) reported 8 minutes ago

  There's a line in The Lean Startup that stung when I read it last week: "learning" is the oldest excuse in the book for a failure of execution. Eric Ries tells the story of IMVU's first product. His team spent six months building an instant-messaging add-on, based on a genuinely smart-sounding strategy: piggyback on existing IM networks (AOL, Yahoo!, MSN), ride their network effects, spread virally through people's existing friend lists. Whiteboard-brilliant. They launched. Nobody used it. When they finally sat real customers down in front of the product, every assumption fell apart. Customers weren't scared of learning new software - the average teenager ran eight IM clients at once. They didn't want to chat with existing friends through avatars - they wanted to meet strangers. The "obvious" barrier the whole strategy was built around wasn't a barrier at all. Ries's point isn't "test more." It's sharper than that: in a startup, any effort that doesn't produce evidence about what customers actually want is waste - no matter how well it's executed. He calls the real version of this validated learning, to separate it from the after-the-fact story you tell yourself when something doesn't work. I'm sitting in a smaller version of that exact test right now with Owoye. One of the assumptions baked into the product is that WhatsApp and IG sellers want their invoices auto-matched to incoming payments. It sounds obviously useful from where I sit. But that's precisely the position IMVU's team was in - certain, and wrong, about what would remove friction for their customer. So this week will not be spent refining the feature. It will be spent in conversations with actual sellers, watching how they track who's paid right now - screenshots, memory, WhatsApp scrollback - before deciding whether "auto-match" solves their problem or just mine. The uncomfortable question worth asking about your own product this week: is the thing you're building solving a problem your customer has, or a problem you have with how your customer works?

• 
  Tony Peterson (@soflinvest) reported 8 minutes ago

  @Matt_Pinner Never had a waterbed. I still use my original AOL email address.

• 
  astrosteve (@astrosteve) reported 14 minutes ago

  Fun fact: My computer was so close to being able to not run the original EQ well that if I had anything else running, it would stutter and freeze up. When I had to use AOL for about 2 months, this was a problem because the AOL client had to be running and made EQ stutter.

• 
  The Stairway to Retro 💾🕹️ (@StairwayToRetro) reported 18 minutes ago

  @RetroTechorDie At a stretch, I could understand them wanting to shut down the Nina network if the Italians plan to revive AOL chat. But going after someone who makes a video, especially one with a positive tone toward the AOL brand, makes absolutely no sense.

• 
  JR, Jr (@JohnFRyan1) reported 22 minutes ago

  @oelma__ 19/20. I never used AOL

• 
  jescatsrule (@janejanekitt) reported 24 minutes ago

  @oelma__ I still have an AOL address. The only thing I never used was a waterbed.