Monitoring
Status Page
A status page is a public dashboard that displays the current health of a service and the history of past incidents. Status pages set customer expectations during outages, cut inbound support volume, and act as the single source of truth communications teams can point to.
Part of Status pages — the full answer, the facts and the alternatives in one place.
In depth
Modern status pages support three surfaces: component health (per-service up/down/degraded), incident history (with post-mortem write-ups), and subscription (email, RSS, webhook, or Slack push when status changes).
Good status pages are hosted on a separate origin from the product so that a full outage still leaves the status page reachable. Lemwatch runs status pages on isolated infrastructure and supports vanity URLs like status.yourbrand.com via custom CNAME.
Why it matters
Silence during an outage is worse than the outage. A live status page turns 200 angry support tickets into 200 customers refreshing the same page — and gives your team the breathing room to actually fix the issue.
Also known as
- Status page
- Public status page
- System status
How Lemwatch helps with status page
Lemwatch monitors status page continuously and alerts you the moment something changes.
Branded status pages →Related terms
Incident
An incident is a confirmed period of degraded or unavailable service that requires human attention. Incidents …
SLA
A service level agreement (SLA) is a contractual commitment between a provider and a customer specifying a mea…
Website Monitoring
Website monitoring is the continuous automated checking of a website's availability, performance, security, co…
Alert Fatigue
Alert fatigue is the desensitisation that happens when an on-call team receives too many alerts, especially fa…
Synthetic Monitoring
Synthetic monitoring is the practice of running scripted, scheduled checks against a website from controlled p…
Browse the full Lemwatch monitoring glossary (47 terms).