Most cross-cloud outages are not discovered by users first. They are discovered late, because the health check kept reporting green while the real private path was already broken.

That happens for a simple reason. The probe is not travelling the path the application travels. It checks a public endpoint from the internet, or it checks a service from inside the same cloud, and then everyone assumes the link between clouds is fine. When the private route, the DNS view, or the firewall rule in the middle fails, the dashboard stays green and the application fails anyway.

Honest probing is not about adding more checks. It is about placing the checks where the traffic actually goes, and making each check fail for one clear reason at a time.

The three paths that get confused

A typical multi-cloud service has at least three different paths that can each be healthy on their own:

The public path. A load balancer or public endpoint that anyone on the internet can reach.

The intra-cloud path.…