Namecheap‘s shared hosting servers went down again on August 26, marking the company’s second outage this month, and this time it never said why. A status post published at 20:25 UTC listed 78 affected servers across three categories, Business, Premium, and Server, and closed with a line that set the tone for everything that followed: “Unfortunately, we have no ETA so far.”
The scale broke down as 18 servers under Business, 33 under Premium, and 27 under Server. Two updates followed. At 21:10 UTC, for instance, the company reported the servers back up and under observation. By 22:45 UTC, it declared the issue resolved. Even so, neither update, nor the original post, named a cause. Domain Name Wire, which covered the incident as it unfolded, noted the same gap: no explanation, and no estimated resolution time, from start to finish.
Fifteen minutes after the all clear, at 23:00 UTC, Namecheap opened emergency maintenance on the MySQL service running on Premium 293, one of the servers named in the outage. That maintenance wrapped at midnight. Still, whether it connected to the earlier outage is something neither status post addresses.
This wasn’t Namecheap’s first disruption this month, either. On August 13, a cooling failure at RadiusDC’s Phoenix data center knocked out hosting, EasyWP, Private Email, and parts of billing for several hours. That time, the company named the cause quickly, and CEO Hillan Klein detailed it in a blog post the next day, attributing the outage directly to the cooling system failure and RadiusDC’s decision to take services offline.
By contrast, the August 26 incident stands apart in both scope and disclosure. It was limited to shared hosting rather than spanning multiple products, and where the Phoenix incident got a cause, a data center name, and executive commentary, the August status post described the problem only as “temporary technical issues” and left it there.
Ultimately, Namecheap has now had two outages in thirteen days. Only one, though, came with an explanation.
