The problem that I have with mt is that they sell themselves as the "don't worry, put your site with us and nothing can go wrong" company. And that can never be true. No one can make promises like that, but those promises mean that they don't tell you things like backup strategies, replication, data centers, etc. And so you're just left with a promise that they've taken care of everything.<p>While I don't expect a company to tell me everything, I much prefer Amazon's take on the issue. For example, they specifically quote an annual failure rate that they expect and offer S3 snapshots (which are replicated across multiple boxes in multiple locations) as a backup. No hype or promises; just the knowledge I need to make sure I don't loose data.<p>With companies like Slicehost, Linode, or Amazon I know what I'm getting: a Xen instance with a certain amount of RAM. I can then replicate data, take backups, etc. to make sure that my site stays up and running. With Media Temple, I just get the promise of "hundreds of servers working in tandem to power [my] websites". Clearly it isn't 500 servers just working on my site or anything like that. So, what is it? It's a mystery and I find that when companies try to be mysterious, it's not because they're giving you more; it's because they're giving you less.
Glad I switched from them. Such an overhyped company. I've been on Slicehost since February 23rd of last year and have absolutely no complains. On (mt) I got shoddy support and a lazy staff (how the hell can you promise svn without ssh support for that long), for an incredibly overpriced hosting service.
(mt)'s gs offering has been absolutely terrible for us. Since the summer uptime and support have both been equally awful. The only redeeming quality of the gs service is the insanely large storage (100gb).
We have about 30 sites hosted with them and I have been none too pleased. The service is shoddy and disapointing. Currently, they are running Subversion 1.4.2 on the gridservers packages, which is nearly 3 years old. I've asked if they can upgrade to 1.5.x with no avail.<p>Our customers constantly complain that their sites are down, even if only for minutes at a time. I know we're only paying $20 a month for about 10 separate accounts, but I get better service from Dreamhost.<p>I think they're overpriced. I've dealt with tons of shared hosts for much less with better service. It seems like people get suckered in with their pretty website and the fact that a lot of big sites us them without doing much research.
Ouch, that's terrible. I'm glad I switched a couple of months ago -- if I didn't this would've affected me. :/<p>Anyone else notice how all of the sites on (mt)'s (gs) client page happen to be online every time there's a major outage?
It gets worse for those affected: <a href="http://weblog.mediatemple.net/weblog/2009/03/01/cluster-2-important-update/" rel="nofollow">http://weblog.mediatemple.net/weblog/2009/03/01/cluster-2-im...</a><p>Sounds like there's gonna be some financial compensation according to some messages from MT on Twitter to customers voicing their disapproval at the now 24+ hours downtime.
People pay only $20 per month and then complain like they're paying for hosting at rackspace. The service is a great value for what it provides. If what you're doing is that vital, you shouldnt be hosting it on a grid server at media temple
20 hrs now. It's not looking good... So glad I'm on cluster 4. Twitter is full of unhappy campers.<p>This has been compounded by the outage earlier this week too on the same cluster!
My non-essential sites are down (I didn't notice until I read it on HN). Good thing I'm hosting my emails on Gmail or I'd be getting calls from friends I host for free.
I just cross my fingers hoping this ain't gonna happen to our customer's site (Cluster #: 1 Storage #: 4). Maybe they will become a better hosting after all.
We just transitioned a customer off of MT onto some cheap dedicated servers with Amazon S3 storage and not only did their hosting costs go down, the performance went up dramatically.<p>In the business parlance of today, my stakeholder expectations were not aligned with their soup to nuts value proposition.