Our status page displays a large number of individually monitored services, and we wanted per-service status and uptime for each of them. : We spent a consistent number of hours managing, troubleshooting, and fixing the status page, adding up to of engineer time per year. The status page was a good place to find out because the blast radius of getting it wrong was survivable. Separate domain and deploy pipeline: Status page releases are not coupled to product releases, and a bad product deploy cannot take the page down. Status page releases are not coupled to product releases, and a bad product deploy cannot take the page down.