A DOWN heartbeat now lights up the dashboard and sidebar like any other outage, you can click any heartbeat to see when its pings actually arrived, and a handful of rough edges in the create flow are gone.
PingZen's alert form is rebuilt — duplicate an alert to a second channel in one click, a shorter default form with collapsible Advanced settings, and triggers that only show the events a monitor can actually report.
Every monitor now has a Download report button — on the monitor page and in the monitors list. Pick a period and PDF or CSV, and you get uptime, MTTR/MTBF, latency percentiles, incidents, and error budget in one file.
Every public status page now has a Download SLA report button. Visitors get a 90-day PDF — overall uptime, per-service windows, daily history, incidents — without an account, and you don't configure anything.
Invite colleagues to a workspace with viewer or editor roles. They see your monitors and configure their own alerts — all within the owner's plan limits, no shared logins, no duplicate checks.
When a site sits behind a Cloudflare JavaScript/Turnstile challenge, PingZen now says so explicitly — and tells you exactly how to stop the false DOWN.
An expired domain or unpaid hosting bill replaces your site with a parking page that still returns HTTP 200 — so classic uptime monitoring stays green while visitors see a dead site. Here is how PingZen catches it.
An expired TLS certificate takes your whole site down and scares away every visitor. Here is how to monitor certificate expiry and get alerted days in advance.
Public monitoring services can't reach 10.x or 192.168.x addresses. Private probes let you watch internal databases, NAS boxes, and intranet apps from the same dashboard.