Skip to content

FAQ

Yes. The free plan includes 50 monitors, checked every minute, with 30 days of incident history.

Sign in with GitHub, Google, Microsoft, or email. With GitHub or Google, neither provider has you type in an address. Email sign-in is the exception: you enter one directly. GitHub sign-in still needs a verified primary email on GitHub’s side regardless of what you type — sign-in fails outright if GitHub reports none, or only an unverified one. We normally store whatever address GitHub returns as your account’s email, the same as a direct email sign-in — except we skip saving it if your account already has an email on file, or if that address already belongs to a different account. Google sign-in needs no email address you separately enter or that we store — Google’s authorization response includes a verified address, which we use transiently for trusted-domain checks and to match it against existing accounts for linking purposes, but the address value itself is not persisted. And recipients for alerts can be webhooks instead of email. See the sign-in guide.

Webhooks, browser push, email, RSS feeds, and MCP queries. See Webhooks, Push notifications, and the email alerts guide.

Infrastructure-class failures are re-checked from two additional regions. State only changes when 2 of 3 regions agree. See Monitors for details on cross-region confirmation.

Yes — the uptimemonitoring/assert-healthy action is built for deploy verification. See GitHub Action.

Can I monitor private IPs or internal services

Section titled “Can I monitor private IPs or internal services”

No. Private and reserved targets are blocked. See Security for details on target restrictions.