Status page
A status page is a public page that shows whether a service and its parts are working, along with current incidents, planned maintenance and past uptime.
During an outage a status page answers the question everyone is asking, so support does not have to answer it a hundred times. It works best on separate infrastructure, usually its own subdomain, so it stays up when the product is down.
Useful status pages list components in terms customers recognise (API, dashboard, checkout), post updates with times as an incident progresses, announce maintenance in advance and let people subscribe.
In OpenUptime
OpenUptime status pages show 90-day uptime per component, incidents and maintenance, with email and RSS subscriptions and a custom domain on paid plans. The page can be embedded in your site or README.
Questions
Should a status page be public?
For a product with external customers, usually yes: being open during incidents builds more trust than silence. Internal services can use a private page.
Should the status page update automatically?
Component status can follow monitors automatically, so the page is never green during an outage. Written updates still need a person, because customers want to know what is being done.
Related terms
Monitor it with OpenUptime
Checks from one or several regions, alerts to the tools you use, and a status page for your customers. Free to start, open source under the MIT license.
状态页（Status page）
状态页是一个公开页面，展示服务及其各组成部分是否正常，以及当前事件、计划维护和历史可用率。
故障期间，状态页回答了所有人都在问的问题，客服就不必回答上百遍。它最好部署在独立的基础设施上，通常用单独的子域名，这样产品宕机时它依然可以访问。
好用的状态页会用客户能理解的名称列出组件（API、控制台、结账），在事件处理过程中带时间戳地发布更新，提前公告维护，并允许用户订阅。
在 OpenUptime 中
OpenUptime 的状态页显示每个组件 90 天的可用率、事件和维护，支持邮件和 RSS 订阅，付费套餐可使用自定义域名。状态还可以嵌入到你的网站或 README 中。
常见问题
状态页应该公开吗？
对于有外部客户的产品，通常应该公开：故障期间保持透明，比沉默更能赢得信任。内部服务可以使用私有状态页。
状态页应该自动更新吗？
组件状态可以跟随监控自动更新，这样故障时页面不会还显示正常。但文字更新仍然需要人来写，因为客户想知道正在做什么。