Getting started

From signup to a running check in a few minutes, and what a sensible first hour looks like.

First check

  1. Create an account. Signup runs on Datargo, the company behind Perstat; no credit card. The free plan is not a trial clock: 10 monitors at 300-second intervals, 1 public status page, no time limit.
  2. Point a monitor at a URL. Pick http, paste the URL, keep the defaults. The monitor probes from multiple continents and confirms by quorum before it ever alerts; there is nothing to tune for that, it is the rule.
  3. Watch the first results. Per-region latency, per-IP results for dual-stack targets, and DNS time separated from total time arrive with the first checks.

A sensible first hour

  • Add an ssl_cert monitor for the certificate you always forget, and a domain monitor for the registration layer (NS, DNSSEC, WHOIS expiry). The check types each explain what they verify.
  • Create your status page and pick the components worth showing. Public, or gated from Sentinel.
  • If you run on-call, verify your phone number (one-time code) so escalation can actually reach you. SMS and calls start at Sentinel.
  • Announce your first maintenance window before you deploy, not after; announced windows do not count against you.

Where things live

The cockpit is the live view across everything; History carries the raw timeline, the curated outage record, and the configuration audit. Every number you see feeds the same availability record your status page and your SLA conversation use. One record, no drift.