HTTP(S) monitors

An HTTP(S) monitor sends a request to a URL on a schedule and checks the response status code.

Settings

Setting	Default	Notes
URL	—	Must start with http:// or https://. Up to 2,048 characters.
Method	GET	GET, HEAD or POST.
Interval	Plan minimum	30s, 1m, 2m, 5m, 10m, 15m, 30m or 60m. Free: 5m minimum. Pro: 1m. Team: 30s.
Timeout	10 seconds	Between 1 and 30 seconds. A request that takes longer counts as a failure.
Expected status	200-299	Codes and ranges separated by commas, e.g. 200-299,301 or 200,204.
Follow redirects	On	Follows up to 5 redirects. With this off, a 301 or 302 is evaluated as-is.
Request headers	None	Custom headers, e.g. Authorization: Bearer <token> for a protected health endpoint.
Request body	None	Sent with POST. Up to 10,000 characters.

When a check counts as failed

• The connection fails (DNS error, refused connection, TLS error).
• No response within the timeout.
• The status code is outside the expected status list.

A failed check does not open an incident immediately. It is re-checked first; see False-alarm protection.

Examples

Health endpoint that returns 204

• URL: https://api.example.com/healthz
• Method: HEAD
• Expected status: 204

Login page that redirects

To check the redirect itself, turn off Follow redirects and set expected status to 302. To check the final page, keep redirects on and use 200-299.

Protected internal API

• Header: Authorization: Bearer <read-only token>
• Expected status: 200

Use a token with read-only scope. Header values are stored with your monitor configuration.

Request identification

Checks are sent with the user agent AsniherBot/1.0 (+https://asniher.com/bot). If a firewall or bot protection blocks unknown clients, allow this user agent for your health-check path.

Limits

Monitors can only target public addresses. Private and internal IP ranges (for example 10.0.0.0/8, 192.168.0.0/16, 127.0.0.1) are rejected. To monitor an internal service, use a heartbeat monitor and ping out from inside your network.