Service status page
A transparent status page with current state, component history, and an incident update.
When this template fits
Use this page to communicate the current health of a small service, its main components, and a recent incident. It is a presentation template; a trustworthy production status page also needs monitoring data and an independent delivery path.
How the layout works
The overall state appears before component rows and incident history. Text labels accompany status color, timestamps provide context, and simple rows remain readable without relying on a complex chart or client-side application.
What to customize
List components users recognize, publish timestamps in a stated time zone, and describe impact before technical cause. Add subscription options and an incident archive only when updates are generated from a reliable operational process.
Review before publishing
Verify that the displayed state comes from monitoring rather than a hard-coded optimistic default. During an incident, update the user impact and next communication time; do not remove inconvenient history after the service recovers.
Keep building with context
Compare a related pattern or read a practical guide before adapting this example in the Playground.