Every layer.
The right signal.
Availability, resources and background work. Find the monitor that fits what you run, then keep the results together in one clear workspace.
What would you like to watch?
Choose a check for the layer you need to understand. External probes, host metrics and signals from your applications answer different questions.
Uptime monitoring
Know when your website stops answering, slows down or returns the wrong content. Keep availability, response times and the details of every check together in one workspace.
ExploreHost monitoring
Bring CPU, memory, disk, load and process metrics into the same workspace as your service checks. See the machine behind the response, with thresholds that suit the way it runs.
ExploreSSL monitoring
Watch certificate validity and renewal dates before a browser warning becomes the first sign of trouble. Give every important HTTPS service a clear certificate health check.
ExploreDomain monitoring
Keep registration expiry dates in view and get renewal warnings before a missed payment affects your website, email and the services behind your name.
ExploreAPI monitoring
Check more than a status code. Send the request your endpoint expects, validate JSON and response headers, and see when a healthy-looking API stops doing its job.
ExplorePing monitoring
Watch network reachability with ICMP checks from your selected regions. Follow latency, packet loss and regional differences for the machines and devices you depend on.
ExplorePort monitoring
Check whether a public TCP service accepts connections. Watch mail, SSH, database gateways and other listeners that need a more focused check than a website monitor.
ExploreIP monitoring
Monitor public IPv4 and IPv6 reachability directly. Keep an address-level view of latency and packet loss without depending on a hostname lookup.
ExploreDNS monitoring
Watch the DNS records your services depend on. See lookup results, returned values and TTLs in a focused monitor built for the layer before the connection.
ExploreHeartbeat monitoring
Watch backups, scheduled scripts and background jobs without giving them a public URL. Let each successful run check in, and get a signal when the expected heartbeat is missing.
ExploreLog monitoring
Turn application log patterns into monitoring signals. Watch error counts, specific messages or a service that has gone quiet, alongside the availability checks for the same stack.
ExploreBuild a useful set of checks
Start with a website or API check for your customer-facing service. Add DNS, SSL and domain checks to watch dependencies that can interrupt an otherwise healthy application. Use ping, IP or TCP port checks when network reachability is the question.
For the machine behind the service, connect host metrics. For scheduled work, add a completion heartbeat. When the application is producing errors or has gone quiet, use a focused log rule. These signals complement one another; none of them alone proves that every customer journey works.
Choose alert destinations and failure thresholds that make the result actionable. A clear monitor name and an owner are often as useful as another chart.
Compare monitor behavior