Monitors
Every kind of check we can run, exactly when each one fails, and the settings they share.
-
How monitoring works
Intervals, regions, and the exact rule that decides when an incident opens.
-
Settings every monitor has
Interval, timeout, failure threshold, regions, latency alerts, pausing and deleting.
-
Choosing a monitor type
Which of the types answers your question, and which one people pick by mistake.
-
Reading a monitor's page
What the uptime figures, the chart and the result bars are telling you.
-
HTTP(s)
Is the site answering? The workhorse check, and the one with the most ways to be fooled.
-
Keyword
Is the right page being served? HTTP plus a search of the body.
-
SSL certificate
Is the certificate valid, trusted, and not about to expire?
-
DNS
Do the records still resolve, and still point where they should?
-
Ping
Is the host answering ICMP? Simple, and blocked more often than people expect.
-
Port (TCP)
Is something listening on that port and accepting connections?
-
UDP
Is your DNS, NTP, STUN or custom UDP service replying?
-
API
A separate type for API endpoints — which today behaves exactly like HTTP.
-
Content freshness
Has something stopped being updated? For feeds, exports and dashboards that go stale silently.
-
Heartbeat
Did the scheduled job actually run? The monitor that waits to be told, with copy-paste examples.
-
Content change
Tell me when this page changes. Never goes down; just announces.
Still stuck?
If this did not answer your question, tell us and we will fix the page as well as answer you.