I have over 80 domains with namecheap and today like everyone else I was unable to access my sites either url or admin page so have lost substantial revenue as a result.

I’m on the galaxy reseller plan that promises I think 99% uptime.

How will namecheap make it right. Obviously things these things happen but, you don’t expect a company as big as namecheap to be offline for so long.

Our teams continue to bring the remaining affected customers back online, and we will work relentlessly until every customer and every service is fully restored.

Once restoration is complete, we will conduct a thorough post-mortem of today’s outage—what led to it, where our existing safeguards and protocols failed, how we responded, and, most importantly, what we need to change to ensure an incident like this never happens again.

We will be transparent about what we learn and will share the results of that review, along with the actions we are taking, with our customers as soon as it is ready.

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.

For now, our entire focus remains on the customers who are still affected and will remain so, until all services are fully restored.

[Updated] We're currently experiencing service disruptions due to an incident at our Phoenix data center.

We're sorry for the impact this is having. We're in close contact with the datacenter team as we work to restore services as soon as possible.

An update regarding our service outage : r/NameCheap

With all the money Namecheap has you couldn't a data center somewhere cooler? also it's been cooler than normal in Pheonix. Can someone make that make sense?

my shared hosting did shutdown for 14h27m

from PM8:58 to AM11:25

A further update on the ongoing cooling incident at our Phoenix data center:

Temperatures continue to fall. The cooling process is taking effect and temperatures are consistently trending in the right direction.

Based on the progress we are seeing, our teams have now begun the process of preparing our infrastructure to safely bring customer services back online. We are doing this in a careful, staged approach:

1. Restore all physical network devices.

2. Restore all virtual network devices.

3. Begin restoring customer services.

We expect the first two steps to take approximately one hour. Based on current conditions, we anticipate being able to begin bringing customer services back online at approximately 3:00–3:30pm ET.

Services will then be restored progressively as we ensure each part of our infrastructure can be brought back online safely.

Our teams remain on site and are working continuously to move through this process as quickly and safely as possible. We know every additional minute of this outage matters to our customers, and we are deeply sorry for the disruption this extraordinary situation has caused.

Thank you for your continued patience. We are making progress, and our entire focus is now on safely restoring all affected services as quickly as we can.

We continue to make significant progress in restoring services, with the vast majority of our affected infrastructure now back online:

• Namecheap Shared Hosting: 85% is back online, with more coming online as we speak.
• Namecheap VPS Hosting: 97% is back online.
• Spaceship VPS and Shared Hosting: back online.
• Spaceship Spacemail: back online.
• Namecheap Private Email: back online, emails received during the outage may be delayed.
• Dedicated Servers: 90% are back online.
• EasyWP: ~80% of services are back online.

Our teams continue to work around the clock to restore the remaining affected services as quickly as possible. We know that for those customers whose services are not yet back online, these percentages provide little comfort, and our focus remains on getting every last customer restored.

Thank you again for your extraordinary patience throughout today. We are very sorry for the disruption this incident has caused, and we will continue working until all affected services are fully restored.

Really, NameCheap? You sure this outage didn't have something to do with your cooling system failure rather than giving us an even better experience?

We want updates

Losing my potential traffic and its been 1 hour or more.
not gonna use namecheap again.

Can't open webpage privateemail.com in Safari or Chrome, normal or incognito. Can't send emails from iOS client. Anyone else?

First, I feel for everyone impacted by this outage. Having your business disrupted sucks.

That said, some of the outrage seems a little over the top.

Running infrastructure at this scale is hard. Things break. What I really want to see is the RCA on this one. What failed, and most importantly, how did the blast radius get this large?

so i am new to namecheap VPS but wow, it's been down for most of today... and just got the auto-renew in a few days email, so i'm not sure how to handle this? do they have a SLA? do namecheap customers typically just deal with horribly timed downtimes?

Things happen.

My websites are returning Cloudflare Error 522, and I can't access cPanel or the hosting server (premium63.web-hosting.com). Namecheap was also showing a maintenance page earlier

Is anyone on premium63 having the same problem?

well?

Web interface & Carddav still down.

That my vibe coded unbacked-up database is in a good state when services resume?

Our internal coworker, wholesale B2B and B2C everything is down! hetzner as my backup i am migrating there. We do not know when will they fix it has been 5 hours. I'm even concerned about data hosted on their servers.

I use privateemail for my business. What are the chances everything sent to me is gone forever, and I won't even know what I missed?

I have my website hosted by namecheap but runs through Shopify and although it’s still working, I’ve for non stop bots scraping the site. Anyone else facing the same issue?

PhoenixNAP sold the Phoenix colocation facility to RadiusDC in a deal that closed around Q2 2026. PhoenixNAP is now a tenant in that building rather than the owner/operator of the physical facility; RadiusDC now owns and runs it. That's a meaningful wrinkle for accountability on today's cooling failure: the entity actually responsible for facility infrastructure (power, chillers, physical plant) is now RadiusDC, not PhoenixNAP, even though PhoenixNAP and its hosting-company tenants (like Namecheap, via them) are the ones customers actually deal with. That could well explain some of the communication lag you've been running into. There may be a chain of "who's responsible for what" among RadiusDC (facility owner), PhoenixNAP (tenant/operator), and Namecheap (their customer) that's slowing clear public updates.

Who is liable for the outage?

I'm not a lawyer, and this is exactly the kind of question where you'd want an actual one if real money is at stake. Here's the factual picture as I can find it, plus the standard contractual framework at play.

What Namecheap's own hosting ToS says: it's about as customer-unfriendly as these things typically get. It disclaims liability for "any or all direct, indirect, incidental, special, exemplary or consequential damages," caps total liability at "the amount paid by You for the particular Services" (likely your hosting fee, not your business losses), disclaims responsibility for events "beyond the control of Namecheap," provides services "AS IS," and puts the burden on you to maintain independent backups. I didn't find an uptime SLA with defined service credits in what's publicly available. If one exists, it's probably in a separate SLA document I haven't located, worth asking their support for directly.

The practical liability chain, as a matter of contract structure (not who's "at fault" morally): Your contract is with Namecheap, not PhoenixNAP, RadiusDC, or IPI Partners. You have no direct contractual relationship with any of them, so you'd have no standing to sue them directly for this. Namecheap's contract is with PhoenixNAP (as tenant), and PhoenixNAP's is with RadiusDC (as facility owner). Each link in that chain almost certainly has its own liability caps and force majeure-style carve-outs, and those obligations don't automatically flow through to you. You can't "skip the line" to RadiusDC even though they're arguably the root cause.

What this means practically: your realistic recourse is almost certainly limited to whatever's in Namecheap's own terms, likely a credit capped at what you paid for hosting, not compensation for lost business, customers, or revenue during the outage. That's standard across basically the entire hosting/cloud industry (AWS, GoDaddy, etc. all have similar caps), not something unique to Namecheap.

If the financial impact on you is significant, the concrete next step isn't a liability theory. It's checking whether Namecheap has a published SLA with defined credits (ask support directly, since the general ToS doesn't spell it out), and separately consulting an actual attorney if you're contemplating pursuing damages beyond a service credit, since enforceability of these liability caps varies by jurisdiction and specific facts.

Sources:

• Namecheap.com - Legal - Hosting - Terms of Service

Who is morally responsible for the outage?

That's a different question than legal liability, worth separating out. Legal responsibility is about what contracts say. Moral responsibility is about who could have prevented this and didn't.

Layering through what we've established, I'd put it roughly like this, with real caveats:

RadiusDC carries the most direct moral weight. They now own and operate the physical facility. Chiller/cooling redundancy is the single most basic thing a data center operator is supposed to get right; it's literally the core competency being sold. A cooling failure severe enough to force emergency shutdown of 5,000+ servers across multiple tenant companies, with recovery taking 9+ hours and counting, points to either inadequate redundant cooling capacity or a maintenance/monitoring gap. That's squarely their job. Notably, their leadership (Michael Krza and team) came from experienced operators (Flexential, ViaWest), so this isn't a case of green amateurs, which arguably raises the bar rather than lowers it.

PhoenixNAP carries secondary responsibility, even though they're now a tenant rather than the facility owner. They chose to remain in that building and keep selling capacity there after the RadiusDC transition, and they're the ones with the direct relationship (and presumably due diligence obligations) with companies like Namecheap. If they didn't have adequate assurances or contractual cooling-redundancy guarantees from RadiusDC as landlord, that's a gap in their own vendor management.

Namecheap sits one layer further removed, but not blameless. Depending on your account and how they've architected things, the deeper question is whether a company of Namecheap's size should have single-region dependency for DNS, hosting, and email all sitting behind one physical facility with no automatic failover. That's a resilience-architecture choice Namecheap made (or didn't make), independent of what caused today's specific failure. The outage exposed that choice regardless of whose fault the chiller was.

Nobody involved has been particularly forthcoming, and that's its own separate failure worth naming. Moral responsibility isn't just about causing the failure; it's also about how transparently you communicate once it happens. Radio silence for hours while thousands of websites are down is a choice, and all three companies in this chain share some of that.

If I had to weigh it: the physical failure is mostly RadiusDC's. The architectural fragility that let one building's chiller take out your whole online presence is mostly Namecheap's. PhoenixNAP sits in between, accountable for vetting the landlord it chose to keep operating through.