Changelog ·

Heartbeat monitors cost one credit per check-in; webhooks need https

The pricing section now states the heartbeat cost and the panel shows it; new and changed webhook channels must use https.

monitorsaccountalerts

Heartbeats. A heartbeat monitor uses one credit per expected check-in, the same as a scheduled check at that interval: a job that must call in every 5 minutes costs 8,640 credits a month. The pricing section says so from today, and the panel, the API's credits_per_month, import, bulk change and quick add show that cost instead of 0. The 650,000 free credits a month cover it for most accounts. Until today the panel showed heartbeats as free while the ledger charged them; no account on PingWise had a heartbeat monitor or had spent bought credits in that period, so nothing was owed to anyone.

Webhooks. New and changed webhook channels must use https, as the help text always said; an alert carries details about your site and should not travel in the clear. Webhook channels added over plain http before today keep working and are marked «http · needs https when changed» on the Alerts list. ntfy topics may still use http. Webhooks has the rules.

← All updates