Starlink and Yahoo Mail Outages: Business Continuity Lessons

What happened in the July 2025 Starlink and Yahoo Mail outages, and the practical business continuity steps any company can take to avoid being stuck.

On 24 July 2025, two big services failed on the same day. Starlink's satellite internet went down worldwide for about two and a half hours because of an internal software failure. Yahoo Mail also had a widespread outage, with users locked out by a "Temporary Error 15" message.

Neither was a cyberattack. Both are useful business continuity lessons: any single provider can fail, so plan for it.

What happened to Starlink

Starlink is SpaceX's satellite internet service. On the afternoon of 24 July 2025 (US Eastern time), users around the world lost connection.

What reputable reporting confirmed:

Cause: Starlink's engineering vice-president said the outage came from failures in key internal software services that run the core network.
Duration: About 2.5 hours before the network mostly recovered.
Scale: Downdetector logged a peak of about 61,000 reports, and internet monitor NetBlocks said Starlink's overall connectivity fell to about 16% of normal levels.
Response: Elon Musk apologised publicly and said SpaceX would fix the root cause.

The key point: the satellites were fine. Software that coordinates the network failed, and that took everything down at once.

What happened to Yahoo Mail

On the morning of 24 July 2025 (US time), Yahoo Mail users began reporting they could not log in. Many saw "Temporary Error 15". Some could not send or receive email. Downdetector reports climbed into the thousands, and AOL Mail, run by the same parent company, also had problems.

I could not find an official explanation of the cause from Yahoo, so I won't guess at one.

The business continuity lessons

Business continuity means keeping the business running when something breaks. Here are the lessons that apply to a Klang Valley office or a Penang factory just as much as to a big enterprise.

1. Find your single points of failure

A single point of failure is one thing that, if it breaks, stops the work. Make a simple list:

How do we connect to the internet?
How do we send email and messages?
How do we take payments?
Where are our files and systems hosted?

If any answer has only one option, that is a risk.

2. Have a second internet link from a different path

Many businesses now use satellite internet as a backup. The Starlink outage shows a backup can fail too.

Good redundancy means two links that don't share the same weak point. For example, fibre from one provider plus 5G or satellite from another. A dual-WAN router can switch between them automatically.

3. Don't run everything through one email account

A shop that runs all customer orders through one free webmail box is exposed. Practical steps:

Use a business email service on your own domain, so you can switch providers if needed.
Keep a second channel for customers, such as WhatsApp Business or a phone line.
Save key contacts somewhere outside your email.

4. Write a one-page outage plan

It does not need to be fancy. It should answer:

Who decides that we are "in an outage"?
How do staff talk to each other if email and chat are down?
How do we tell customers?
What can we keep doing offline (paper orders, manual receipts)?

Print it. A plan stored only in the cloud is no use when the cloud is down.

5. Test it

Once a year, unplug the main internet link for an hour during a quiet time. See what breaks. Fix it. This is cheaper than finding out during a real outage.

6. Watch your providers

Bookmark your providers' status pages and follow their official accounts. Third-party sites like Downdetector help you check quickly whether the problem is yours or theirs.

7. Expect software failures, not just storms

Both outages came from systems failing, not physical damage. Ask your key vendors how they handle bad software updates. Do they roll changes out slowly? Can they roll back quickly?

How this fits with security planning

Outages and cyberattacks need many of the same things: backups, a contact list, a decision-maker and a plan to tell customers. If you build a cyberattack response plan, reuse it for outages. Pair it with immutable backups so your data survives either kind of event.

Good monitoring also helps. You want to know a service is down before your customers tell you.

My take: these business continuity lessons are not about avoiding Starlink or Yahoo. They are about never relying on just one of anything that matters.

Quick answers

What caused the July 2025 Starlink outage?

Starlink said it was a failure in internal software services that operate its core network. It was not a cyberattack, and service mostly recovered after about 2.5 hours.

What is Yahoo "Temporary Error 15"?

It is a login error users saw during the 24 July 2025 outage. Yahoo did not publish a detailed public cause that I could find.

Is satellite internet a good backup for my business?

It can be, as long as it is not your only backup. Pair it with a link from a different provider and technology, such as fibre plus mobile data.

What is the simplest first step in business continuity?

List the services you can't work without, and note which ones have no backup. That list tells you what to fix first.