AOL outages and service status in Glen Allen, Virginia

Problems in the last 24 hours in Glen Allen, Virginia

The chart below shows the number of AOL reports we have received in the last 24 hours from users in Glen Allen, Virginia 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 Glen Allen, Virginia

Latest outage, problems and issue reports in Glen Allen and nearby locations:

• 
  JeyJohnson akaStinel (@JjGoodTimez) reported 29 minutes ago from Laurel Village, Virginia

  @AOLSupportHelp 🙄🙄🙄 I can pass any verification you throw at me ! Y’all not trying to help me. I need this email address back! Don’t worry about it... my lawyer will be in contact soon enough.

• 
  Muva Myra 💋 (@_MyraX) reported 52 minutes ago from Dumbarton, Virginia

  Bye , I couldn’t get past them asking about AOL . Oh my ****

AOL Issues Reports

Latest outage, problems and issue reports in social media:

• 
  BAT-SALEH (@BATVRABEL) reported 5 minutes ago

  @Quadripolar_B I was in one in the AOL days. I dominated that **** until they asked me to run it. I still have some of the shows I wrote. I can't believe I ever had the imagination and attention span for that. I gave myself carpal tunnel.

• 
  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?

• 
  Scottx70 (@scottx70) reported 9 minutes ago

  @CJGRISHAM Courtesy of Larry Johnson STFU Here is the heart of the problem. The Combat Logistics Force today numbers about 34 ships — a figure that has stayed essentially flat for well over a decade. On paper, stability. In practice, a slow hollowing, because the demands on that force have grown while its most capable ships have disappeared. Around 2010, the Navy operated all four of its Supply-class fast combat support ships. Today only two remain. In the mid-2010s the Navy inactivated two of them into reserve to save roughly $30 million a year each in operating costs — a decision that looked reasonable on a spreadsheet and looks indefensible from the deck of a hungry ship. The reason it bites is arithmetic: replacing the combined capability of one fast support ship typically takes an oiler plus a dry cargo ship — two hulls, two crews, two schedules — to move the fuel, ammo, and food that one ship used to carry in a single package. Cut the fast support fleet in half and every sustained single-carrier mission becomes harder to feed. The rest of the force is aging underneath the flat headline. The Henry J. Kaiser-class oilers that form the backbone date to the 1980s and are being retired faster than their replacements arrive. The new John Lewis-class oiler program is meant to recapitalize the fleet with some twenty ships, but the lead ship only delivered in 2022 and just one was fully operational by mid-2025. The Navy’s own newer answer — a smaller, more numerous “light replenishment oiler,” the T-AOL — does not begin construction until FY2027 and will not arrive in numbers until the 2030s. The analytic consensus across defense researchers is blunt: the logistics force is not enough, and not fast enough, for the demands now being placed on it.

• 
  Blake Hansen (@BlakesLLAIS) reported 9 minutes ago

  @DChadwickAuthor 19. Never had an AOL account.

• 
  Dana Pico (@Dana_TFSJ) reported 13 minutes ago

  @BostonBridget .@AOL is 36 now; even if she chose to thaw out a few, and have them fertilized and implanted, how old would she be when she had her first pregnancy? Every extra year increases the odds for a bad pregnancy and disabled child. @JillFilipovic

• 
  Beholder242 (Brett T) (@beholder242) reported 13 minutes ago

  @ReavingMango @MagsNoctis 18. Never used AOL or a waterbed.

• 
  FRESH™👻👑 (@PalmBeach561) reported 13 minutes ago

  I remember back when we had aol chat rooms and would just talk **** about everything and any thing

• 
  African$avage (@SHTOOPIDTHICK) reported 15 minutes ago

  @BankheadOunce lol and aol slow as hell dial up

• 
  retired (@Helbreak07) reported 18 minutes ago

  @LuluTeala 19. It was AOL for me. I got a water bed in 2006 when I rented a cheap furnished apartment in Alaska. I ended up sleeping on the couch, couldn't stand the damn'd thing

• 
  Lilith Hunter (@hunter_lilith) reported 19 minutes ago

  @JustJJSC they realized CONTENT is king back when AOL bought Time Waner. Some were slow to adapt, but Comcast bought NBC/Universal, Disney bought ABC, CBS bought Paramount/or vice versa, and a few new were created, netflix, az prime, to make content. The said FU. added commercials.