Today, I'm glad to have moved away all my production environments as well.
That's just the problem with services as AWS, traffic is too costly to have production live with another provider as well.
Having one AWS account scares the crap out of me as well. It’s never a good thing if all your eggs are in one basket.
My money is on stuff spread across Bytemark, Linode and DigitalOcean with a DR plan involving mostly automatic recovery.
AWS doesn’t get a look in as it is extremely costly to port away from anything that isn’t bare metal and pipes.
Ansible works for this stuff as it allows you to can the task of “quick get me a production environment up on Linode!”
If you can afford some downtime you don’t need a hot standby just roll out everything into new provider and you’re done.
I’ve done this on very large scale environments and small ones and it’s achievable for even small organisations. The killer is avoid anything you can’t run on bare metal servers.
1) your DNS provider having issues (even Route53 sometimes has them, https://mwork.io/2017/03/14/aws-route53-dns-outage-impacts-l...)
2) legal issues, when one of your domains gets seized or the provider gets pressured into cancelling, just as has happened with Pirate bay, SciHub and friends, gambling or sites with user generated content that may be illegal or frowned upon in some countries or for the latter to the Nazi site Daily Stormer (although I'm glad for it being down, it's a perfect example what can happen in a very short time frame)
3) (edit, after suggestion below) the entire TLD going down because the TLD DNS provider has issues, which also happens from time to time.
Just fire up another one, install everything on there, switch off the old one and forget about it. This means never paying for more than one month in advance.
Servers break. Providers go down.
It happens to all of them. Whenever I read comments like yours I wonder where you moved your servers to, and if you'll move them again when that goes down too.