# Status pages

URL: /systems/status-pages · Id: `system:status-pages`

> Status pages publishes the health of each Product and opens an Incident when a check fails, updating subscribers until it resolves.

Status pages publishes the health of each [Product](/business/nouns/product) and opens an [Incident](/business/nouns/incident) when a check fails, updating subscribers until it resolves. Updates come from [Monitoring](/code/systems/monitoring) as they happen, so no one writes them by hand.

## Summary
| Part | This System |
| --- | --- |
| Group | Support |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Wakes: offered once its Event fires |

You can ask:

- “Put up a status page”
- “Tell customers the API is down”
- “Mark the incident resolved”

## What you get
| Part | This System |
| --- | --- |
| Starts | On for every Startup at creation, with nothing to install. |
| Wakes | On [`Incident.opened`](/business/events/Incident.opened). |
| Built from | [Event streams](/code/platform/event-streams), [Workflows](/code/platform/workflows), [Email delivery](/systems/communications/email), [Observability](/code/platform/observability) |

## Nouns it owns
| Noun | Definition |
| --- | --- |
| [Incident](/business/nouns/incident) | An Incident is an Issue where an Interface or Site fails Customers in production, tracked from detection to postmortem. |

## Verbs
| Verb | Object | Approval | Event |
| --- | --- | --- | --- |
| [Incident.create](/business/nouns/incident/create) | [Incident](/business/nouns/incident) | None | `Incident.created` |
| [Incident.update](/business/nouns/incident/update) | [Incident](/business/nouns/incident) | None | `Incident.updated` |

## Events
| Direction | Event | How |
| --- | --- | --- |
| Emits | `Incident.created` | By [Incident.create](/business/nouns/incident/create) |
| Emits | `Incident.updated` | By [Incident.update](/business/nouns/incident/update) |

## States
None.

## Who operates it
| Part | This System |
| --- | --- |
| Accountable | [Operations Lead](/agents/operations/operations-lead) |
| Team | [Operations Team](/agents/operations) |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | `supervised` |
| Also calls its Verbs | [Privacy Officer](/agents/legal/privacy-officer) |

## Approvals and limits
None.

## Processes that use it
| Process | How it uses it |
| --- | --- |
| [Incident response](/workflows/processes/incident-response) | A Workflow writes [Incident](/business/nouns/incident) |
| [Vulnerability disclosure](/workflows/processes/vulnerability-disclosure) | A Workflow writes [Incident](/business/nouns/incident) |
| [Notify regulator](/workflows/processes/notify-regulator) | A step calls [Incident.update](/business/nouns/incident/update) |

## Rail underneath
None.

## Views and dashboards
| View | Shows | Metrics |
| --- | --- | --- |
| The [Operations Lead](/agents/operations/operations-lead)’s view | The Metrics its accountable Role answers for. | [Liquidity](/agents/operations#liquidity) |

## Access
What each Access level may call here.

| Access level | May call |
| --- | --- |
| `owner` | Every Verb (5) |
| `admin` | Every Verb (5) |
| `member` | Every Verb (5) |
| `viewer` | Read only (2 of 5) |

## Import and export
None.

## Fees and pricing
None.

## Availability and limits
| Part | This System |
| --- | --- |
| Status | Beta: it works, and its Verbs may still change |

## Compliance notes
Controls it carries:

- [Log completeness](/systems/trust-and-governance/controls/log-completeness)
- [Append-only records](/systems/trust-and-governance/controls/append-only-records)
- [Anomaly monitoring](/systems/trust-and-governance/controls/anomaly-monitoring)
- [Incident handling](/systems/trust-and-governance/controls/incident-handling)
- [Capacity headroom](/systems/trust-and-governance/controls/capacity-headroom)
- [Action completion](/systems/trust-and-governance/controls/action-completion)

## Related Systems
- [Monitoring](/code/systems/monitoring)
- [Support](/systems/support)
- [Notices](/systems/notices)

## Example
A [Headless SaaS](/products/templates/headless-saas) for verification codes sees delivery through one carrier slow to 40 seconds. Status pages opens an Incident on its `status.` subdomain and posts an update every 15 minutes. It emails the 300 subscribed developers when delivery recovers.