Monitor Feature

Watch your site — and the APIs behind it — confirmed before you’re alerted.

HTTP/HTTPS monitoring with real request configuration. Methods, auth, headers, body, custom status codes, SSL expiry. Three consecutive failed checks confirm an incident before you’re paged.

The Problem

A homepage check tells you the site loads. It doesn’t tell you the API works.

Most uptime tools hit your homepage with a generic GET and call that "monitoring." But your customers are on a checkout endpoint behind auth, a webhook that needs a real POST body, or an API that returns 200 with the wrong status code in the JSON. Watching one path doesn’t cut it. The Monitor Feature lets you check the actual request — the way it really runs.

Real Endpoint Monitoring

Configure the request the way it actually runs.

Six layers of configuration — the same depth you get in tools that cost ten times as much.

Pick the HTTP method

HEAD (default — lightest, no body transfer), GET, POST, PUT, PATCH, DELETE, OPTIONS. Test real endpoints the way they actually behave.

Authentication

Basic or Bearer auth. Monitor endpoints behind a login or token — not just the public homepage.

Custom headers

Add any key/value pairs: API keys, bearer tokens, content negotiation, custom routing. Multiple headers per check.

Request body + JSON toggle

Send a real payload with POST/PUT/PATCH. Flip the JSON toggle to send as application/json instead of form-encoded.

Custom Up status codes

Defaults to 2xx and 3xx. Allow 404 on a search endpoint, flag 401 as failure on an auth-protected route — your call.

SSL & domain expiry

On HTTPS checks, we track certificate validity and domain expiry — and warn you before either lapses.

Checks run from 2 US monitor locations (EU expansion planned). Intervals from 5 minutes (free tier) down to 1 minute on paid plans.

Multi-Probe Confirmation

The evidence is captured at the moment of failure.

When your monitor catches a problem, our global probe network fires automatically on the third failed check — so when your engineer gets the alert, the forensic data is already attached.

The verification runs the moment the issue is happening — not 5 minutes later when you’re trying to reproduce it. A situation report with the regions, routes, and response codes is attached to the incident in your dashboard before your engineer even opens the alert. The first question — “where is this happening?” — is already answered.

Field Setup

Live in three steps.

1

Paste your URL

Your website page or an API endpoint. HTTP or HTTPS, no DNS changes, no code.

2

Configure the request

For simple uptime, defaults just work. For APIs: pick the method, add auth, custom headers, a body, and which status codes count as healthy (default 2xx/3xx).

3

Set alerts & save

Email, SMS, Slack, Teams, or webhook. 3 consecutive failed checks confirm an incident before you’re paged.

Stand-By for Deployment

Stop guessing if your endpoints are up.
Start watching them properly.

Free forever tier. Setup in 5 minutes. No credit card.

No credit card Free 5-min checks 1-min on paid plans Cancel anytime