I have never heard of an extended S3 crash affecting one bucket. In fact, I only heard about one large-scale reading without any changes in my story. Problems with routing, etc. They may give you downtime, but changing buckets will not fix this, since they are all served by the same interface.
If you want to have a backup plan, one good option is to use CNAME, as Rahman suggests, but your backup system should not be on S3; Download it from a regular VPS to another provider (not EC2). Note that the old CNAME will be cached for its TTL; setting a very long TTL will mean that it will take longer to switch to another resource.
source share