On August 13, Namecheap went down. Not briefly, not partially. For the better part of 28 hours, websites, email, DNS management, and even the support helpdesk were all offline after a cooling failure at the company’s Phoenix data centre.
If your site runs on Namecheap hosting, or your domain is registered there and still points to their nameservers, you almost certainly felt it. Here is what actually happened, how Namecheap responded, and what the incident tells you about the risks of putting too many eggs in one basket.
What Caused the Outage
A major storm hit Phoenix on the night of August 12, causing utility power interruptions at the RadiusDC: Phoenix data centre where Namecheap runs a significant portion of its core infrastructure. The storm knocked out the facility’s cooling systems.
When temperatures inside the data centre reached critical levels, RadiusDC instructed Namecheap to take its servers offline. That was the right call. Running servers in a overheating environment risks permanent hardware damage and potentially much longer downtime. A controlled shutdown is painful, but it beats a hardware failure that takes weeks to recover from.
Worth noting: early posts on social media misidentified the facility as PhoenixNAP. Namecheap has since issued a correction. The operator was RadiusDC, not PhoenixNAP, which had no involvement in this incident.
What Went Down and for How Long
The first status update went out at 8:35 AM EDT on August 13. Full resolution was confirmed at 1:00 PM EDT on August 14. That is just over 28 hours from first alert to all-clear.
Here is what was affected:
- Namecheap.com and account dashboard: customers could not log in for most of the outage
- Shared, VPS, and Dedicated Hosting: sites offline or returning errors
- EasyWP: the managed WordPress platform was fully disrupted; some sites on two specific alias records remained down until 3:50 AM on August 14
- DNS management: customers could not update DNS records (though DNS resolution itself stayed up)
- Private Email: sending and receiving both affected across legacy and new plans
- Support helpdesk: live chat and email support went down with everything else; staff redirected customers to Microsoft Teams
One piece of good news on email: incoming messages were not lost. When a receiving server is temporarily unavailable, sending servers retry delivery. Messages arrived late, but they did arrive.
Why It Affected Sites Hosted Elsewhere Too
This is the part that catches people off guard. If your domain is registered at Namecheap and you have not changed its nameservers, your domain resolves through Namecheap’s DNS infrastructure. During the outage, DNS management was down.
DNS zone resolution did remain available throughout, which means most domains continued resolving. But the incident highlighted a real dependency: if Namecheap’s DNS infrastructure had gone fully dark, sites hosted anywhere in the world would have gone offline just because the domain pointed at Namecheap’s nameservers.
The short version: your hosting and your domain registrar are separate risks. An outage at one can bring down the other’s work.
The Tier 3 Problem
Namecheap described the RadiusDC facility as a Tier 3 data centre, “designed with a high level of redundancy.” That framing will frustrate anyone who just spent 28 hours staring at a dead website.
The thing is, Tier 3 certification means a facility can handle planned maintenance without downtime and can survive single points of equipment failure. It does not mean it is immune to every possible external event. A storm severe enough to knock out all four cooling units simultaneously is outside what most redundancy designs account for.
Namecheap called it an “extremely unusual incident” and the first of its kind in 25 years at that facility. That is probably true. But the underlying architecture still put critical control systems in a single physical location, and that is worth understanding regardless of how rare the trigger was.
An analyst writing about the outage described it as a textbook single point of failure: the central control plane that authenticates users, processes API requests, and routes traffic was concentrated in Phoenix. When Phoenix went down, everything that depended on it went with it.
How Namecheap Handled It
Honestly, better than most.
CEO Hillan Klein posted live updates on X throughout the incident and signed the service outage blog post himself, rather than putting out a generic PR statement. The status page had timestamped updates roughly every one to two hours across the full duration. The cause was disclosed clearly and early. The correction about RadiusDC versus PhoenixNAP was published without delay.
Klein’s statement is worth reading directly: “I, along with our whole team, are genuinely sorry for the outage today and for the impact it has had on so many of our customers. We failed you today. We know that trust is earned through our actions, not our words, and we will work every day to regain the trust we lost.“
That is an unusual level of candour for a company of Namecheap’s size. Most hosts would have published a single status update and moved on.
That said, two things fell short. The support helpdesk itself was taken down by the outage, leaving customers without any way to reach the team at the exact moment they needed help most. Redirecting to Microsoft Teams accounts was a fallback, not a solution. And as of the time of writing, no compensation has been announced and no post-mortem report has been published, despite Klein’s public commitment to both.
What This Means for Your Site
A 28-hour outage at a host managing 18 million domains is a reminder of a few things worth acting on:
- Backups live off your host. If your only backup is stored on the server that just went down, it is not really a backup. Use a separate service or download copies locally. Our WordPress backup guide walks through the options.
- Your registrar and your host are separate risks. If you host elsewhere but your domain is registered at Namecheap, you still had a dependency on their infrastructure. Consider whether that exposure makes sense for your situation.
- Premium DNS is a real thing. Moving your nameservers to a dedicated DNS provider like Cloudflare or a premium DNS service means a hosting outage does not automatically become a DNS outage too.
- Check your host’s SLA. Most uptime guarantees cover compensation in the form of account credit, and the threshold is usually much higher than 28 hours of downtime would trigger. If you have not read yours, now is a good time.
If you want a closer look at Namecheap’s hosting products, reliability record, and what you actually get for the money, our full Namecheap review covers the detail.
Frequently Asked Questions
Is Namecheap back online after the August 2026 outage?
Yes. Full service was restored at 1:00 PM EDT on August 14, 2026. The final services to come back were some EasyWP sites, which were fully operational by 3:50 AM EDT on August 14.
Did the Namecheap outage cause data loss?
Namecheap has not reported any data loss. The deliberate shutdown was specifically intended to protect hardware from damage. Email that could not be delivered during the outage was not lost; sending servers retry delivery and messages arrived once services were restored.
Will Namecheap compensate customers for the outage?
No compensation has been announced as of the time of writing. CEO Hillan Klein committed to publishing a full service outage and promised to share the actions Namecheap will take to prevent a repeat incident.
Why did sites hosted elsewhere go down because of the Namecheap outage?
If your domain is registered at Namecheap and uses their default nameservers, it relies on their DNS infrastructure to resolve. During the outage, DNS management was affected. DNS zone resolution stayed up for most of the incident, but the dependency on Namecheap’s nameservers created a risk for sites hosted on other platforms.
