AOL outages and service status in Valley Stream, New York

Problems in the last 24 hours in Valley Stream, New York

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

Live Outage Map Near Valley Stream, New York

The most recent AOL outage reports came from the following cities: Hewlett.

City	Problem Type	Report Time
Hewlett	E-mail	1 month ago
Franklin Square	E-mail	4 months ago
Floral Park	E-mail	7 months ago
Valley Stream	Total Blackout	7 months ago

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 Valley Stream, New York

Latest outage, problems and issue reports in Valley Stream and nearby locations:

• 
  Jay (@Nissan_620Z) reported 12 minutes ago from Inwood, New York

  I get shit for my aol email address...well it’s my name with no numbers or extra characters....so I’m keeping it til it disappear 🤣🤣

• 
  Chris Payne (@my3sonsJJM) reported 21 minutes ago from Franklin Square, New York

  @zack_hample never got the video from that guy if you have his contact could you reach out...good to see you yesterday...thanks from Chris n James....cmp105 is the address at aol

• 
  CINDY LU (@NCCindyLu) reported 23 minutes ago from Lynbrook, New York

  @AOL you're driving me nuts!! I can't sync with my iOS and outlook because you changed your settings!! I PAY for your services!!! I've done everything you suggest to address the situation and nothing works !! If you don't fix immediately I'm canceling my account 😡

• 
  CINDY LU (@NCCindyLu) reported 55 minutes ago from Lynbrook, New York

  @joshualebowitz @AOL Did this today. Still not working

AOL Issues Reports

Latest outage, problems and issue reports in social media:

• 
  CyberTLDR (@CyberTLDR) reported 2 minutes ago

  2/3 PortSwigger's Gareth Heyes showed it at Black Hat. One Outlook chain spoofs a Microsoft sign in and grabs the typed password. A Yahoo/AOL paste race leaks a login token. A Gmail chain exfiltrates a Slack token after prompt injection. #InfoSec #Privacy #CyberAttack

• 
  kpmaloyauthor (@kpmaloyauthor) reported 6 minutes ago

  @NikoleCallihan I never had an AOL address. lol

• 
  Mike Roberts (@Mikey_A_Roberts) reported 10 minutes ago

  NEVER Once did I EVER have AOL Account.... I didn't have an Email until I was 20 Why? Because **** people that's why...

• 
  Beth Fogle (@fogle003) reported 12 minutes ago

  @Matt_Pinner I never had an AOL address 🤪

• 
  Randall (@iamtandyfox) reported 12 minutes ago

  @Matt_Pinner I’ve never had an AOL account!

• 
  KeiSian (@blkmage) reported 13 minutes ago

  @aaliyahvtuber_ 19. Never actually logged in using AOL.

• 
  JackiO (@Jackio49) reported 16 minutes ago

  @oelma__ 19, never had AOL, didn't like waterbeds. lol

• 
  Aremu Azeez (@aremz04) reported 18 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?

• 
  tmnxeq (@tmnxeq) reported 19 minutes ago

  @0xljki obviously there was demand for bandwidth in '99, most people or businesses had none (this is kinda binary and you had to lay pipes throughout the whole country) operationally, this was a high margin business - you lay the pipe once (expensive capex) & but then can AOL CDs to every households, with virtually no marginal cost for addtl customer. "compute buyers have high margins" - brother what have you been smoking. xAI (admittedly now a compute seller) is losing gazillions - maybe that's why they went from buying/producing compute to selling. OAI/ANT have no published financials but spoiler, they are losing billions per year 1/2

• 
  jjc1234 (@jjc123424) reported 20 minutes ago

  @Matt_Pinner 19 - never had an aol account