Know when something is down or weakened before your users do.
The load balancer reports healthy, users hit errors, and the team finds out from a ticket. Meanwhile a DNSSEC signature lapses or a DMARC record is edited, and nothing fails a build or pages anyone.
Internal checks connect from inside.
A health check behind the load balancer answers for the process, not for the path your users take through DNS, TLS, and the edge.
Posture changes do not look like outages. A DNS record edited by hand, an SPF record that grew past the lookup limit, a DMARC policy quietly relaxed: none of these break anything today, and each one is found later by someone else.
During an incident, people need somewhere to look. Without a page that says what is known, the answer is the support queue.
Probes from outside, alerts on change, and a page your users can read.
Dependably StatusCheck probes the assets you operate from outside your network, the way your users reach them, and treats a change in state, grade, or record as the event to tell you about.
Probe on a schedule
Uptime probes run over HTTP or TCP every 60 seconds by default, and over ICMP when the container is allowed to ping. A failure is retried before anything is declared down, so a single dropped packet is not an incident.
HTTP · TCP · ICMPWatch posture for drift
DNS records and DNSSEC are checked on their own cadence, and SPF, DKIM, and DMARC are read for each domain. Each endpoint's TLS configuration carries a grade from A+ to F. A grade change, a changed record set, or a failing DNSSEC signature is an event.
DNSSEC · SPF/DKIM/DMARCAlert the team
An alert fires when a state changes, and a failed send is retried rather than lost. Alerts go to Slack, PagerDuty, or a webhook; status page subscribers are notified by email.
alertTell your users
The same change updates a public status page that ships without scripts. Schedule maintenance windows ahead of time and the page shows them while they run, post written updates as an incident unfolds, and subscribers hear when a host goes down or recovers.
status pageAn uptime figure built from the record, and a page you can point to.
Probe results are kept for the retention window you set, 90 days by default, and pruned after it. Each uptime figure is computed from them when it is read, so a maintenance window added after the fact still comes out of the figure, and deleting one puts its minutes back.
- Down is declared after retries, from outside, so it matches what users experience.
- A changed DNS record set, a failing DNSSEC signature, or a drop in TLS or email-authentication grade arrives as an alert.
- A public status page with maintenance windows, written incident updates, and subscribers.
- Heartbeats for scheduled jobs, so a backup that stopped running is reported.
- host checkout.example.com
- state up → down · after retries
- probe HTTPS · 502
- posted status page · subscribers notified
Self-hosted and open source.
Dependably StatusCheck is self-hosted and open source under Apache-2.0, and probes from wherever you run it. Our own public status page runs on it, so you can see it working before you install anything, and you can get in touch about your deployment.