AOL outages and service status in Dungannon, Northern Ireland

Problems in the last 24 hours in Dungannon, Northern Ireland

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

Latest outage, problems and issue reports in social media:

• 
  Rosemary🇨🇦 (@rmmh1898) reported 4 minutes ago

  @Matt_Pinner Never had AOL or a waterbed but I still have a cheque book and a typewriter.

• 
  neuroplasticity (@macewan) reported 7 minutes ago

  @WTForeRight @Matt_Pinner 19 - never had aol but I was here during their disk moment.

• 
  matt stevens (@mattst73) reported 9 minutes ago

  @distributedkv Once compute is available we will leave this current token war setup. This is much like the AOL charge by the minute internet back in the 90's. Then some brave souls that where smaller just said unlimited internet for 20 bucks a month. Then the communication companies offered DSL and access to the service for $50 a month. More than likely we will have some small data centers maybe 10 racks serving a neighborhood. Do you really need 2 trillion perimeters to write posts, summarize emails?

• 
  Thom Sieloff 🇺🇸 (@RealThomSieloff) reported 14 minutes ago

  @Matt_Pinner I never had an aol address.

• 
  Shane 💬 (@Technimentals) reported 14 minutes ago

  @HayleyWazEre Long story short, AOL and the largest business-to-business Internet Service Provider at the time (UUNET), were both headquartered here. Companies started laying a lot of fiber. This has been going on for 25 years here. They take a lot of water and power.

• 
  Andreux👨🏿‍💻 (@and_reux) reported 15 minutes ago

  a researcher just showed CSS alone can escape the boundaries of an email and mess with the webmail interface itself across Outlook, Gmail, Fastmail, Proton, Yahoo, AOL: fake login screens, stolen tokens, hijacked UI actions, even manipulated AI assistants that read your inbox. no JS required

• 
  Ollie Forsyth (@ollieforsyth) reported 19 minutes ago

  This Week in Startups: August 3rd It's a wild one 👇 Airtable gets acquired by Bending Spoons for $1.28B. Once valued at $11B, now picked up at a fraction, the third brand-at-a-discount play this year after AOL and Eventbrite. Google’s AI leadership reshuffle. Demis Hassabis moves from CEO of DeepMind to Alphabet Chief Scientist. Nikita Bier steps down from X as Chief Product Officer. Revolut founder in line for a mega payout. Nik Storonsky’s incentive package could push his fortune to £57B if Revolut hits $200B valuation, not far-fetched after its latest secondary at $115B! SpaceX posted its first quarterly earnings. Revenue reached $7.8B (nearly 2x YoY, beating estimates).

• 
  Robbie Wade (@WadeRobbie1969) reported 20 minutes ago

  @Matt_Pinner 19. Never had a AOL address

• 
  RealCoachI (@Coach_I5) reported 22 minutes ago

  @ChrisMizTV @CFBDirect Man, i’ve been just playing offline while watching movies and whatever because i don’t dare risk my Dynasty while watching, but it is just sad. The entire mode is slow and clunky. I feel like i’m on AOL in 1996.

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