A public status page your customers can trust

Built from real check data

Each component on the page is one of your monitors, so the status shown is the result of the same checks that page your on-call engineer. There is nothing to update manually and nothing to keep in sync.

• Component status updates as soon as a monitor changes state.
• The 90-day bar is generated from stored check history, not from manual entries.
• Choose which monitors appear and rename them for a customer audience.

Put it on your own domain

Point a CNAME or A record at ServerInspector and serve the page from status.yourdomain.com. Customers see your brand, and the page stays reachable independently of the application it reports on.

What to publish during an incident

Be early, be specific about impact and avoid speculating about cause. A short first update within minutes builds more trust than a perfect explanation an hour later. Keep a regular cadence until resolution, then post a brief summary.

• State what is affected and what still works.
• Give the next update time, and keep it.
• Close with resolution time and, for significant outages, a follow-up write-up.

Fewer support tickets, better SLA conversations

A public history of uptime is also evidence. When a customer asks about reliability during a renewal, a 90-day record with documented incident durations is a stronger answer than a number in a slide.