Features

HTTP, Ping, Port, SSL, DNS, API, and Cron checks from 30 seconds. Custom intervals per probe.

Flag probe response times that deviate from historical baselines.

Run each check from multiple geographic regions and require quorum before marking down.

Public and private pages. Custom domain with auto-SSL. Jamstack delivery — survives your outage.

Carve a status page into sections (Frontend, API, Database, Workers…) so the public surface reads as a system map instead of a flat list. Drag-free reorder, per-group monitor assignment, ungrouped monitors land at the bottom.

Self-contained HTML widget at /embed.html plus an oEmbed v1 endpoint so Slack, WordPress, Discord, and Notion auto-render a live status block when someone pastes the URL. Brand-name link + overall pill + per-monitor rows; zero external assets so iframe isolation holds.

Composite "service quality" metrics rendered on the public status page footer: avg resolution time, time to first update, updates per incident, post-mortem rate. Forces transparency on how well you handle the outages you do have — not just whether they happened.

Shields.io-style SVG badge ({your-page}/badge.svg) plus a shields.io endpoint-compatible JSON. Embed in your GitHub README, customer-facing dashboard, or any HTML — it pulses brand-green when everything's up, coral on major outage, blue during maintenance.

Upload a logo and inject custom CSS to brand the public status page beyond the default theme.

Allow the tenant to serve their status page under status.<their-domain>.com instead of status.statuspulse.ai/<slug>.

Hide "Powered by StatusPulse" from the public status page and add your own footer line (legal disclaimer, contact email, copyright). Combined with custom domain + branding, your page reads as fully yours.

Track incidents from start to resolution. Email watchers and groups get notified automatically, with a one-click unsubscribe in every message.

Use Claude to draft incident updates, impact summaries, and root-cause suggestions.

When the cross-tenant anomaly model flags a sustained excursion above threshold, StatusPulse pre-stages a Proposed incident in your dashboard — review and promote with one click, or dismiss. Get out ahead of customer complaints. No other status-page tool has the underlying ML to drive this.

Critical incidents auto-page Owner/Admin members via SMS + email if no public update lands inside 15 min (30 min for Major). Per-incident 30-min cooldown so an unresponsive operator gets one nudge, not a flood. Internal / scheduled / proposed incidents excluded.

One-click CSV of any incident — metadata, components, full timeline, SLO impact rows. Compliance reviewers and audit teams pivot in Excel; you avoid screenshot-the-screen workflows.

Operator-grade view of MTTR, time-to-first-update, volume trend (12-bucket bar chart), and the top noisy components by incident-link count. 30/90/365-day windows; per-page filter.

Open and track incidents manually with public lifecycle (Investigating → Identified → Monitoring → Resolved), narrative timeline, and per-component impact.

Attach a long-form retrospective to a resolved incident with sections for summary, timeline, root cause, impact, remediation, and follow-ups. Public detail page at /incidents/<id>/postmortem.

Schedule a maintenance window on a public status page. Pre-window banner, auto-open at start, auto-resolve at end, dedicated subscriber notification.

Mark an incident as internal-only and it stays in your dashboard for triage tracking — never on the public page, never to subscribers. Useful for war-room comms, capacity planning, PR-coordination tickets you don't want to publish.

Each incident shows the probe-derived uptime drop, downtime in window, and share of monthly error budget burned. Statuspage.io can't ship this — they don't have probes. You do, so you see the SLA cost of every incident in real-time.

Route subscriber and alert email replies to your help desk inbox (support@your-company.com) instead of the default donotreply box. Envelope sender stays on our verified ACS box for deliverability; only Reply-To changes.

Forward incident events to PagerDuty, Opsgenie, Zapier, or any custom HTTPS endpoint. Per-page configuration, HMAC-SHA256 signing, custom request headers (Authorization, X-API-Key, …).

Schedule-aware paging. Build a weekly rotation of who's on-call, attach a multi-step escalation policy to each status page, and the auto-pager calls the right person instead of fan-out-to-everyone. Replaces blast-everyone-on-Critical with surgical paging that the rest of the team doesn't have to dismiss.

Post incidents to a Slack channel via an incoming webhook.

Send alert notifications via SMS, in addition to email.

Post incidents to a Microsoft Teams channel via an incoming webhook.

Public status pages and scheduled PDF reports render in English, Portuguese, Spanish, French, Italian, and German. Visitors pick their language from the page footer; reports honour the per-subscription locale.

Download monthly uptime and SLA reports as branded PDFs — shareable with customers, regulators, or internal stakeholders.

Use Claude to rewrite the executive-summary page in plain non-technical language.

Auto-deliver PDF reports by email on a recurring schedule.

Render PDF reports with the tenant's logo and brand colour.

Programmatic, cursor-paginated read of the full tenant audit trail (writes / deletes / soft-deletes / restores; actor identity, IP, UA; before/after JSON diffs). Filter by date, actor, entity, action. Required for SOC 2 / ISO 27001 vendor reviews.

JSON read API for status / incidents / probes with per-tenant rate-limited bearer tokens. Free 60/min, Starter 120, Pro 600, Business 6000 req/min. Build internal dashboards, status aggregators, or chatbot integrations against your own page.

Restrict workspace membership to a specific email domain (e.g. @acme.com). Combined with Entra External ID federation (Google Workspace + Microsoft work accounts), enforces single-sign-on for every member. Stops randoms from claiming the workspace via mismatched invite links.

Invite additional users to the workspace with Owner / Admin / Editor / Viewer roles. Free is restricted to the workspace owner only (1 seat); Starter and above unlock the invite flow up to the plan's max_team_members limit.