Get up and running in under five minutes.

Quickstart

Sign up, add your first check, plug in a notification channel. That's it.

1. 1. Create an account

   Head to app.upclock.dev and sign in. Free Hobby plan, no credit card.

2. 2. Add a check

   Click Create Service, paste a URL, set the interval. We start checking it from global edge nodes within seconds.

3. 3. Connect a channel

   Add an email, Slack workspace, or webhook in Channels. We page you when three consecutive checks fail.

4. 4. Publish a status page (optional)

   Group checks into a public status page at your-brand.upclock.dev or a custom domain.

HTTP Checks

The most common check type. Verifies your endpoint returns the response you expect.

What we verify

• Status code (default: any 2xx)
• Response body contains a substring (optional)
• Response time under a threshold (optional)
• Custom headers, methods (GET/POST/HEAD), and request bodies
• Follow redirects (up to 5 hops)

Intervals

Hobby checks run every 3 minutes. Pro drops to 30 seconds. Team drops to 10 seconds. Faster intervals mean shorter detection time during incidents.

Timeouts

Default request timeout is 30 seconds. Anything slower is treated as a failure.

TCP Checks

For services that don't speak HTTP — databases, SSH, mail servers, custom protocols. We open a TCP connection on the port you specify and confirm the socket accepts the connection.

Host:     db.example.com
Port:     5432
Interval: 60s
Timeout:  10s

A check passes if the TCP handshake completes within the timeout. We don't send a protocol-level payload — that's up to you to verify out-of-band.

DNS Checks

Resolve a hostname and verify the record matches what you expect. Useful for catching DNS hijacks, misconfigurations after a registrar change, or stale CDN entries.

Supported records

• A — IPv4 address
• AAAA — IPv6 address
• CNAME — alias
• MX — mail exchange
• TXT — text records (SPF, DKIM, verification)

Channels

We send an alert when a check has failed three consecutive times, and a recovery notice when it has succeeded twice in a row. This is the "low-noise" part — single blips don't page anyone.

Available channels

Webhook payload

{
  "event": "incident.opened",
  "incident_id": "inc_8f3a...",
  "service": "API Gateway",
  "url": "https://api.example.com/health",
  "status": "down",
  "started_at": "2026-05-09T14:21:03Z",
  "error": "connection refused"
}

Status Pages

Publish a public page that shows component health, current incidents, scheduled maintenance, and a 90-day uptime history. Customers can subscribe to email updates.

Components

A status page is composed of components (e.g. "API", "Web App", "Background Jobs"). Each component is backed by one or more checks. When all backing checks are healthy, the component shows operational.

Custom domain

Point a CNAME at cname.upclock.dev and we'll provision an SSL certificate automatically.

Private pages

Pro plans support password-protected status pages, useful for staging or internal-only systems.

SSL Monitoring

For HTTPS checks on Basic and Pro plans, we track the certificate expiry and send a warning notification 30, 14, and 7 days before expiration. If a cert ever serves an unexpected hostname or chain, you'll know.

SSL monitoring runs as part of the regular HTTP check — there's no separate check type to configure.

FAQ