
r/HostingReport

All of Namecheap is down, again. Something's up.
[supprimé]
My Experience After Nearly a Year and $10,000+ With GoDaddy
I’m sharing my experience to help other small-business owners make an informed decision before choosing GoDaddy and, hopefully, help GoDaddy fix these issues.
I hired GoDaddy in October 2025 for website design, Website Care, hosting, SEO and Microsoft 365. Nearly a year later, I am still dealing with problems getting these services to work reliably.
My experience has been a repeating cycle: I report a website problem, spend significant time with support, wait for it to be addressed, and then discover that while one problem was fixed, something else was changed or broken.
Support has required repeated verification, transfers, explaining the same problem again, repeating troubleshooting, creating tickets, waiting and calling back. On at least six occasions, I spent approximately 6–9 hours working directly with GoDaddy support on website issues.
My biggest concern is my customer contact form. Prospective clients submit the form and receive confirmation that we will respond, but I don't receive their inquiry. To the client, it appears my company simply failed to respond. I previously spent days working with GoDaddy on this same form.
I have also escalated issues, but my experience has been another ticket and another wait while my published website remains affected.
After spending more than $10,000, my advice is to carefully evaluate your needs. For a basic website, GoDaddy may be worth considering. If your business depends on a polished, reliable, commercial-grade website, I recommend evaluating dedicated professional web-development firms.
I would also carefully evaluate purchasing Microsoft 365, OneDrive and SharePoint directly from Microsoft rather than through GoDaddy.
Technology problems happen. My concern is the extraordinary amount of time required to get the services I purchased working reliably. I hope this helps other business owners make informed decisions and helps GoDaddy address these recurring service and support problems.
I am extremely disappointed with my recent experience with Hosting.com
My annual hosting renewal invoice (#A-INV-1264990) was issued on 11 August 2026 with a clearly stated due date of 25 August 2026. Yet, on 11 August—two weeks BEFORE the invoice was due—my hosting account suddenly became inaccessible. My website went offline, and I could no longer access cPanel.
Initially, I assumed this was a premature billing suspension. What Hosting.com's support team later told me was even more concerning.
According to their response, my hosting account was actually DELETED from their server node. They specifically stated that this was an "isolated server-level removal rather than an automated non-payment suspension."
I did not request the deletion.
My invoice was not overdue.
My hosting renewal date had not arrived.
Yet my website and hosting environment were removed.
What frustrates me even more is that I am now being told that I need to PAY the upcoming KES 5,800 renewal invoice before they will recreate the hosting environment and restore my website from their offsite backups.
That makes absolutely no sense to me.
If Hosting.com acknowledges that the account was deleted prematurely at the server level and that it was NOT deleted because of non-payment, why should I have to make an early payment to correct a problem I did not cause?
The payment itself isn't even the biggest issue here. It is the principle and the handling of the incident.
A hosting company is entrusted with websites, databases, emails and other business-critical data. Having an active hosting environment inexplicably deleted before its renewal date is extremely concerning.
I have asked Hosting.com to explain:
• What or who triggered the server-level deletion?
• Why was an active hosting account deleted approximately two weeks before renewal?
• Was this a human error, automated process or system failure?
• Why is restoration conditional on early payment when they acknowledge this wasn't a non-payment suspension?
• What is the timestamp of the latest complete offsite backup?
• Will all files, databases, emails and configurations be fully recoverable?
• What safeguards are being implemented to prevent this from happening again?
Support reference: PRN-306-22871.
At this point, I am waiting for Hosting.com to take responsibility for the incident, restore the service, and provide a proper technical explanation.
For anyone considering a hosting provider, reliability isn't just about uptime percentages. It's also about what happens when something goes seriously wrong—and whether the provider takes responsibility when it does.
I will update this review depending on how Hosting.com resolves the matter.
Major Outage Hits Namecheap: Sites and Email Down Following Phoenix Data Center Power Failure
A major outage has hit major domain registrar and hosting provider Namecheap, causing widespread disruptions across its hosting infrastructure and email services.
Source : Namecheap website official screenshot
Key Details of the Incident
- Root Cause: Namecheap confirmed an emergency maintenance event triggered by a severe power outage at its primary data center located in Phoenix.
- Services Impacted: Hosted websites across shared, VPS, and dedicated servers are experiencing significant downtime, slow loading speeds, or throwing 503 connection errors.
- Private Email Service: Namecheap's email infrastructure (which serves around 1.4 million inboxes) is currently affected. While Namecheap stated email delivery delays are expected, they do not anticipate lost messages.
- Support System Outage: Compounding customer frustration, Namecheap’s live chat helpdesk went down during the incident. Customers are being directed to reach support via email or Microsoft Teams, with real-time status updates posted on their official X account.
Scale & Reaction
With over 24 million web domains hosted on the platform, network monitoring tools like NetBlocks reported a drastic drop in Namecheap’s overall network traffic. Outage reports spiked on Downdetector early Thursday morning.
The situation has sparked widespread criticism online regarding the lack of data center redundancy for a major hosting provider handling millions of websites globally. Namecheap stated their technical teams are working to restore full network connectivity as quickly as possible.
UK small business using a .co.uk domain offered to buy the matching .com domain for $135, declined $1K counter-offer, then lost $1.5K on a failed UDRP!
We've got another UDRP karma story:
A UK small business owner who uses the domain LoyalSoldiers.co.uk wanted the matching .com domain (LoyalSoldiers.com), so he contacted the owner of the domain and offered to buy it for £100 ($135).
He then received a $999 counter-offer, but he declined it and opted for a UDRP complaint demanding that the .com domain be transferred to him. He paid a $1,500 fee to file the UDRP complaint with WIPO (full case details here).
Well, guess what? It didn't go his way. The claim was denied and ruled a reverse domain name hijacking attempt.
Could've just paid $1k and got the domain the easy way.
Now that the domain owner knows this guy can pay more, it might get more expensive if he tries to buy it again!
Startup buys a domain name for $1.5 million in a LTO transaction then cancels after two payments
A couple of months ago, a crypto startup bought the domain name Haste.com for "$2 million", according to their announcement on X.
It was a 24-month LTO (Lease To Own) transaction.
The seller of the domain (James Booth) just revealed that the sale has been canceled after two installments were paid, and that the actual price was $1.5 million, not $2 million as the startup (buyer) publicly announced.
James gets to keep the domain and the two payments already made (should be about $125,000).
The domain is back for sale on Atom at $1,495,000 BIN.
Most big web hosts are switching to AI support; pick a small provider if you want human support
One by one, big web hosting providers are switching from human chat support to AI chatbots. Some of them still allow you to access human support with a quick click (or prompt), while others make it extremely painful to get past the AI chatbot.
That may work for some newbies who mostly ask newbie questions that an AI chatbot can handle, but for me, when I need to contact support, it's usually an issue that needs human intervention.
Small web hosts are slower to adopt AI and many still have human-only support, but you have to look harder to find those. Search for them on forums and Reddit -- that's where I found several good ones.