Uptime monitoringAll features.
Everything Uptime monitoring does today: what one check is, what is kept, how an alert reaches you, and what each plan includes.
27 features in 6 groups, checked against the product on 14 November 2026.
Checks
One request per check
Each check is one HTTPS request for the site's home page, sent from Cloudflare's network. Redirects are followed.
Up means a 2xx answer
The site counts as up when the final answer has a 2xx status. Any other status, no answer within 10 seconds, or a network error counts as down.
Every 5 minutes
On every plan a site is checked every 5 minutes from the moment it is verified.
Every minutePro and Business
You can set any site to be checked every minute. A new site starts at 5 minutes until you change it.
Starts on verification
Monitoring begins within a minute of the DNS record being confirmed. There is nothing to install on the site.
Run checks now
A button on the overview checks every verified site at once, at most once every 30 seconds. It records the results; it does not send alerts.
A recognisable user agent
Checks are sent as BCDRPulse-Monitor/1.0, so you can find them in your logs or allow them through a firewall.
What is recorded
Every check's result
Up or down, the status code, the response time in milliseconds, the error if there was one, and the time.
30 days of history
Check results are kept for 30 days and then deleted.
Status and last change
Each site shows whether it is up or down, when it was last checked and when its status last changed.
A log of alerts
Every alert is logged with where it was sent and whether it was delivered.
Alerts
When a site goes down
An alert goes out when a site that was up fails a check. One failed check is enough: nothing checks a second time first.
When it recovers
A second alert goes out when the site answers again, so a long outage is two messages and not a stream.
Email
From alerts@bcdrpulse.com, with the status code, the response time, the time it was detected in UTC and the error.
Webhook
A JSON POST to an HTTPS address you give: the event (monitor.down or monitor.up), the host, the status code, the response time, the error and the time. The request is not signed.
Channels belong to the account
Every email address and webhook you add receives every alert for every site.
Recent alerts
The Alerts page lists the latest 25: the site, down or recovered, where it was sent, and delivered or failed.
Dashboard
Overview
The number of verified and pending sites, an uptime percentage from the most recent checks, the average response time of the last 50 successful checks, and the checks made today.
Response-time chart
The latest 30 response times across your sites.
A row for each site
Its status, uptime percentage, last response time, latest security scan grade and the time since the last check.
Ownership and safety
Proof by DNS record
You add a TXT record at _bcdrpulse on your domain, with a value from your dashboard. Only verified sites are checked.
Public sites only
IP addresses and internal names are refused as sites, and a webhook must be an HTTPS address on a public host.
Removing a site removes its data
Removing a site deletes its checks and its alert log. Deleting your account deletes all of them.
Plans and limits
Free
10 sites, checked every 5 minutes, with email and webhook alerts.
Pro
25 sites, checked as often as every minute.
Business
100 sites, checked as often as every minute.
Unverified sites count
A site you have added but not yet verified counts towards the plan's number of sites.
What it does not do.
- It checks from one place, once. There is no second location and no retry before an alert, so a brief network fault between us and your site can read as an outage.
- It checks the home page over HTTPS only: no other path, no search for a word on the page, and no status other than 2xx can be set as healthy.
- It has no status page, maintenance windows, SMS or chat alerts, and no export or API.
- It does not test your backups, failover or restore. It tells you whether the site answered.