Skip to content

Templates

Status page examples and templates

Four status page templates, each built on RealUptime for a different kind of business. Every reading below is illustrative template data, not a real customer or a live incident: RealUptime is a new product, and these are starting points, not a showcase of who uses it.

API-first products, developer tools, platforms with a public API

SaaS API

API, dashboard, and auth, watched by region

Built for a developer-facing product where an API outage is the whole incident. Leads with the API and auth components, since those are what an integrating customer checks first.

Regional health shown by default, not collapsed into one badge

SaaS API status

Degraded
  • APIDegraded
  • Web dashboardOperational
  • AuthenticationOperational
  • WebhooksOperational

Checked from four regions

  • US EastOperational
  • US WestOperational
  • EuropeDegraded
  • Asia-PacificOperational
Example

Online stores, marketplaces, anything with a checkout flow

E-commerce

Storefront and checkout, separated on purpose

Checkout and storefront browsing fail independently in most real incidents, so this template keeps them as separate components instead of one combined site reading that hides which half is actually broken.

Component grouping keeps payments separate from browsing

E-commerce status

Operational
  • StorefrontOperational
  • CheckoutOperational
  • PaymentsOperational
  • SearchOperational
  • Order trackingOperational

Checked from four regions

  • US EastOperational
  • US WestOperational
  • EuropeOperational
  • Asia-PacificOperational
Example

Agencies, freelancers, and consultancies managing client sites

Agency multi-client

One page, every client site grouped and labeled

For an agency or freelancer hosting several client sites: the properties for each client sit together in their own labeled group on one page, so any client can find their own status without wading through the rest.

Component groups keep each client's readings together

Agency multi-client status

Down
  • Client A: marketing siteOperational
  • Client A: booking appOperational
  • Client B: storefrontDown
  • Client C: landing pageOperational

Checked from four regions

  • US EastOperational
  • US WestOperational
  • EuropeDown
  • Asia-PacificOperational
Example

Open source maintainers and projects with a public package or docs site

Open source project

Registry, docs, and CI, the surfaces contributors hit

Built for a maintained open source project: the package registry and docs site are what a new user hits first, and CI/build status is what a contributor actually cares about day to day.

Free-tier friendly: public, subscribable, no seat cost for contributors

Open source project status

Operational
  • Package registryOperational
  • Documentation siteOperational
  • CI / build pipelineOperational
  • Community forumOperational

Checked from four regions

  • US EastOperational
  • US WestOperational
  • EuropeOperational
  • Asia-PacificOperational
Example

How cloning works

“Clone this template” takes you to a free RealUptime account. Once you're signed up, build your status page with the same component layout and grouping shown above: name your components, pick which regions to check from, and publish. There's no paid plan required to start; the free tier includes a public status page and ten monitors.

Looking for the reasoning behind checking from more than one region by default, rather than collapsing everything to a single badge? See why a status page can show all green during a real outage. Comparing status page tools first? The status page tool checklist covers what to test.