How IsItUp works

A clear path from signal to action

Every monitor follows a bounded workflow: validate the destination, run the right kind of check, classify the result, and preserve useful context for your team.

01

1. Choose the signal

Add an HTTP, HTTPS, DNS, ping, or TCP monitor depending on the service you need to observe. Configure the interval, timeout, expected responses, and optional request details allowed by your plan.

02

2. Validate safely

Public destinations are checked before network requests run. Private, reserved, loopback, link-local, credentialed, and unsafe redirect targets are rejected.

03

3. Execute and measure

The monitoring engine records the check status, HTTP result where relevant, response time, redirect path, TLS or DNS errors, and the failure category.

04

4. Confirm incidents

Optional failure and recovery confirmation thresholds prevent a single transient result from becoming an unnecessary alert.

05

5. Notify and recover

Email and configured webhook channels receive incident and recovery events. Maintenance windows can mark expected work without changing historical evidence.

06

6. Review reliability

The dashboard provides uptime overview, issue lists, response-time views, incident history, analytics, and exports for the retention and reporting periods your account allows.