Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
On Wednesday 17th March, globally used DNS provider Network Solutions experienced the dreaded downtime we all hope to avoid. Starting at 4am Eastern time and continuing through to Thursday 18th with still no resolution, it’s affected thousands of people across the world.
Who are Network Solutions?
Network Solutions are the 4th biggest domain registrar in the world, with nearly 7 million users worldwide. They offer a range of different online services, with specialised expertise in domains and web hosting, website optimisations and development, social media advertising, and SSL certificates.
How has Network Solutions downtime affected our customers?
For us, Network Solutions downtime has clearly affected our customers’ website downtime with customers in Canada, the USA, UK, Germany, and France all experiencing DNS type outages.
From our data, it seems that Network Solutions going down has affected people’s emails which will, unfortunately, prove massively detrimental due to the sheer number of emails people are sending now we’re in lockdown due to the Covid-19 pandemic.
On further investigation, we can see that we’ve sent more alerts by both email and SMS than average for website downtime to our user base, with an estimated 1,000 users suffering as a result of Network Solutions being down.
The bad news doesn’t stop there, unfortunately. Network Solutions also has a partner program, meaning that both bigger, well-known companies and smaller businesses will both be affected by this unexplained downtime. Other reported linked providers include register.com.
What are Network Solutions saying about their service issues?
Network Solutions was inundated on Twitter with complaints from users, many wanting to know when it would be back up and running. In a statement from their Twitter profile, they said:
As of 18th March AM, Network Solutions has experienced over 12 hours of service issues, which will undoubtedly have a huge impact on customers worldwide. They’ve had hundreds of comments on social media, more so today with the outage expected to have been fixed ready for their customers today.
It just goes to show that unfortunately, website downtime and outages happen to everyone, regardless of precautionary measures taken. That’s why it’s extremely important to have website monitoring in place to alert you as soon as website downtime happens.
Kat Holmes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026