For business

Uptime monitors

A monitor checks one target on a schedule, from residential and datacenter nodes in the countries you pick.

On this page

Create a monitor
Check types
Intervals, regions & per-run credits
Targets
Verified targets, email alerts & webhooks
States
Edit, pause or delete a monitor

Create a monitor

Open the business dashboard
Go to Dashboard, Business and press New monitor.
Describe the check
- Monitor name: what you want to call it.
- Target host or HTTP(S) URL: what to check.
- Check type: HTTP (HEAD or verified GET), TCP connect, or ICMP ping.
- Interval: 5m by default, or 60s / 30s on verified domains.
- Regions: any available node (ANY), or 1 to 3 online countries showing exact live node counts.
- Notifications: Email me on outages (alert_email, enabled by default) and optional HTTPS webhook URL + signing secret.
Create it
Press Create monitor. Click the monitor's title or Inspect at any time to open 24-hour p50/p95 latency charts, regional breakdowns, and latest probes.

Check types

Type	What it does	Target must be verified
HTTP (`HEAD`)	Lightweight status and phase-timing request on standard web ports	No
HTTP (`GET`)	Full HTTP GET check with custom path and port support	Yes
TCP connect	Opens a TCP handshake and closes cleanly	Yes
ICMP ping	Sends echo packets to measure RTT and loss	Yes

Intervals, regions & per-run credits

A monitor runs every 5 minutes (300s) by default. Intervals of 60 and 30 seconds are unlocked once you verify domain ownership. For regions, choose Any available node or pick up to 3 active countries from the live coverage directory.

Each scheduled run charges 1 credit per stored probe result (credits_per_run shows the expected vantages per cycle). If your available credit balance drops to 0, scheduled runs are skipped with skipped_reason: "insufficient_credits" without opening false outage incidents, and resume automatically as soon as credits are available again.

Targets

A target can be written as:

A hostname or an IP address: example.com
A host and a port: example.com:8443
A URL: https://example.com/healthz
An IPv6 address in brackets: [2001:db8::1]:443

A monitor refuses:

An address with a username or password in it.
A #fragment.
A scheme other than http or https.
A port or a path on a ping check, and a path on a TCP check.

Verified targets, email alerts & webhooks

Until you prove that a host is yours, Hopbits checks it gently: HEAD requests only, on standard web ports, without a query string, and no more often than every 5 minutes.

Verify the target via DNS TXT or /.well-known/ HTTP file to unlock 30s/60s intervals, HTTP GET, custom ports, TCP connect, and ICMP ping. You can re-verify (POST /v1/targets/{id}/verify) or remove (DELETE /v1/targets/{id}) verified domains at any time.

Every monitor enables Email me on outages (alert_email: true) by default so outage and recovery transitions reach your verified account email. You can also attach an HTTPS webhook_url and webhook_secret to receive X-Hopbits-Signature callbacks (check.down, check.degraded, check.up), and press Test webhook (POST /v1/checks/{id}/test-webhook) to deliver a signed check.test event immediately.

States

State	Meaning
Up	The target answered within threshold.
Slow	It answered, with elevated latency or partial degradation.
Down	Regional quorum confirmed the target did not answer.
Pending	Awaiting the first scheduled check run.
Paused	Paused via console or `PATCH /v1/checks/{id}`.

Edit, pause or delete a monitor

Open a monitor's drawer (or call PATCH /v1/checks/{id}) to update its name, interval, regions, HTTP method or path, outage email toggle, or webhook configuration. Press Pause / Resume in the table row or drawer, or Delete (DELETE /v1/checks/{id}) to remove the monitor.