If you work with government, the SLA's are so tight that this will never be feasible. Large SaaS and infrastructure providers consistently game uptime metrics t

If you work with government, the SLA's are so tight that this will never be feasible. Large SaaS and infrastructure providers consistently game uptime metrics to reduce breach related refunds and compensation. For one major provider I saw them count as "service uptime is calculated by contacting the service once every minute of the day, if the service is contactable within any period of that 60 seconds, it is considered up". So if you healthcheck request typically responds in 200ms, but their internal infra falls over and it takes 59800ms instead - it's still considered "up", not even degraded. This is stretched further with some providers to the point where they consider returning the header of an HTTP request as "response returned", before any body is sent. So they'll stand-up networking infrastructure when something falls over to hold millions of connections while they fix the backend to actually serve the content.. Eventually. Often you'll find this isn't even contractually well-defined and is only given to you after an outage and you question their reporting. They expect you to take them to court if you disagree with this definition.