You see each failed check by region, you choose how many failures must stack up before an alert, and you can export the history.
Uptime monitoring is useful when you need a record of whether an endpoint answered, not a recording of a user clicking through the product.
- Regional results. Every run includes the region, status, and response time, so one location can be compared with the rest.
- A fail count you control. A channel alerts after the consecutive failures you set. Set it to 1 when the first failure should page someone.
- History you can export. Download results as CSV, add a note for a maintenance window, and run a one-off check after a deploy.
Public status pages are a separate product. They can show availability to customers. They are not built into the uptime check itself.