Edit: The 5 hours are what I've noticed from either personal servers or those of friends/acquaintances. YMMV.
Edit: The 5 hours are what I've noticed from either personal servers or those of friends/acquaintances. YMMV.
I don't keep track of the totals but I think it you search their forums, I seem to recall someone who had monitored them with Pingdom or Wormly(or equivalent) for a fair period of time.
An Amazon small instance has 1.7 GB of memory, and 160 GB of "local instance storage" (which Amazon will wipe when your instance goes down), and "1 EC2 unit" (a single core on a 1.2 GHz 2007 Xeon processor). It will cost you about $60 a month.
A similar plan on Linode will give you 1.5 GB RAM, and 60 GB storage. They will also throw in bandwidth and persistent storage, though.
Amazon tends to give you more flexibility (on demand prices, spot prices, dedicated prices, bigger instances, smaller instances, persistent storage, cheap temporary storage, and so on). But it's not as easy to use as Linode.
Linode targets people who want a cloud server. Amazon has a number of uses.
The real trouble with Amazon is the erratic performance of the EBS system which can kill an otherwise fast system. Linode's I/O does seem to be much more consistent and predictable.
Amazon's storage capacity and the cost of storage is unmatched, though. If you have a mountain of data, Linode will be prohibitively expensive.
p.s. The last two weren't network outages - they were total power failures. Your 'node would have been hard-booted as a result.