Monitoring

Healthcheck Types

Uptimy supports 9 healthcheck types for monitoring any service, from REST APIs, gRPC endpoints and MCP servers to DNS records and SSL certificates. Choose the right check type for your infrastructure.

Overview

Every healthcheck in Uptimy shares a common set of features that make monitoring flexible and reliable. Regardless of check type, you get configurable intervals, timeout settings, multi-node monitoring, and a powerful tagging system to organize your checks.

Common Features

FeatureDescription
Check IntervalThe shortest interval each plan allows: Free every 5 minutes, Starter every 60 seconds, Growth every 30 seconds, Scale every 15 seconds, Enterprise custom. Browser checks run at most every 5 minutes on every plan.
TimeoutConfigurable timeout per check. If the target does not respond in time, the check fails.
Active / Pause TogglePause and resume any healthcheck without deleting its configuration or history.
Manual TriggerRun any healthcheck on demand with a single click to verify changes instantly.
Tag SystemOrganize checks with custom tags, under Details, for filtering lists, routing alerts with workflow Filter nodes, and reports by tag. Heartbeats take the same tags.
Multi-Node MonitoringRun checks from multiple geographic locations to detect regional outages.

Choosing the Right Check Type

If you're monitoring a web application, start with an HTTP check. For microservices, consider gRPC or TCP checks. Use Heartbeats for cron jobs and background workers that should report in on a schedule.

Available Healthcheck Types

Click on any check type below to learn about its configuration options, response data, and best practices.

Heartbeats Are a Standalone Feature

Scheduled tasks and background jobs use a push-based model instead of pull-based checks. See Heartbeats for the dedicated setup and behavior.

How Healthchecks Work

When you create a healthcheck, Uptimy runs it at your interval from each region you pick. Each run produces a result with timing data, status information and response details.

When a run fails, the region reruns the check 10 seconds apart (twice by default, once for browser checks) before the failure counts. The check is Down once a majority of its regions confirm the failure. If fewer regions fail, or it gets slower than you allow, it is Degraded. The incident conditions open an incident when it goes Down, or when it is Degraded with Alert when degraded on, and your workflows send the notifications.

All check results are stored and shown in your dashboard with response time graphs, uptime percentages and detailed logs. You can filter the list by name, tags, Runs on (Cloud or an agent) and status.

Confirmed by a Majority of Regions

Requiring a majority keeps one region's network trouble from looking like an outage. To change how many regions must confirm a failure, or how often a region rechecks, open the check's Alerting tab and use Confirm from and Recheck a failure.