Start with what the visitor can know
A useful notice describes the affected task in ordinary language. “The public booking page is unavailable” is more informative than a vague claim that everything is broken, provided that impact has actually been confirmed. Separate the customer-facing consequence from the technical hypothesis. An alert can begin an investigation without establishing the root cause, full extent or time at which every visitor became affected.
Choose a proportionate update
UptimeRobot documents hosted status pages and incident communication features. Whether you use a dedicated page or another existing channel, decide who can publish and how they confirm facts. Do not expose private endpoint names, customer information or internal access details in public updates. A status channel should reduce confusion without becoming a stream of speculative technical commentary that the business cannot substantiate.
Use a fictional first notice
An example might say: “We are investigating a problem reaching our appointment page. Our usual telephone contact remains available during office hours. We will post another update after the maintainer checks the service.” This is a fictional writing pattern, not a notice about a real business. Include only alternatives that actually exist, and do not promise a specific repair time merely because a customer understandably wants one.
Update after verification
When the service appears restored, check the relevant customer task and distinguish that evidence from the monitor changing state. If the cause remains unknown, say so internally and avoid a public explanation invented to sound conclusive. Retain timestamps for the initial observation, updates and verified recovery. A clear limited account is more credible than an exaggerated assurance that the issue can never recur. Keep an accessible copy of the last confirmed update.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- UptimeRobot: status pages — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26