Uptime Monitoring is Here

Drumbeats started as a cron job and background job monitor. Today it also watches your websites and APIs.

Add a URL, choose a check interval between 1 and 5 minutes, and Drumbeats will start pinging it. If your endpoint goes down, you get notified through the same channels you already use — Email, Slack, Telegram, Discord, Webhook, or Browser Push.

What shipped

HTTP checks with configurable intervals

Create an uptime monitor by entering a URL. Drumbeats sends an HTTP request at your chosen interval (1, 2, 3, or 5 minutes) and records the result. You see status codes, response times, and errors in a check results table on the monitor detail page.

Response time tracking

Every monitor gets a 24-hour response time chart showing Avg, P95, Min, and Max stats. You can spot degradation before it turns into downtime — a creeping P95 is often the first warning sign.

Retry-based false positive suppression

A single failed check does not trigger an alert. Drumbeats retries 3 times with 5-second gaps before opening an incident. This handles transient network blips, brief deploy windows, and load balancer hiccups without waking anyone up.

If all retries fail, Drumbeats opens an incident and sends notifications. When the endpoint recovers, the incident resolves automatically.

Works with your existing notification channels

Uptime monitors use the same notification groups as your cron and event-driven monitors. If you already have Slack and Email configured, your uptime alerts go there too. No extra setup.

This includes the new Browser Push channel — get native push notifications in your browser without installing anything.

Status page support

Uptime monitors can be added to your public status page alongside your cron monitors. Your users see a single view of operational health across both scheduled jobs and endpoint availability.

Billing

Each HTTP check consumes 1 Beat. If retries fire, each retry also counts as 1 Beat. A monitor checking every minute uses roughly 43,200 Beats per month. On the Free plan (200K Beats/month), that leaves room for about 4 monitors at 1-minute intervals — or more at lower frequencies.

The math scales linearly: a 5-minute interval uses about 8,640 Beats per month.

Firewall and WAF whitelisting

Drumbeats sends requests with the user-agent Drumbeats/1.0 (+https://drumbeats.io/docs/monitor-types/uptime). If your endpoint sits behind a WAF or firewall, whitelist this user-agent string to avoid blocked checks being reported as downtime.

You can find the IP addresses used by Drumbeats for uptime checks on the monitor detail page.

Coming soon

We are already working on the next round of uptime capabilities:

• Keyword verification — assert that the response body contains (or does not contain) a specific string
• SSL certificate expiry monitoring — get alerted before your cert expires
• Multi-region checks — run checks from multiple locations to distinguish local network issues from real outages

Get started

If you already have a Drumbeats account, go to your dashboard, click New Monitor, and select Uptime. Enter a URL, pick an interval, assign a notification group, and you are live.

If you are new to Drumbeats, start free — 50 monitors and 200K Beats per month, no credit card required.