Update, October 23, 2026: We corrected this post using Namecheap’s own write-up, published August 14 after service was restored. The data center was RadiusDC Phoenix, not PhoenixNAP as early reports on X said. DNS lookups kept working during the outage; DNS management was what went down. And incoming email was delayed, not lost. The original report below was written live on August 13 at 3:15 PM ET.
If you spent this morning refreshing a dead website, you are not alone. Namecheap, one of the largest domain registrars and web hosts in the world, has been down for more than six hours after a cooling failure at the Phoenix data center that houses a large chunk of its infrastructure. (Recovery ran into August 14.)
This one is worse than a typical hosting outage, because so many small businesses keep their domain, DNS, website and email in the same place. We will get to that. First, the facts.
Is Namecheap down right now?
Yes, at least partially. As of 3:15 PM ET on August 13, 2026, Namecheap has not declared the incident resolved.
The company’s most recent update said temperatures in the data center are falling and that customer services would begin coming back online around 3:00 to 3:30 PM ET, restored in stages rather than all at once. Expect a slow, uneven recovery rather than a single moment where everything works again.
You can follow the official updates on the Namecheap status page.
What caused the Namecheap outage
This was not a hack, a bad deploy, or a billing dispute. It was air conditioning.
Some of Namecheap’s essential systems run in the RadiusDC data center in Phoenix, Arizona. According to Namecheap’s write-up, a major storm caused the facility’s cooling systems to fail, temperatures around its equipment reached critical levels, and RadiusDC told Namecheap to take services offline. (Several early posts on X named PhoenixNAP; Namecheap later confirmed PhoenixNAP was not involved.)
In Phoenix. In August.
Once temperatures climb past a safe threshold, an operator has two options: let hardware run hot and risk permanently destroying it, or power things down on purpose and stay dark until cooling is restored. Namecheap chose the second one. That is the right call, and it is also why the outage lasted so long.
To their credit, CEO Hillan Klein has been posting detailed updates publicly all day rather than hiding behind a status page. His 2:20 PM ET update laid out exactly how they planned to bring everything back:
Temporary chillers were brought in and pointed at Namecheap’s part of the data center. Everything after that was a waiting game.
Timeline of the August 13 outage
| Time (ET) | What happened |
|---|---|
| Early morning | A storm knocks out cooling at the RadiusDC Phoenix data center, and temperatures climb to critical levels. |
| 8:35 AM | Namecheap declares an emergency, citing a cooling system failure. Its own support helpdesk goes offline with everything else. |
| 2:20 PM | Namecheap outlines a three-stage recovery: physical network devices, then virtual network devices, then customer services. |
| 3:00 PM | Customer services expected to begin coming back online, restored progressively. |
| Aug 14 | Namecheap publishes its write-up and says everything affected has been restored. |
What went down, and what stayed up
Nearly everything. The affected list covers:
- Namecheap.com and the account dashboard, so customers could not even log in to see what was happening
- Shared, VPS, and dedicated hosting, with sites returning 503 errors, loading slowly, or not loading at all
- EasyWP, Namecheap’s managed WordPress product
- DNS management, so nobody could change DNS records (DNS lookups themselves kept working)
- Email, including Private Email, shared hosting mailboxes, and email forwarding
- URL redirect management (existing redirects kept working)
- Hosting operations such as activations, renewals, and plan changes
- The support helpdesk itself, which forced Namecheap to route customer support through backup Microsoft Teams accounts
Domain auctions kept running, and so did DNS lookups and existing URL redirects. That was about it.
The part most people missed: everything in one place
Here is what made today unusually painful.
If your website is hosted at Namecheap, an outage there takes your site offline. Bad, but expected. That is the deal you make with any host.
The good news, per Namecheap’s later write-up: DNS zone resolution stayed up. A domain registered at Namecheap but pointed at a website hosted somewhere else kept loading. What went down was DNS management. Nobody could log in to change a record, move nameservers or fix anything, because the dashboard was down along with everything else.
The businesses that had the worst day were the ones with everything at Namecheap: the domain, the website and the email. When all of it sits with one company, one bad building takes all of it offline at once, and the control panel you would use to work around it is offline too.
That is the difference between an outage that costs you a morning and an outage that costs you a day of leads.
What to do if your site is still down
Honestly? Mostly wait. But do these four things.
1. Confirm it is actually Namecheap. Check the status page before you start changing settings. Panic edits during an outage cause more damage than the outage does.
2. Do not move your nameservers mid-outage. It feels productive. It is not. DNS changes take time to propagate, and you can easily end up broken for longer than if you had left it alone.
3. Tell people. Post on your Google Business Profile and social channels that your site and email are temporarily down and give a phone number. Customers forgive an outage. They do not forgive silence.
4. Check for missed messages. Namecheap says incoming mail to its servers was delayed rather than lost, because sending servers retry. Contact form notifications sent while your site’s mail was down can still go missing, so check your form plugin’s stored entries directly once you are back up, not just your inbox.
The real lesson: one company should not be able to take you offline
Namecheap is not a bad company. They communicated clearly, they made the right call protecting hardware, and a storm knocking out cooling in a third-party facility is not something you can code your way around. If you are deciding whether to stay, we looked at whether Namecheap is legit in more depth.
The lesson is not “leave Namecheap.” It is this: a lot of small businesses have quietly stacked their domain, their DNS, their hosting, and their email with one vendor, because it was simpler and slightly cheaper. That works fine right up until the day it does not, and then all four fail at once and there is no dashboard to log into.
Those are four separate jobs. They do not have to live in the same building.
How we set up client sites
We separate the layers on purpose, and today is exactly why.
Hosting is ours, not resold. Client sites run on servers we manage directly, primarily out of Raleigh, with global options through Vultr, AWS, and Google Cloud. When a registrar has a bad day, our clients’ servers are not in that building.
DNS runs through Cloudflare, not the registrar. Cloudflare’s DNS is free, fast, and spread across a global network. It also means the company you bought your domain from is not the same company that decides whether the world can find it. If you’re wondering whether Cloudflare itself can be trusted with that job, we went through whether Cloudflare is safe.
Backups run daily, automatically. Plus a manual backup before any update. Restoring is a decision, not an archaeology project.
We watch it. Uptime monitoring means we usually know before the client does, which is the whole point of paying someone to handle this.
None of that is exotic. It is just what happens when someone sets your site up to survive a bad day instead of setting it up in the fewest possible clicks.
Frequently asked questions
How long was Namecheap down?
Most of the day on August 13, with recovery running into August 14. Namecheap declared an emergency at 8:35 AM ET and began restoring services in stages that afternoon. Its August 14 write-up says everything affected was restored; it did not give a total duration.
Was Namecheap hacked?
No. A storm caused a cooling system failure at the RadiusDC data center in Phoenix, and Namecheap took systems offline on the data center’s instructions to protect hardware from heat damage.
Is my data safe?
Namecheap has not reported any data loss, and a controlled shutdown is specifically the move you make to avoid it. That said, if you do not have your own backups independent of your host, today is a good day to fix that.
My site is hosted elsewhere. Was it affected?
Probably not for visitors. Namecheap says DNS lookups kept working, so a domain pointed at another host kept loading. What you couldn’t do was change any DNS settings until Namecheap’s dashboard came back. Running DNS through a separate provider such as Cloudflare keeps that control in your hands.
Should I switch away from Namecheap?
Not reflexively. Every provider has an outage eventually, and the ones that publish honest updates during a bad day are usually the better ones. The change worth making is structural: stop keeping your domain, DNS, hosting, and email all in one place.
Need someone to look at your setup?
If today caught you off guard and you are not sure where your domain, DNS, hosting, and email actually live, we will map it out for you and tell you honestly whether it needs to change. No pressure, and no charge to look.
Call us at (919) 444-2005 or get in touch here. You can also read more about how our hosting works, or, if you are rethinking where your domains live, our breakdown of Cloudflare vs. GoDaddy domain pricing.
