Especially with availability zones and multiple regions. Most companies don't have the capital or expertise to set up a local equivalent that even remotely approaches the robustness of a big cloud provider. The enormous cost savings of not owning multiple physical plants (you need at least two, separated far enough geographically that they're on separate electrical grids and in different natural disaster regions) can be spent on hardening your cloud presence, with plenty of money left over for other things.
If you're truly concerned about a single provider, use Terraform or Serverless to spread your infrastructure across multiple providers. Complexity goes way up, however, and the incremental benefit over using multiple regions in a single provider probably isn't worth the investment.
As an example, Google's SRE discipline is aimed at hitting 99.99% reliability. Anything over that isn't going to be noticed by users and the incremental improvements are cost-scaled way out of proportion to the improvements.
Companies I've worked for have had issues from 3rd party SaaS vendors way more often than the IaaS cloud providers. In the past 8 years I can think of 2 times where we were directly affected by a cloud provider's issues, and maybe 2 or 3 times indirectly. Having said that, avoid AWS' us-east-1 as most of the issues seem to happen in that region.
If you're truly concerned about a single provider, use Terraform or Serverless to spread your infrastructure across multiple providers. Complexity goes way up, however, and the incremental benefit over using multiple regions in a single provider probably isn't worth the investment.
As an example, Google's SRE discipline is aimed at hitting 99.99% reliability. Anything over that isn't going to be noticed by users and the incremental improvements are cost-scaled way out of proportion to the improvements.
Companies I've worked for have had issues from 3rd party SaaS vendors way more often than the IaaS cloud providers. In the past 8 years I can think of 2 times where we were directly affected by a cloud provider's issues, and maybe 2 or 3 times indirectly. Having said that, avoid AWS' us-east-1 as most of the issues seem to happen in that region.