Changelog

TL;DR

Publish branded status pages that combine the latest health, 30-day uptime and response-time history, and selected sites without exposing private dashboard data.
Keep customers informed with public incident timelines, Markdown updates, impact levels, and automatic separation of active and recently resolved incidents.

Create multiple status pages per team, keep them private as drafts, and publish or unpublish them when ready.
Choose which monitored sites appear on each page.
Add a page name, description, and custom PNG, JPEG, or WebP logo.
Share a page at its Sitepulse URL or connect a custom domain by adding the provided CNAME record.
Select which latest checks visitors can see: status and response time, SSL validity and days remaining, DNS health, broken-link count, and performance score.
Optionally include 30 days of daily uptime and average response-time history for each site.
Overall and per-site indicators distinguish operational, degraded, and outage conditions. Missing or stale checks show as no data rather than current health.
Public pages refresh automatically every 60 seconds.

Create customer-facing incidents with a title, start time, initial update, state, and impact.
Move incidents through Investigating, Identified, Monitoring, and Resolved states with Minor, Major, or Critical impact.
Append timestamped updates in Markdown; external links open safely in a new tab and the newest update appears first.
Active incidents appear above site health and affect the page’s overall state. Resolved incidents remain visible in recent history for 14 days.
Filter incident history by the date on which an incident was active.

No-data periods are clearer in uptime timelines.
Fixed DNS details for IPv6 addresses, MX priorities, and CNAME targets.
Reordered the site health overview so status, SSL, DNS, links, and performance follow the same sequence used elsewhere.

Queued issue alerts now preserve the details from the moment the event happened, so later changes cannot alter a delayed email or webhook.
Outdated alerts are cancelled when an issue changes state or its notification route is disabled or reconfigured.
Changing an account email now requires recent identity confirmation as well as verification of the new address.

Sitepulse is now generally available: one dashboard for uptime, SSL, DNS, broken links, and performance across every site you look after.
Issue lifecycle alerts route to Slack, Discord, Microsoft Teams, email, or a webhook when configured thresholds are met.
Starter, Growth, and Agency plans scale by sites, seats, on-demand rechecks, and check history.

Five check types are included for every site: uptime, SSL and certificates, DNS records, broken links, and performance.
With the default uptime rule, a failed scheduled check is retried after two minutes before an incident opens. Teams can configure a different consecutive-failure threshold.
SSL monitoring tracks expiry, hostname mismatches, and untrusted certificate chains.
DNS checks query Cloudflare and Google for A, AAAA, CNAME, MX, NS, and TXT records; expected values can be configured to detect mismatches as well as resolution failures.
Bounded broken-link crawls surface failed URLs with the source page; JavaScript rendering can be enabled per site.
Performance checks record Lighthouse scores, response time, and Core Web Vitals over time.

Send alerts to Slack, Discord, Microsoft Teams, email, or a custom webhook.
Configure routing per rule and mix channels freely so the right failure reaches the right destination.
Each alert includes the site, check type, and severity so you can act without opening the dashboard first.

Multi-seat workspaces with team owners, invitations, and role-based access.
A portfolio overview with one clear status per site for agencies managing client work.
Plans include on-demand rechecks, check history up to 365 days, and minimum cadences from 10 minutes down to 1 minute on Agency.