What is uptime monitoring?
Uptime monitoring checks whether the services your customers depend on are available, responsive, and behaving as expected.
What uptime monitoring checks
A monitor runs a check on a schedule and turns the result into a clear operational state. That can be an HTTP response, a TCP connection, a DNS answer, a ping, a browser journey, or a heartbeat sent by your own job. KEEPitALIVE records response time and history alongside the current state.
Set up a monitor
Choose the signal that best matches the thing you need to prove, give it a useful name, set the target and check interval, then choose who should be alerted. Use an HTTP or API monitor for a reachable endpoint; use Browser when the actual user journey matters; use Heartbeat when your job or worker must report completion.
Measure the signal that matters
A successful 200 response does not always mean the product works. Check an expected status or response body for an API, monitor a browser flow for login or checkout, and use a heartbeat for scheduled work that could silently stop. Pick the narrowest monitor that proves the outcome you care about.
What happens when a check fails
KEEPitALIVE records the state transition, opens or updates the relevant incident, and routes notifications through the channels you configured. Triggers can send signed webhooks, create a custom notification, or run incident actions. A later healthy result records recovery and can resolve the operational loop.
Continue from here
Use the monitor-type guide to choose the right check, Quick Start to create the first one, and status pages to share a deliberate, sanitized view of service health.