Websites, business email, and DNS for a large slice of Namecheap's customer base went dark on 13 August 2026 after the cooling system at the Phoenix data center hosting the company's core infrastructure failed. By Namecheap's own count, more than 5,000 servers were taken offline — not by the failure itself, but by a deliberate shutdown to stop hardware cooking in a data hall that had lost its chillers.
The blast radius is wider than that of most outages at a hosting provider because Namecheap's authoritative DNS servers sit within the same failure domain. That means sites hosted elsewhere broke too, as long as their nameservers pointed to Namecheap. And because the support helpdesk lives in that same building, customers could not open a ticket to ask what was happening.
What Is Actually Broken
Namecheap's status post explicitly lists the affected services. This is the full scope as the company described it:
| Service | Reported impact |
|---|---|
| namecheap.com | Site under emergency maintenance; account dashboard unreachable |
| Shared, VPS & Dedicated hosting | Sites unavailable, slow, or returning 503 errors; cPanel/hosting panel inaccessible |
| Namecheap DNS | Zone resolution and zone management unavailable |
| EasyWP | Entire platform affected — EasyWP.com, the dashboard, and customer sites |
| Private Email | Intermittent; incoming and outgoing delivery both disrupted |
| Mail forwarding | Free Email Forwarding and Domain Privacy forwarding both hit |
| URL Redirect | Affected on both BasicDNS and PremiumDNS |
| Support helpdesk | Unable to process email tickets; live chat pushed as the fallback |
| Hosting operations | Activations, renewals, and plan changes are being processed with delays |
Independent outage trackers put the user-reported breakdown at roughly 60% hosting, 30% domains, and 10% cloud services, with reports arriving from Mexico, Vietnam, Uruguay, and across Europe — consistent with a single-origin failure rather than a regional network problem. Live user reports are aggregated on Downbits' Namecheap status page, which also lets you file a report if your own services are affected.
Timeline of the Namecheap Outage
All times below are UTC, with Indian Standard Time in brackets. The sequence matters because the data center operator flagged the problem roughly two hours before Namecheap told customers anything.
| Time (13 Aug 2026) | Event |
|---|---|
| 10:28 UTC (15:58 IST) | PhoenixNAP opens an incident titled “Higher ambient temperature in the Phoenix DC”, noting no critical service impact |
| 11:28 UTC (16:58 IST) | PhoenixNAP moves the incident to Identified, warning that the equipment may reboot |
| 11:42 UTC (17:12 IST) | Namecheap posts a separate notice about EasyWP servers being unreachable |
| ~12:20 UTC (17:50 IST) | Third-party trackers register the start of mass user reports |
| 12:35 UTC (18:05 IST) | Namecheap publishes its emergency maintenance status post, citing a power outage |
| ~12:40 UTC (18:10 IST) | Namecheap confirms the disruption on X; states there is no ETA |
| 13:04 UTC (18:34 IST) | PhoenixNAP reports its facilities team is working with an on-site vendor, still no ETA |
| Later, 13 Aug | CEO Hillan Klein states 2 of 4 chillers are back, temperatures are dropping, and a third is expected within roughly three hours |
Power Outage or Cooling Failure? The Two Accounts Do Not Match
This is the part worth reading carefully, because Namecheap has given customers two different causes.
The status post and the company's X account both attribute the incident to “emergency maintenance due to a power outage affecting our datacenter in Phoenix”.
Namecheap CEO Hillan Klein, posting publicly the same day, described something different: an infrastructure incident at PhoenixNAP where “the facility has suffered a failure of its cooling systems”. He said Namecheap then chose to power services down to prevent overheating and long-term hardware damage.
PhoenixNAP's own status page supports the CEO's version, not the status post's. Its incident is titled around ambient temperature, and its updates describe chillers and a cooling vendor — there is no mention of a utility power failure.
The two are not mutually exclusive; a power event can take chillers offline, and a chiller failure can force a controlled power-down. But the distinction is not academic for customers. A power outage implies infrastructure that came back when the lights did. A cooling failure implies a thermal shutdown, which is slower to recover from, because you cannot safely repower thousands of servers until the hall has actually cooled. That is the better explanation for why this ran for many hours rather than minutes.
No, There Is No Confirmed DDoS Attack
Several outlets and aggregator sites have published headlines pairing this outage with a distributed denial-of-service attack. Some framed it as Namecheap being hit by a DDoS and a power outage simultaneously.
Cyber Kendra checked every primary source available for this incident: Namecheap's status post, its X account, its CEO's public statement, and PhoenixNAP's status page. None of them mentions a DDoS attack. Every official account points to a facility-level cooling or power problem.
The DDoS framing appears to be a carryover from a separate Namecheap incident in February 2024, when the company confirmed a DDoS affecting its main site and support systems. It has also experienced DDoS-related disruption on a dedicated server earlier in 2026. Those were real events. They are not this one.
Some customers on social platforms have alleged that Namecheap initially communicated a DDoS before switching to the power-outage explanation. Cyber Kendra has not been able to verify that claim against any archived Namecheap communication, and it should be treated as unconfirmed. If you are reading a report that attributes this outage to an attack, check whether it cites a Namecheap source or another news article.
Will I Lose Email, Files, or Data?
In the email, Namecheap has been specific, and the explanation is technically sound. Mail sent to affected addresses during the outage is not expected to be lost. When a receiving mail server is unreachable, the sending server queues the message and automatically retries over a period that can last for days. Once connectivity returns, the backlog delivers. What you should expect is delay, not loss.
The exceptions worth knowing:
- Senders whose mail servers give up early, or which bounce on the first timeout, may generate a delivery failure notice. Those messages will not arrive on their own.
- Anything time-sensitive that routed through Namecheap forwarding — password resets, OTPs, payment confirmations, calendar invites — may arrive too late to be usable, even if it eventually arrives.
- Mail you were composing in webmail at the moment of the cutoff is gone unless it was saved as a draft on the server.
On hosting data, a thermal shutdown is a controlled power-down, which is the safest kind. Namecheap has not reported data loss and has not indicated that any storage was damaged. That said, an unplanned shutdown of thousands of machines can leave individual databases in an inconsistent state on restart. When your site comes back, check that recent writes — orders, form submissions, new posts — are actually present before assuming everything restored cleanly.
What Namecheap Users Should Do Right Now
- Do not start a domain transfer during an outage. Transfers need working registrar systems and a reachable admin email. Starting now is likely to fail or stall, leaving a state that is harder to unwind than waiting.
- Do not change nameservers in a panic. If Namecheap's DNS management panel is down, you cannot make the change anyway, and a half-applied nameserver switch during propagation can extend your downtime past the outage itself.
- Use live chat, not tickets. Namecheap's email ticketing was explicitly listed as affected. Chat via the Help Center was the channel the company pointed customers to.
- Tell your own customers before they tell you. If you host client sites, a short factual notice naming the upstream cause protects you far better than silence. Link to the vendor status page, not to your own guesswork.
- Screenshot everything. Uptime monitor logs, error pages, timestamps, and lost transaction records. If you intend to ask for a credit, the case is built on evidence you collect now, not on your recollection next week.
- Check your recent data once you are back. Verify the last few hours of database writes before the outage, and confirm scheduled jobs and cron tasks resumed.
The Design Decision That Made This Worse
Most coverage of this outage stops at “data center had a problem”. The more useful question is why a single facility could take out this much surface area at once.
Namecheap has been a major PhoenixNAP tenant for years. In its own public post-mortem after a 2018 outage at the same facility, the company described itself as one of the site's largest tenants, drawing around half a megawatt and running thousands of servers there. The 5,000-plus figure cited this week suggests that concentration has not meaningfully changed.
Concentrating hosting in one well-run facility is a defensible business decision. Concentrating authoritative DNS in the same failure domain as the hosting it serves is a different matter. DNS is the one service in the stack that is supposed to be geographically distributed precisely so that it survives the loss of any single site. When Namecheap DNS went down, it did not just break Namecheap-hosted sites — it broke every site anywhere in the world whose nameservers pointed at Namecheap, including sites hosted on entirely unaffected providers.
The support helpdesk is sitting in the same building compound. The moment customers most needed to reach Namecheap was the moment Namecheap could not receive tickets. Status communication then falls back to X, which is not where most customers look first.
For readers who host with Namecheap, the practical takeaway is narrower than “switch providers”. It is this: your DNS provider and your hosting provider should not be the same company on the same site. Moving authoritative DNS to an independent, anycast provider costs nothing on most free tiers and decouples the two largest failure modes you are exposed to. Had that separation been in place, a large share of the sites that broke this week would have remained resolvable, served an error from their origin, and been fixable with a temporary redirect.
Namecheap's Track Record at Phoenix
This is not the first significant incident at the same facility, and the pattern is part of why the reaction from longtime customers was so sharp.
- November 2018 — A power failure at PhoenixNAP during UPS maintenance caused route flapping on Namecheap's core network. The company published a detailed post-mortem noting that some non-critical infrastructure was not designed to be power-redundant.
- August 2020 — A prolonged outage hit namecheap.com, shared hosting, VPS, EasyWP, and Private Email; Namecheap ultimately attributed it to a third-party upstream provider.
- September 2021 — A misconfiguration during network expansion triggered a network storm that took down a redundant firewall cluster. Namecheap's post-mortem conceded that its first response had been based on an incorrect assumption, costing it hours.
- February 2024 — A confirmed DDoS campaign affected the main site and customer support.
- July 2026 — Shared and VPS hosting in Phoenix experienced timeouts, with restoration staged across servers.
Read together, these are not all the same failure. But four of the five involve the Phoenix footprint, and the recurring theme in Namecheap's own post-mortems is redundancy that existed on paper failing to hold at the edges.
Can You Claim Compensation?
Namecheap had not announced any compensation, service credit, or SLA payout at the time of writing, and customers were publicly asking for one.
What is worth knowing before you ask: hosting SLA credits generally have to be requested rather than applied automatically, are usually calculated as a proportion of the monthly fee rather than your business losses, and are typically defined in the hosting terms rather than the general terms of service. Read the SLA terms attached to your specific plan — shared, VPS, dedicated, and EasyWP are not necessarily covered identically — and file the request through the ticket system once it is processing email again, with your monitoring logs attached.
Cyber Kendra is not a legal advisor, and consequential losses from downtime are usually excluded by hosting contracts. If the sums involved are material to your business, that is a conversation for a lawyer rather than a support ticket.
Frequently Asked Questions
Is Namecheap down right now?
Namecheap opened emergency maintenance on 13 August 2026 and had not posted an all-clear as of this article's last verification. The authoritative source is Namecheap's own status post, which the company said it would update directly. For crowd-sourced reports from other users, see Downbits.
Why is Namecheap down?
A failure at its Phoenix data center, operated by PhoenixNAP. Namecheap's status page attributes it to a power outage; its CEO and PhoenixNAP describe a cooling system failure that forced a protective shutdown of more than 5,000 servers.
Was Namecheap hacked or hit by a DDoS attack?
No primary source from Namecheap or PhoenixNAP describes an attack for this incident. Reports linking it to a DDoS appear to conflate it with a separate, confirmed February 2024 Namecheap incident.
Will I lose emails sent during the Namecheap outage?
Namecheap says messages are not expected to be lost. Sending mail to the server queue and retry automatically, so the mail should be delivered late rather than disappear. Hard bounces from senders that give up early are the exception.
Are my domain registrations at risk?
Domain registration records are stored at the registry, not on Namecheap's hosting servers, so ownership is unaffected by a data center outage. Renewals and transfers processed during the window may be delayed.
My site is hosted elsewhere, but it still went down. Why?
Because your domain's nameservers point at Namecheap DNS. Namecheap's authoritative DNS was in the same failure domain as its hosting, so name resolution failed regardless of where the site was served.
Should I move my domain away from Namecheap?
Moving registration mid-incident is more likely to create problems than solve them. The higher-value change, once services are stable, is to separate DNS from hosting so that a single provider outage cannot break both at once.
How do I contact Namecheap support during the outage?
Email ticketing was listed as affected. Namecheap directed customers to live chat through its Help Center as the working channel.
This page is updated as the incident progresses. Bookmark it rather than searching again.
Disclosure: Downbits, linked above, is operated by Cyber Kendra.