I haven't done experiments to measure downtime on Azure myself. SLAs are tricky once you dig very closely into the details. If I recall correctly, years ago whe

I haven't done experiments to measure downtime on Azure myself. SLAs are tricky once you dig very closely into the details. If I recall correctly, years ago when Google Cloud came out that they defined "uptime" as "responding at least once within a 10 minute period", so that a service that's online for 1 minute, then is offline for the next 9 minutes...is still considered to have 100% availability from an SLA perspective. Moreover, your actual costs from the cloud vendors is often tricky and muddled, given they have some many different ways to charge you. For managed databases, this often includes things like some backup storage costs, bandwidth costs for ingress/egress, etc. All of that is "included" in our flat pricing. But the biggest thing: Timescale Cloud is not offering an undifferentiated Postgres offering. It's the only place to get the best version of TimescaleDB. And in many cases, this will /save/ you money. For example, TimescaleDB's native compression typically gets 94% bandwidth reduction. So the 500GB on Timescale Cloud is equivalent to paying for 8TB on Azure or AWS. And without all the other TimescaleDB features, including performance improvements of executing queries against compressed data.