An HTTP monitor checks that a URL returns the response you expect, on a schedule, from the regions you choose. This guide covers how the check works and how to configure it.
Stector sends a request to your monitor's URL on the interval you set, from each region you've enabled. Each individual run either matches your expected status code or it doesn't — there's no retry of the request itself. A monitor's status only flips to down once enough regions agree the endpoint is failing (see Regions and intervals below).
From /dashboard/monitors/new, choose HTTP monitor and set:
200. Stector compares this as an exact match, not a range: a monitor expecting 200 treats a 204 response as a failure.Once a monitor is created, its type can't be changed. On the edit page at /dashboard/monitors/[id]/edit, Monitor type appears as a read-only label instead of a dropdown.
Under Authentication, choose one of four types: None, Bearer token, HTTP Basic, or Custom header. Basic adds a Username field alongside the secret; Custom header adds a Header name field (for example X-API-Key) alongside the secret.
If a monitor has authentication configured and the endpoint responds with a redirect, Stector treats that as a failure rather than following it — forwarding an Authorization or custom header to a redirect target could send your credentials somewhere you didn't intend. Point the monitor's URL at the final destination instead.
When editing a monitor that already has a secret saved, leave the secret field blank to keep the existing value. Stector only replaces it when you type a new one.
Monitors run from three regions — US East, EU West, and Asia — on a Check interval from 1 minute to 1 hour. A region counts as failing once it has recorded two consecutive failing runs. Stector then requires at least two regions to agree — or if you've enabled only one region, that region decides on its own — before flipping a monitor to down.