USE CASE · Software as a service
SaaS
Multi-tenant uptime, multi-region failover, and the page your customers open when they call their account manager.
What good looks like
Each customer-facing component (API, webhooks, dashboard, exports) is its own row on the page, so a customer can tell at a glance whether the issue they are hitting is their plan, their region, or you. The post-mortem lands within 48 hours and is linked from the incident itself.
What goes wrong without one
Customers assume your service is down because the page they care about is slow, and your support team cannot prove otherwise. A competitor's status page is one tab away.
What this workload actually needs
HTTP/HTTPS on the API, on the dashboard, and on each webhook delivery endpoint you publish. DNS records for the canonical hostname, so you catch the registrar / DNS-provider incidents that don't touch your origin. A regional split: same checks, run from at least two regions, so a single region's outage doesn't look like a product outage.
Rollout checklist
- 01Inventory every customer-facing surface. If a customer can name it, it gets a row on the page.
- 02Pick a 1-minute check interval for the API and dashboard. SaaS pricing is per-minute; you cannot tell the customer the issue is on your side in five minutes when they have already switched tabs.
- 03Set the 24h uptime threshold at 99.9% for Pro-tier components and 99.5% for free. Pick numbers the team would actually apologise for missing, not aspirational ones.
- 04Post the first three monthly reviews to a public changelog on the page. The first month of data is the single most convincing thing a prospect sees before signing up.
Set up a saas status page in two minutes.
Free plan. No card. Cancel any time.