Uptime monitoring & site status

What it does

On your plan's schedule, Monitrova requests each site and records whether it responded healthily, how long it took (total response time and time to first byte, TTFB), and the HTTP status. A run that fails is re-verified from a second network location before any "down" alert is sent — so a site that merely blocks our main IP (a WAF or geofence) doesn't trigger a false alarm.

Site status

Status	What it means
Up	The most recent check succeeded — a healthy status within the timeout.
Down	The most recent check failed from both locations — timeout, refused connection, bad status, or blocked.
Unknown	No check has run yet, or the site is archived.

Why a check can fail

Reason	What it means
Timeout	No response within your timeout setting — the server is slow or unreachable.
Connection refused	The server actively rejected the connection — it may be down.
Bad status code	A response that doesn't match your expected status (e.g. a 500 or 404).
SSL error	The HTTPS connection failed (often a certificate problem) when Verify SSL is on.
Blocked	A firewall or bot-protection challenge blocked the request. The second location helps confirm whether the site is truly down.

Good to know

• Response time and TTFB are recorded on every check — see them on the site detail and the response-time chart.
• A high TTFB points at a slow backend; a high total with low TTFB points at page size/transfer.
• The second-location re-check only happens after a failure, to suppress false "down" alerts — confirmed by the check's vantage detail.

Related guides

• Incidents
• Your dashboard
• Uptime Checker