Publish branded public service health.
Status pages publish selected uptime checks and their incident history to visitors. They are intentionally separate from the authenticated dashboard and use slow polling because anonymous viewers cannot mint a private realtime identity.
Choose a title, description, accent color, theme, color mode, and the uptime checks to display. A page can show every team check or only a selected set, and each selected check can have a customer-facing display name and order.
ServerChirp derives the overall banner from the current state of the visible checks. Keep display names customer-facing; internal hostnames and server IDs are rarely meaningful to visitors.
Attach a custom hostname after its DNS record points to the required target. ServerChirp validates the domain before activating it and manages the public TLS path.
The page lists recent incidents opened and resolved by its visible uptime checks. Each incident shows the check, cause, start time, and resolution time when recovered. ServerChirp does not turn these automatic records into a free-form incident-posting system.
Password protection can limit a status page to customers or internal teams. A non-password-protected page exposes an RSS feed of its uptime incidents.
Publish services whose state helps a customer make a decision. Do not expose internal server inventory, private IP addresses, debugging output, or security-sensitive detail.
