(WEB HOST INDUSTRY REVIEW) — Many customers of Web hosting provider DreamHost (www.dreamhost.com) have reported outages in the past week, after the company experienced a significant network failure following the company’s data center migration.
In a November 24th blog post, DreamHost wrote that it “completed the mother of all DreamHost data center moves”, moving from its former Net2EZ facility to its new home at Alchemy Communications’ data center.
Problems began to arise just a couple days prior to the post, while some customers are still reporting issues now, more than a week after the migration was completed.
According to a post on the ZDNet blog, which cites a DreamHost technical team’s response to a customer email, the outages can be attributed to DreamHost’s upgrading of its shared hosting hardware, the upgrade going terribly wrong, and customer support not knowing how to resolve this problem.
Throughout the whole situation, DreamHost has been keeping customers informed about its current status via email, the DreamHost Status page, and Twitter.
In an update on its status page at 11:30 p.m. PST Monday, DreamHost notified customers that one of its “vserver hosts is no longer detecting its raid controller preventing the machine from booting”.
Several updates later, the company finally managed to replace the raid controller and complete a file-system check on the host server.
Most recently, the team wrote this status update at 3:25 a.m. PST Tuesday: “As usual, we’re watching this one closely and will update if we have any other issues!”
However, some customers continue to encounter problems and have reported their issues on Twitter.
One customer posted on Twitter this message around 12:00 p.m. PST on Tuesday: “Looks like all my websites are down. Dreamhost having problems again? I haven’t found any reports nor heard back on an e-mail.”
DreamHost updated its Twitter page with this message, early Tuesday morning:
“Update: At least 95% of the servers/services are back. If your site is still down, it should be back *very* soon. Sorry about all of this!”
No related posts.
