--- title: "Show each part's state on the status page ยท Agent Wranglers" url: https://agentwranglers.se/playbook/operations/incidents/status-page id: OPS-73 level: Recommended updated: 2026-10-22 tokens: 772 licence: "CC BY 4.0" licence_url: https://creativecommons.org/licenses/by/4.0/ --- # Show each part's state on the status page from outside checks For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Incidents](https://agentwranglers.se/playbook/operations/incidents.md). By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-22. - ID: OPS-73 - Level: Recommended - Chapter: [Incidents](https://agentwranglers.se/playbook/operations/incidents.md) - Rule: List every part users depend on, such as the website, sign-in, the API and payments, on the status page. Let outside checks mark a part down within 5 minutes, with no person needed. - Check: The status page lists every part named in the service levels. Stop one part on staging. Its entry changes from up to down within 5 minutes with no person acting, and back within 5 minutes of the restart. The page shows 90 days of history and offers a subscription. - How: A status page that waits for someone to update it stays green during the first, worst minutes of an outage. Point the outside monitor from [Watch the service from outside](https://agentwranglers.se/playbook/engineering/running-in-production/monitoring-uptime.md) at one check per part, and let it set that part's state. People then add the words, as [Keep users informed](https://agentwranglers.se/playbook/operations/incidents/status-updates.md) says. Host the page with another provider, under a name served by another DNS provider. Then it survives your own host or DNS failing. Show 90 days of history and planned maintenance from [Say when you'll be back](https://agentwranglers.se/playbook/website/when-things-break/maintenance-pages.md). Offer email or feed updates. Link the page from the site footer, the help pages and error pages. ## Related rules - ENG-24 [Watch the service from outside](https://agentwranglers.se/playbook/engineering/running-in-production/monitoring-uptime.md) in Engineering - OPS-28 [Keep users informed](https://agentwranglers.se/playbook/operations/incidents/status-updates.md) in Operations and observability - WEB-221 [Say when you'll be back](https://agentwranglers.se/playbook/website/when-things-break/maintenance-pages.md) in Website - SUP-3 [Confirm each new ticket with its ID and the answer time](https://agentwranglers.se/playbook/customer-support/inbox-and-tickets/ticket-acknowledgement.md) in Customer support **For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `Agent Wranglers operations and observability playbook`. In code you write, add a comment next to it with the same link. - Previous: [Keep users informed](https://agentwranglers.se/playbook/operations/incidents/status-updates.md) - Next: [Fix the service first](https://agentwranglers.se/playbook/operations/incidents/mitigate-first.md) - [Incidents](https://agentwranglers.se/playbook/operations/incidents.md)