Two major domain registries are offline. Namecheap and Namesilo

[examplens]

I don't know if it is really planned maintenance as they are trying to present, or if it is a well-organized attack.
It must be admitted that the timing is awkward.

🚨We're currently experiencing service disruptions due to a power outage affecting our datacenter in Phoenix.

We're sorry for the disruption this is causing. Our team is working to restore services as soon as possible.

We'll keep you updated here.

https://x.com/Namecheap/status/2087902651124011037?s=20

Spaceship is also owned by Namecheap, but it is not affected by this problem

There is no announcement from Namesilo

[JeromeTash]

There is no announcement from Namesilo

NameSilo also just posted an update a few moments back


https://x.com/namesilo/status/2087986337366286709
It turns out they both share the same data centre provider (https://phoenixnap.com), located in Phoenix, Arizona. I think this explains why both domain registries are experiencing the blackout.

[PX-Z]

This also means a major headache and potentially significant business losses for companies that host their websites or servers with providers such as namecheap or namesilo when their infrastructure is located in the affected data center.

I also doubt that these two are the only providers affected by this data center incident. There are likely other hosting companies, resellers, and services whose infrastructure is colocated or dependent on the same facility.

[robelneo]

This thing can happen, based on my experience in the 6 years I've been at Namecheap; it seldom happens, it's good that they already fix it, but a 24-hour downtime will have a serious impact on your business, and there will be a perception that your business is out, which is why a community based or business based platform should have a social media handle so they can update their clients and communities about the downtime.

[NotATether]

This just makes it even harder for sysadmins and builders to keep their sites online.

So many levels where the web service can go offline, from the hosting, to the registrar's DNS, even to the whole data center's networking. This happened to me recently, and it screwed my services for a few days.

I think the best option now is to keep backups which are packaged in a way that lets you quickly deploy to a different DC.

[examplens]

This just makes it even harder for sysadmins and builders to keep their sites online.

So many levels where the web service can go offline, from the hosting, to the registrar's DNS, even to the whole data center's networking. This happened to me recently, and it screwed my services for a few days.

I think the best option now is to keep backups which are packaged in a way that lets you quickly deploy to a different DC.

All this is ok, but to move to another server, it is necessary to make a specific update to the DNS records.
And that is also impossible here, because they are completely unavailable. Not much can be done if the domain is also registered with them.

[coin-investor]

I think the best option now is to keep backups which are packaged in a way that lets you quickly deploy to a different DC.

All this is ok, but to move to another server, it is necessary to make a specific update to the DNS records.
And that is also impossible here, because they are completely unavailable. Not much can be done if the domain is also registered with them.

This is only possible if the domain and hosting are separate and you have a backup on your machine, but Namecheap downtime has never lasted 48 hours; it may impact you if you run a client-based site and can't update your client.
If your site is business-related, you need ways to communicate hosting issues to your client; without communication, it can ruin your reputation.

[examplens]

However, Spaceship was also subject to this problem.
I received their explanation as to why the work was interrupted

Spaceship services back online
Dear xx,

All our services are now back online following the significant outage caused by a cooling system failure at the RadiusDC: Phoenix data center.
We know many of you were unable to access websites, email, and other services you rely on. We’re deeply sorry for the disruption this caused.
While our teams continue to monitor everything closely, we want to explain what happened, why services had to be taken offline, and what we’re doing next.
 
What happened?
A major storm knocked out cooling systems at the data center, causing temperatures to rise to unsafe levels.
RadiusDC instructed us to take services offline to protect customer infrastructure. It was a disruptive step, but keeping equipment running could have caused serious and lasting damage.
Keeping affected services offline until conditions were safe also helped prevent further problems during recovery.

How this may have affected you
Several Spaceship services were disrupted:
Hosting – customer websites and key hosting operations experienced significant disruption.
EasyWP – customer websites and access to EasyWP services were disrupted.
Spacemail – sending and receiving email was unavailable.
Email forwarding – forwarded emails could not be received.
info icon   
Important: Incoming emails should not have been lost. Only delayed.
What happens next
With services restored, we’re examining the incident in detail and will be taking steps to make our infrastructure more resilient.
This includes adding further redundancy across our data centers in the US, Europe, and Asia.