Uptime Checks across clouds
Synthetic probes from outside the cloud - Route 53 health checks, Cloud Monitoring uptime checks, OCI Health Checks - with the alert that turns a failure into a page.
3 verified modules - all static-validated and publish-checked; live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | A Route 53 Health Check with the Alarm that Makes a Failure a Notification | static-validated |
| Google Cloud | An Uptime Check with the Certificate Validated and the Alert Policy that Pages | static-validated |
| Oracle Cloud | Uptime Monitors that Probe from Three Places and Feed an Alarm | static-validated |
How to choose
Compare where the probes come from and whether their addresses are published (an endpoint behind an allow-list needs them), the fastest interval and what it costs, whether the check can assert on the body rather than the status code, and what a failure does: a DNS failover, an alert policy, or a graph nobody watches.
When not to use
An uptime check proves the endpoint answered a probe from a public address; it does not prove your users can reach it, and a private endpoint cannot be checked this way at all. The alert is the product; the check is the sensor.