Features
Everything, and nothing you did not ask for.
Corveto does one job. These are the parts of it.
Checks from twelve regions
Every endpoint is checked from twelve locations at once. A failure has to be seen from at least three before anyone is woken up.
Alerts that reach a person
Escalation policies with working-hours rules, on-call rotations and a fallback that keeps trying until someone acknowledges.
Status pages your customers trust
A hosted status page on your own domain, updated from the same checks that page your team.
Certificate and domain expiry
Warnings at thirty, fourteen and three days, so the outage that never happens is the one nobody remembers.
Response-time budgets
Set a threshold per endpoint and get told when the ninety-fifth percentile crosses it. Slow is a kind of down, and it usually arrives first.
An API for everything
Every monitor, incident and status update is readable and writable over a documented REST API.
How a check works.
Every monitor runs from twelve regions on your chosen interval. A region reports a failure only after the request times out or returns an unexpected status twice in a row.
When three regions agree, the incident opens and your escalation policy starts. Until then nothing is sent, because a single unhappy network path is not an outage.
