I just switched from running my own server hardware for various operations (including this blog, isbn.nu, wifinetnews.com, and Books & Writers) to a Virtual Private Server (VPS), in which I have two virtual machines under my control but don't have to deal with the underlying hardware. It's been over eight years since I moved my servers into a co-location data center, and I've mostly run servers of my own since 1994.The experience of moving was, well, moving. I had a great relationship with my co-lo, and enjoyed controlling every aspect of my fate and destiny. But with aging hardware and dropping costs for VPS hosting, it simply couldn't be financially justified any more. A recent experience with a meltdown on a Xserve with TidBITS (where I program and write) led me to believe virtual machine hosting was totally reasonable. I've been working for several weeks to set things up the way I wanted, and started moving Web servers a few weeks ago one at a time. I had a few glitches, but all my own. I'm very happy with the speed, performance, and flexibility. I finally moved isbn.nu, my heaviest data/CPU user, a week ago. A few tweaks were needed, but all was well. Then I wrote about the issue of VPS for an upcoming column (will add link) and tweeted about shutting off servers. That angered the data center gods, which struck the Fremont, Calif., DC at which my VPSes are located. The power surge apparently blew the mains and overwhelmed UPS backups. Power was quickly restored, and one of my servers was back online within a couple hours. The other? Some hard drives went bad and needed to be swapped, but total downtime was perhaps five hours (from a Saturday night to Sunday morning, hardly prime time). If the hard drive array was truly fubared, I had additional backups that the host could have restored. Clearly, I should have kept my mouth shut.