Uptime checks
Pointsman checks each service once a minute and only raises the alarm when two regions agree it is down.
60 s
between checks
6
regions checking
90 days
of history on the board
Two regions must agree
A failed check is retried from elsewhere before anyone gets paged.
Five kinds of check
Watch APIs, pages, SSL certificates, DNS records and cron jobs from one list.
Ninety days on the board
Each bar is one day. Hover it to see exactly what happened.
In detail
What a check does
Each monitor sends a real request from one of six regions once a minute. It records the status code, the response time and the certificate, then compares them with the rules you set.
Why two regions
One bad route should not wake anybody. When a check fails, Pointsman retries from a different region straight away. Only a second failure opens an incident.
What you can watch
HTTP and HTTPS endpoints, with status code and body rules
Keyword checks that fail when a page loses important text
SSL certificates and domain expiry, weeks ahead
DNS records that change without warning
Cron jobs that stop reporting in
All features
Uptime checks
Every service checked once a minute from six regions.
Incident timeline
One running record from the first failed check to the fix.
Status pages
A public page that updates before customers start asking.
On-call schedules
Fair rotations that everyone on the team can read.
Alert rules
Decide who hears about what, and how loudly.
Response time
Spot the slowdown before it turns into an outage.
