New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Namesilo has been down for over an hour.
It looks like NameSilo IT department went to Cancún.
I host my domains DNS with Namesilo, I have no problem with DNS, this outage is only on their main website.
Comments
@NameCrane refugee offer?! soon?
NameSilo and Namecheap one in the same? Namecheap is down too.
I just checked namecheap.com
https://www.namecheap.com/
Maybe Namesilo is also using PhoenixNAP? At least Namecheap does for sure.
https://lowendtalk.com/discussion/comment/4847446/#Comment_4847446
They post this on their page:
We're currently experiencing a service disruption due to an issue at one of our data center providers. Our team is actively working with the provider to restore service as quickly as possible.
We apologize for the interruption and appreciate your patience.
Shit happens. Silo is/was solid.
```[Updated] Namecheap.com Website and Services: Emergency Maintenance
Domains, EasyWP, General, Hosting, Private email Aug
13
202608:35:am America/New_York Ted V.
Dear Customers,
We’re currently responding to an emergency caused by a power outage at our Phoenix datacenter. As a result, the following services may be affected:
Namecheap.com: undergoing emergency maintenance
Shared, VPS, and Dedicated Hosting: experiencing network issues. Websites may be slow, unavailable, or return 503 errors. Hosting panel access may also be affected.
EasyWP: all infrastructure, including EasyWP.com, the Dashboard, and client websites, may be temporarily unreachable.
DNS: Namecheap DNS infrastructure is unavailable. DNS zone resolution and management are affected.
Private Email, Shared Hosting mailboxes, Free Email Forwarding, and Domain Privacy email forwarding: incoming and outgoing mail delivery may be delayed. Sending servers will see connection timeouts, but messages are not expected to be lost, mail should arrive once sending servers retry after the incident resolves.
URL Redirect (BasicDNS and PremiumDNS): may also be affected
Hosting operations (activations, renewals, plan changes): processed with a delay.
We’re also experiencing an issue with our support helpdesk and are currently unable to assist via live chat. You can still reach our Customer Support Team via Microsoft Teams or email.
Check out this Knowledgebase article for details: How can I request support via email?
Backup Teams accounts:
Domain Support: namecheap1, namecheap2, namecheap3, namecheap4, namecheap5
Hosting Support: namecheap6, namecheap7, namecheap8
SSL Support: namecheap9
Domain Transfers Support: namecheap10
Hosting Transfers Support: namecheap11
Managed WordPress Support: live:.cid.d05bca5918cd3f4d
Private Email Support: live:.cid.19487adb22e4e066
Billing Support: live:.cid.f4bb718e1b033727
L&A / Abuse: nc.abuse
Our team is working to bring systems back online as soon as possible.
We’ll update this post as soon as we have further news.
Kind regards,
Namecheap Support Team```
Namesilo.com added a update:
https://www.namesilo.com/
So both namecheap and namsilo uses the same dc? Anyway, people said that namecheap also suffered from ddos. Maybe the ddos aren't originally what took them down but just some party taking advantage of them in the middle of having trouble. Even nc dns are down so people that uses nc dns are shitting themselves too. Lucky me spaceship aren't affected, at least their site are still up. But i never use registrar default dns anyway.
It's unacceptable for registrars of the size of either of these two to be down longer than it takes to switch over to another environment. This isn't an AWS or Cloudflare outage.
Which is annoying because I had really started to get used to Namesilo. Their management panel was a nice upgrade from some other registrars (Internetbs, Hover). Counting myself lucky not having any critical domains there that would ever require urgent changes at registrar level. External DNS is a blessing.
Wishing them and everyone the best.
namecheap also.
Namesilo.com is working now!
It's not acceptable for them to have everything in the same datacenter, but it is acceptable to have another single point of failure with Cloudflare, and/or AWS?
This is the first of such outage I've ever heard of and I've been a Namesilo customer for years. It's possible they had others that I never saw -- I haven't been tracking.
But, are you sure that if they had a 100% AWS infrastructure that they would have had less downtime, overall? I tend to think that AWS and Cloudflare might actually go down more often than this datacenter's (probably redundant) power.
Is this not the worst time of the year to go to Cancun? I go in December.
A huge shit the size of a silo.
It seems PhoenixNAP opens at 2010. So, it's been 16 years (some parts should be or near EOL)
Yes, but I think they're different enough that it's not an apples to apples comparison. Single point of failure in the form of a single data center vs. single point of failure in the form of a hyperscaler.
I'm not the server admin person (aside from my own hobby projects and side quests), so I do lack the in-depth insight into the complexity of this. However, I've had my fingers in companies that in case one hyperscaler region has an outage, the business can with a tolerable amount of headache shift to another region. These weren't massive companies. They just invested in time into architecture and infrastructure that enabled it.
My point with hyperscalers was in references to past cases where they have had (near) total outages across all regions. This wasn't one of those going on, because there wasn't a total outage with a hyperscaler. Hence, in my opinion, NameSilo and Namecheap seem to be using infrastructure that's too fragile relative to how important they might be for clients.
Like I said, I'm a happy Namesilo customer and Namecheap isn't bad either. But if they have an infrastructure that lets them be down like this, I wouldn't be comfortable holding critical domains with them where a registrar-level change on short notice may be required or desired in some cases (mainly thinking of regulated sectors). I'm not actually changing my opinion on Namesilo and Namecheap based on this event, just bearing this incident in mind next time I'm in a meeting and registration of critical domains comes up.
I'm a relatively new Namesilo customer, so I'm very glad to hear this! I'm confident they've earned their good reputation.
I think using an infrastructure with location redundancy is better than being down for several hours because of one data center being down. Of course, not all AWS/GCP/Azure clients are actually set up that way and are effectively single-homed to a region. (IIRC, even being in a single hyperscaler region can often mean you have multi-DC redundancy within that region?) But to answer your question: yes, if they had set themselves up for it, the risk of a total outage would likely be lower. It's less of a "would they have had" and more of a "could they have done things to ensure", and hyperscalers can make the second one easier.
Inb4 Bezos shill check clears.
Namecheap experienced a major infrastructure meltdown on Thursday after cooling systems failed at a Phoenix datacenter housing a significant part of its server infrastructure.
The incident at PhoenixNAP forced Namecheap to take thousands of servers offline as temperatures inside the facility climbed.
Namecheap CEO Hillan Klein described the event as an extraordinary infrastructure incident, with the impact extending to more than 5,000 servers.
Source: https://domaingangcom/domain-news/namecheap-phoenix-datacenter-cooling-failure-takes-thousands-of-servers-offline/
I appreciate your thorough reply!
I 100% understand what you are saying. A multi region environment should be more reliable than a single region environment. And in this case, it would've made a huge difference here.
Namesilo is a pretty big business, and you're right that this is pretty serious. So they probably should have more fallback plans in place, I agree. But I don't necessarily agree that using multiple AWS regions will result in less failure in the long run. AWS has had many outages. And Cloudflare has had global, or at least multi-region outages. Complicated infrastructure has more moving parts and sometimes the human element is actually the most dangerous one of all. Something might be perfect on paper, but lo and behold, there's lots of multi-region infrastructure with a lot of money spent on DevOps teams, and they still go down. Heck, Starlink has had multiple serious outages while seeming like something that should have plenty of redundancies in design.
On paper, and/or with a very competent team, you could certainly mitigate for this. But I think sometimes in practice, a single (stable) region can outperform a multi region setup in the long run.
Now if it was multi-cloud, and done very cautiously, I would have the most confidence with that.
Sometimes those "one box wonder" solution putter along for 10+ years without incident... Then they throw a drive and they're down for several hours. I used to try to throw every bit of paranoia into design that I could, and found that often the simpler solution was more warranted. Of course, it's partly due to smaller scale, but also I know that complicated infrastructure can be more delicate or finicky to get just right. Lots of tough problems to solve.
I've been using Incognet @MannDude for a while now for my domains. Haven't looked at using anyone else.
Same!
it's unacceptable, bitch!!!
i expect this unacceptable shit to change because i posted my opinion on LET. if namesilo doesn't take care of their shit, i will post here on LET once again!
Will be moving domains elsewhere.