Create and configure monitors

In Monitors, add a check and choose its type according to what you need to verify. A website returning 200 can still fail if expected content is missing.

In Monitors, add a check and choose its type according to what you need to verify. A website returning 200 can still fail if expected content is missing.

Website and API

Set the name, URL, method and interval. Adjust the timeout and, where needed, headers, Basic Auth and request body. Require specific status codes, ranges or classes, response headers, present or absent text and a JSON value. Choose conditions that represent a correct response from your service.

Port, ping and DNS

A port check verifies a connection can be established; it does not prove the entire application works. Ping requires a check location with that capability. DNS can check answers or notify about changes. For a private service, select an agent allowed to reach that target.

Interval, confirmation and alerts

Your plan sets the minimum interval; checks below 60 seconds are not currently offered. Public checks can be retried and confirmed from other regions before declaring an outage. In Alerts choose all channels, selected channels or none. Without channels the monitor keeps checking and recording incidents.

History and response time

Open a monitor to see recent checks, incidents and periods without data. Where the time goes shows phases its source could measure. DNS, connection, TLS, first byte and download require a compatible agent; other locations provide less detail. A missing phase is not zero.

Import and export

CSV import supports web, port, DNS, certificate and domain checks, up to 200 rows. Review validation and per-row errors first. Creation respects plan limits; inspect the result before repeating an import. Export downloads supported configuration, not a credential backup.