Check every minute, measure availability and response time, and send actionable downtime alerts through the channels your team already watches.
Basic uptime checks only prove that a server returned something. pingdan records each response and lets you define what healthy means, so an error page with a 200 status does not quietly pass. When failures cross your threshold, the right people get the status code, error, timestamp, and recovery notice they need to act.
Paste a public HTTP or HTTPS URL, name the monitor, and select a check interval and timeout.
Choose the expected status and add optional header, body, JSON, or latency assertions.
Attach email, chat, webhook, paging, push, SMS, or incident-management channels.
Understand availability checks, uptime percentages, and why a bare 200 OK is not enough.
Read guide →Balance detection speed and alert quality for websites, APIs, and background jobs.
Read guide →Learn what an actionable notification contains and how to choose the right delivery channel.
Read guide →Website uptime monitoring automatically requests a website on a schedule, evaluates whether the response is healthy, records the result, and alerts someone when the site fails or recovers.
One minute is a practical default for production websites because it keeps average detection time low. Less critical pages and background services can use longer intervals.
Yes. Applications sometimes return a branded error page, empty response, or broken JSON with a 200 status. Body and JSON assertions catch these false-positive healthy checks.
Yes. pingdan includes unlimited monitors, one-minute checks, assertions, alert channels, history, and status pages without a paid plan or credit card.
Create your first monitor in under a minute. Every feature is free.
Create a free monitor