How to Build a Public Status Page
Choose public components, write useful incident updates and separate operational evidence from communication.
Login2Cloud product team · Published 2026-10-01
Publish a clear service map
Use customer-facing labels such as API or Customer Portal instead of internal hostnames. Group related components, publish only intended monitors and check the page from a signed-out browser.
Communicate an investigation
An initial update should state the affected service, observed symptoms and what is being investigated. Move to Identified when evidence supports the explanation, Monitoring while checking recovery and Resolved when the communication can close.
Keep states separate
Manual communication stages do not rewrite monitor observations. If a vendor reports an incident at the same time, describe that correlation without claiming it caused your outage. Maintenance should have an explicit window and scope.
Prepare the update workflow
Assign an owner and review what can be published during an incident. Subscriber email appears only after its consent and delivery release gate passes; a page visit alone never implies consent. Do not publish credentials or private diagnostics.
Common questions
Where should I start?
Use the related tool to inspect the current signal, then configure the matching monitor and verify its first result.