Build status pages from measured uptime not manual incidents

Short summary

A trustworthy status page separates measured uptime data from human-written incident notes, preventing teams from quietly hiding real outages. The uptime bar should be built from actual monitoring checks with multi-region confirmation rules, not from manually published incidents. Using the same alerting rule for both on-call paging and the public timeline ensures the status page can never disagree with itself.

• •Status page uptime bars must come from measured checks, not manually published incidents
• •Use the same confirmation rule for alerts and the public timeline to prevent contradictions
• •Adding monitors after an outage can silently hide past downtime if incidents are snapshotted once

Generated with AI, which can make mistakes.