Public Status Pages

A branded status page for your whole product.

Group every service into one page customers can subscribe to — components, incident and maintenance timelines, your logo and colors, RSS. Need something quick? Turn any monitor into a free public page in one click.

Components & timelinesYour logo, colors, and RSSFree per-monitor quick path

How it works

Build a branded status page in three steps — or skip ahead and turn any monitor into a free public page in one click.

1

Create a status page

Name it, pick a public slug, and you have a branded page ready to wire up. Advanced pages are on Pro and above; one-click per-monitor pages are free on every plan.

2

Group monitors into components

Drop the monitors that matter to your customers into components — API, Dashboard, Background jobs. Each component stays lit by the monitor underneath in real time.

3

Brand it, then share

Upload a logo, pick accent colors, and publish. Post incidents and scheduled maintenance as they happen — your customers can subscribe via RSS.

The actual product

The page your customers see, and the toggle that publishes it

Real components, virtual data. One monitor, one URL, one toggle.

status.drumbeats.io/acme/payment-gateway

Public status

Payment Gateway Health

Verifies processor connectivity every 5 minutes

Operational

Last seen 2m ago

100.0%

24h

99.9%

7d

99.8%

30d

Response timeavg 104ms

No recent incidents. All systems operational.

9:415G · 100%

Drumbeats.io

Public health check

Operationalnow

Uptime

100.0%

24h

100.0%

7d

99.9%

30d

Latency

104ms

No recent incidents.

status.drumbeats.ioPowered by Drumbeats
9:415G · 100%

Drumbeats.io

Public health check

Operationalnow

Uptime

100.0%

24h

100.0%

7d

99.9%

30d

Latency

104ms

No recent incidents.

status.drumbeats.ioPowered by Drumbeats

Live status banner, rolling uptime cards, incident state, and response trends adapt from a wide browser to a phone-sized public URL.

Setup

One toggle. One URL. Done.

Every monitor has a Status Page card in its settings. Toggle it on, get a public URL at status.drumbeats.io/s/<your-slug>, share the link. There is no separate product, no per-page pricing, no static-site step.

  • Auto-refreshes every 60 seconds — driven straight from monitor state
  • Vanity slug on Pro (`status.your-company.com` via CNAME)
  • Drumbeats branding removed on Pro and Business
  • Per-page `noindex` toggle for status pages you don’t want crawled

Two ways to ship status

Build a branded page that speaks for your whole product — or grab a free page per monitor in one click.

Recommended

Advanced status pages

Pro & up · for every need

One branded page for your whole product. Group many monitors into components, run an incident and maintenance timeline, and make it yours — logo, colors, and an RSS feed users can subscribe to.

  • Many monitors, grouped into components
  • Incident & scheduled-maintenance timelines
  • Your logo, colors, and favicon
  • RSS feed for subscribers
Build your branded page

Simple status pages

Free · set up in 60 seconds

Need something quick? Turn any single monitor into a public page in one click — real-time state, 24h/7d/30d uptime cards, and a shareable URL.

  • One public page per monitor
  • Real-time, driven by monitor state
  • 24h / 7d / 30d uptime cards
  • Vanity slug + branding removal on Pro

Why most status pages fail

Status pages are easy to ship and hard to keep honest

Most public status pages are theater. They show a green dot when no human has marked them red — which means they show green for the entire window between an outage starting and an engineer remembering to update the page. Customers refreshing during an incident see "all systems operational" while their requests time out, and the trust cost of being caught lying about uptime is much higher than the cost of just admitting the outage in the first place.

The fix is to drive the page directly from monitor state, not from a human update flow. When a monitor transitions to DOWN (after the configured `failure_tolerance` is hit), the page shows DOWN — automatically, in seconds, without anyone editing anything. Humans add commentary and post-mortem context AFTER the fact; the state itself is never lying.

Drumbeats was designed around this principle. Every status page is a view onto the underlying monitor — not a separate database engineers have to remember to update. You get real-time correctness for free, three rolling-window uptime percentages automatically, and a control surface that lives next to the monitor itself.

Components & groups

Bucket monitors into components and sections — API, Dashboard, Background jobs — so customers see your product the way it is actually built. Each component is lit by its underlying monitor in real time.

Incident timeline

Post incidents as they happen with status, impact, and rolling updates. Drumbeats stamps timestamps, shows active/resolved state, and keeps a public history customers can reference.

Scheduled maintenance

Schedule maintenance windows ahead of time. The page transitions to maintenance at the start, back to operational at the end — no manual flipping, no expired banners.

Your branding

Upload a logo and favicon, pick accent colors, and choose a default theme. The page wears your identity, not Drumbeats’. Custom subdomain on Pro keeps the URL on-brand too.

RSS for subscribers

Customers and partners can subscribe to incident updates via RSS — no email signup, no app to install, just a feed they read where they already read everything else.

Real-time, monitor-driven

Components and the overall page reflect live monitor state. When a monitor flips DOWN, the page does too — no manual updates, no green-during-an-outage.

Start with a page per monitor on Free, or roll many services into one branded Advanced page on Pro — either way the public URL is pinned to live monitor state, so customers see the same authoritative truth your team does.

Drumbeats vs. dedicated status-page tools

Statuspage.io, Atlassian Statuspage, hand-rolled static pages — every team picks one. Here is what each approach actually delivers.

Statuspage.io / Atlassian
Drumbeats
Real-time updates from monitor state
Statuspage.io: driven by API or manual incident updates
Auto-updates within seconds when monitors transition
Pricing
Statuspage.io / Atlassian: separate product, paid tiers
Free on every plan, including the Free tier
Custom subdomain (`status.your-company.com`)
DNS + SSL setup + cert renewal you maintain
CNAME-based vanity slug on Pro
Uptime history
Configurable but billed per data retention tier
24h / 7d / 30d cards built in, no extra setup
Setup time
Hours to days for the first page + custom domain
Under 60 seconds — toggle the Status Page on a monitor
noindex per page
Not always exposed
Built-in toggle for internal / staging pages

FAQ

Common questions about status pages

Fewer support tickets. More user trust.

When users can check status themselves, they stop emailing you. When they see a transparent incident history, they trust your product more — not less. A public status page is one of the highest-ROI things you can add to your infrastructure.

60s

Refresh interval — auto-driven from monitors

24h / 7d / 30d

Rolling uptime windows shown on every page

$0

Status pages are free on every plan

Your users deserve to know what’s happening.

Build a branded status page in minutes — or turn any monitor into a free public page in one click.

No credit card required · Branded pages on Pro · Quick path free on every plan

Keep exploring

What to read next

Related monitoring

Free tools

Resources