# Uptime checks for your sites, APIs and cron jobs Uptime checks them from the same dashboard and alert channels as your tunnels, and they're free while Uptime is in beta. [Start Free Trial](https://app.tunnelhq.com/register) [Read the docs](https://docs.tunnelhq.com/uptime/) ## Five checks and a heartbeat Pick what counts as down: a site, an API, a page's text, a host, a port, a DNS answer or a job that stops checking in. ### Website, keyword, ping, port and DNS Each has its own idea of down, from a status outside 200–299 to a DNS server that answers with the wrong address. More: https://docs.tunnelhq.com/uptime/ ### Heartbeats for cron jobs and backups Your job calls its address each time it runs, so a missed call, /fail or a non-zero exit code sends the alert. More: https://docs.tunnelhq.com/uptime/heartbeat/ ### Certificate and domain expiry Website and keyword checks warn up to two months ahead, and close the warning themselves once you renew. More: https://docs.tunnelhq.com/uptime/checks/#ssl-and-domain-expiration ## Confirmed before anyone is paged A failed check is checked again before it opens an incident, and the alert goes where your tunnel alerts already go. ### One incident, one alert A failure waits out the confirmation period, two minutes by default, and only a second failure opens an incident and alerts. More: https://docs.tunnelhq.com/uptime/checks/#how-a-check-goes-down ### Acknowledge, retest, move on The incident says what failed and where, and you can acknowledge it or run the check again from it. More: https://docs.tunnelhq.com/concepts/incidents/ ### The channels your tunnels use Checks alert through the same 20 channels: Slack, PagerDuty, Telegram, email and the rest. More: https://tunnelhq.com/integrations/ ## Or let your AI assistant set it up Paste one prompt into your assistant and review what it found before anything is added. ### Connect once Sign in from Claude, ChatGPT, Cursor or VS Code. There's no API key to copy. More: https://tunnelhq.com/ai/ ### It asks before it adds One prompt from the empty Uptime page finds the sites, APIs, ports and jobs you run, and waits for your OK. More: https://tunnelhq.com/ai/ ### Every check tested After your yes it adds them and reports each one's first result. More: https://tunnelhq.com/ai/ ## Defaults and plans A new check starts with these settings, and your plan sets how often it can run and where from. SettingDefaultYou can choose Check frequencyEvery 3 minutes20 seconds to 30 minutes Confirmation period2 minutesImmediately to 5 minutes Request timeout30 seconds5 to 60 seconds RedirectsFollowed, up to 10Or judge the redirect itself Certificate checkOnOff accepts self-signed IP versionIPv4 and IPv6Or only one of them PlanShortest frequencyChecks from StarterEvery 30 secondsMain location ProEvery 20 secondsSeveral locations BusinessEvery 20 secondsSeveral locations EnterpriseEvery 20 secondsSeveral locations ## Questions ### When does a failed check alert? It waits out its confirmation period, 2 minutes by default, and checks once more. Only if that fails too does it go Down, open one incident and alert every channel on the check. A blip that clears in time leaves nothing behind. With the period set to Immediately, the first failure alerts. Tunnels work a little differently: their first failure opens a Degraded incident, and the alert waits for the next check. ### Do Uptime checks count against my plan? No. Uptime checks are free during the beta and don't count toward your plan's tunnels. Heartbeats are Uptime checks too. ### Can a check run from several places? On Pro and up. It's Down only when most of its locations see it down, such as 2 of 3. Fewer is Partial, which alerts only if you turn that on. ### How does a heartbeat decide a job is late? You set how often the job runs, up to once every 7 days, and a grace period, 1 hour by default. If no call arrives within both, or a call reports /fail or a non-zero exit code, it goes Down and alerts at once. The address is shown only to people who can edit checks. ### What about certificates and domains? Every https address has its certificate watched, 14 days ahead by default. Domains are opt-in, with the date read from the registry; some, such as .de, publish none, and the check says so. Either one opens an amber Expiring incident that closes itself on renewal. ### Can it watch something on my private network? No. Checks connect from TunnelHQ's servers, so private and reserved addresses such as 10.x.x.x and 192.168.x.x are refused when you save. ### Can I add many at once, or from code? Paste URLs one per line in Bulk import: duplicates are dropped and anything that isn't a web address is reported. The [REST API](https://docs.tunnelhq.com/api/), the [thq CLI](https://docs.tunnelhq.com/cli/) and the [MCP server](https://tunnelhq.com/ai/) create, change and pause checks too. ### Can I group checks? Yes, by site or customer. A group shows its worst status and how many of its checks are up, and never alerts on its own. Source: https://tunnelhq.com/uptime/