Monitors pointed at hosts with a Минцифры (НУЦ) certificate no longer fail on trust. PingZen now recognises the Russian Trusted Root CA for its checks — scoped to the check itself, and gated to Russian domains by default.
Read article →Every check location now shows its IP address. Click it and it is on your clipboard, ready for your firewall or WAF allowlist. The addresses stay current — the server observes them as each checker connects.
Read article →The "Ping arrivals" journal in the heartbeat monitor card was failing with a 500 error — it works now. No data was lost — the full ping history was recorded all along and is available retroactively, including the message field from ping bodies.
Read article →You asked — we shipped: heartbeat check-in intervals up to 30 days right from the dashboard, grace periods up to 24 hours, and honest uptime stats for long-interval monitors.
Read article →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.
Read article →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.
Read article →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.
Read article →