Namecheap is experiencing a broad service disruption on August 13, 2026. The company says the emergency was caused by a power outage at its Phoenix datacenter and confirms impacts across Namecheap.com, hosting, EasyWP, DNS infrastructure, email, redirects, and hosting-related operations.
The most important detail for many administrators is not merely that a web server might be unreachable: Namecheap says its DNS infrastructure is unavailable and that both DNS zone resolution and management are affected. A domain can therefore stop resolving even if its origin server is still running.
Editorial status check: August 13, 2026, 10:17 AM America/Merida. The incident remained open on the official page we reviewed. This article should be updated when Namecheap publishes new information.
What Namecheap confirmed about the August 13 outage
Namecheap's official incident notice, posted at 08:35 AM America/New_York, describes an emergency caused by a power outage at the Phoenix datacenter. At our latest check, the company says its teams are working to bring systems back online and has not published an estimated recovery time.
According to the official Namecheap status notice, the scope includes:
- Namecheap.com: under emergency maintenance.
- Shared, VPS, and Dedicated Hosting: network issues; websites may be slow, unavailable, or return 503 errors. Hosting panel access may also be affected.
- EasyWP: Namecheap says all infrastructure, including the dashboard and customer websites, may be temporarily unreachable.
- DNS: Namecheap's DNS infrastructure is listed as unavailable; zone resolution and management are affected.
- Private Email and hosting mailboxes: inbound and outbound delivery may be delayed. Namecheap says messages are not expected to be lost and should arrive after sending servers retry once the incident is resolved.
- BasicDNS and PremiumDNS URL Redirect: may also be affected.
- Hosting operations: activations, renewals, and plan changes may be delayed.
- Support: the helpdesk and live chat are also experiencing issues; the official notice provides alternative contact channels.
This is broader than an isolated corporate-site outage. When DNS, hosting network connectivity, EasyWP, and email are affected at the same time, the same incident can look very different depending on where each part of a project is hosted.
Why a DNS outage can take down a site while the server is still alive
DNS and hosting are separate layers. Hosting runs the application; authoritative DNS publishes the information needed to find it. If the authoritative servers for a zone stop answering and a cached response has expired, a recursive resolver may be unable to obtain the site's IP address.
That is why a browser can show a name-resolution error while the web server, database, and Nginx or Apache are still healthy. Our guide to how DNS works explains the path between recursive resolvers, cache, and authoritative name servers.
It also explains why switching your laptop to 1.1.1.1 or 8.8.8.8 does not by itself fix an authoritative DNS outage. Those services are recursive resolvers. They can ask for an answer, but they cannot create authoritative data that is unavailable and no longer cached.
Is the Namecheap API down too?
Namecheap's official API documentation identifies https://api.namecheap.com/xml.response as the production endpoint. However, the emergency notice does not list the API as a separate affected component at the time of this review.
That means user reports or individual failures should not be turned into an official claim that every API call is down. If an automation is failing today, capture the actual failure mode—DNS resolution, timeout, connection error, or HTTP/application response—and compare it with the incident timeline.
The distinction matters. A client that cannot resolve api.namecheap.com is failing differently from a client that reaches the endpoint and receives an application error. Until Namecheap publishes API-specific status, treat that part as observed user impact rather than a separately confirmed official outage.
How to tell whether your problem is DNS or the origin server
If you manage an affected domain, you can collect useful evidence without making destructive changes. The following commands are diagnostic instructions; they are not presented as tests Teramont executed against your domain.
1. Check the delegated name servers
dig +short NS yourdomain.com
If the result uses Namecheap or Namecheap hosting name servers, the DNS incident may be directly relevant to your zone.
2. Query more than one recursive resolver
Reduce dependencies in your next architecture
If you want to separate compute from your registrar and choose DNS independently, a VPS gives you control over the server layer and application deployment.
View VPS Hostingdig @1.1.1.1 yourdomain.com A
dig @8.8.8.8 yourdomain.com A
Compare the response code, answer section, and whether one resolver still has cached data. A difference between resolvers does not prove the root cause by itself, but it helps distinguish cache behavior from a consistent failure.
3. If you know the origin IP, test HTTPS while bypassing DNS
curl --resolve yourdomain.com:443:203.0.113.10 https://yourdomain.com/ -I
Replace 203.0.113.10 with your real server IP; the address shown is reserved for documentation. The --resolve option forces cURL to use a specific IP while keeping the site hostname for HTTP and TLS. If the origin answers this way but normal DNS resolution fails, that is strong evidence the failure happens before the web server.
If your hosting is also on affected Namecheap infrastructure, this test may fail too. DNS failure and origin-network failure can happen simultaneously.
Should you change name servers during the outage?
Do not do it reflexively. Changing name servers during an incident can be a valid mitigation only when you already have a complete, current copy of the zone at another authoritative DNS provider, understand the DNSSEC implications, and can accept the transition time.
Namecheap's own DNS change guide warns that host records are not copied automatically between providers and that name-server changes are not instantaneous. Missing MX, TXT, CAA, subdomain, or verification records can turn one outage into several.
If the domain uses DNSSEC, the migration needs even more care. DS records at the registrar must match the keys used by the authoritative zone. Namecheap documents DNSSEC management with Custom DNS; an inconsistent chain of trust can cause validation failures even after the replacement name servers start answering.
Moving DNS does not repair down hosting
There is another important limitation: if the application lives on Shared Hosting, VPS, Dedicated Hosting, or EasyWP infrastructure that is also affected, moving only authoritative DNS to another provider does not bring the origin server back online.
Service recovery requires an alternate destination capable of serving the application: another server, replica, standby environment, or emergency static site. DNS only controls where clients look.
This incident is a useful example of why shared failure domains matter when selecting infrastructure. Our guide to how to choose web hosting covers SLA, backups, DNS, email, migration, and recovery questions that are much easier to answer before an outage.
What to do now if you depend on Namecheap
- Do not make bulk changes without an inventory. Preserve your DNS records, origin IPs, mail configuration, and current name servers if you can still access them.
- Identify the failing layer. Separate DNS resolution, control-panel access, server connectivity, the application, and email.
- Avoid unnecessary reboots and migrations. A 503 or timeout during a network incident does not automatically mean your VPS is corrupted.
- If an external replica is already prepared, follow your runbook. Move traffic only with verified zones and data, and keep a rollback path.
- Watch the official incident page. Scope and recovery can change; use Namecheap's own status notice as the primary source before acting on rumors.
The infrastructure lesson: separate registration, DNS, and compute
No architecture is outage-proof, and using different providers does not guarantee uptime. But separating functions can make failure modes less correlated. Your registrar can manage domain ownership, an authoritative DNS provider can publish the zone, and the application can run on another network.
The benefit is not simply “more vendors.” It is the ability to recover one layer without needing the same platform to be available to modify every other layer. That requires zone backups, emergency access, sensible TTLs planned ahead of time, documented DNSSEC, restorable backups, and an alternate origin when the business genuinely requires high availability.
Current status and what remains unknown
At 10:17 AM America/Merida on August 13, 2026, the verified information is that Namecheap is responding to an emergency caused by a Phoenix power outage and reports impact to DNS, hosting, EasyWP, email, Namecheap.com, and other services. The incident notice we reviewed does not yet provide a recovery ETA or a detailed root-cause analysis beyond the power outage.
It also does not publish a separate API status in that notice. When Namecheap posts a new official update—partial restoration, DNS recovery, full resolution, or a postmortem—this article should be revised with the exact time and source.
