Public status pages

Turn selected monitoring state into a careful public answer.

Publish chosen components, safe incident context, maintenance state, confirmed subscriber updates, and eligible workspace branding without leaking private monitor configuration.

Service statusSubscribe
All systems operational
Website Operational
Public API Operational
Scheduled jobs Operational
SSL certificate Operational

Selected components

Publish only monitors chosen for the page.

Safe incidents

Expose reduced public context, never raw internals.

Confirmed subscribers

Require explicit email confirmation before activation.

Eligible branding

Apply stored logo, accent, and brand visibility safely.

01Public surface

Give service health enough room to be understood.

A large public view brings the overall state, selected components, operational indicators, and planned maintenance into one readable page.

02Privacy boundary

Communicate status without exposing configuration.

Public payloads exclude URLs, request headers and bodies, heartbeat tokens, customer identifiers, raw exceptions, and internal response content.

03Subscriber workflow

Make notification consent explicit.

Email subscribers remain pending until they confirm through the scanner-safe flow. Only verified subscribers receive supported public incident updates.

04Brand fallback

Keep customization entitlement-aware.

Eligible workspaces can store a logo, accent, and PingBeacons-brand visibility preference. Downgrade restores standard branding without deleting saved choices.

Start with PingBeacons

Give customers a clear answer when service health changes.

Publish selected components and safe operational context from the monitoring state you already maintain.