Major outages are rare and I am quite pleased.
For ref, the heroku app is rails, 2x dynos and a shared DB with minimal traffic. The others are PHP/apache apps, one using RDS, on plain EC2.
Heroku is at least 5 layers extra to go wrong on top of EC2. On the one hand I feel that each layer adds to the probability of failure. But I'd hope that one of the benefits of Heroku would be extra redundancy and failure handling, though my limited personal experience hasn't been that way so far.
EDIT: Regarding openness, I certainly feel that every single outage is admitted by Heroku, whereas I feel Amazon's status page has not listed a few outages I've suffered. Again personal feeling, not evidence.
When Heroku has issues during working hours, their support is great - you can pretty easily be put in contact with an engineer or a product manager. The catch here is that there doesn't appear to be any guaranteed response time to any tickets (my urgent ticket (everything is on fire) from Sunday was accepted Monday morning).
Amazon on the other hand is quite opaque - SQS/SimpleDB, for example, went down today for a few minutes (as in the service endpoints told us as such), but there wasn't a peep on the AWS status dashboard.
I've no idea why these services didn't report that my apps were permanently down :(