> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Status pages

> Publish a public page showing which services are up, 90 days of uptime, and incident updates, on your own subdomain or domain.

A status page is the public face of your monitoring. It shows visitors which services are up, a 90-day uptime history, and any incident updates you post. Each page is driven by the monitors you already have, so it stays current on its own.

## Create a page

<Steps>
  <Step title="Open status pages">
    Go to **Status pages** and click **Create status page**. Give it a name (shown as the page heading) and a slug, which becomes its address.
  </Step>

  <Step title="Add the monitors to show">
    Pick the monitors that should appear. Their live state drives the page.
  </Step>

  <Step title="Group them into components">
    Optionally group monitors into named components like `API`, `Dashboard`, or `Payments`. A component shows the worst state of the monitors inside it, so one failing check turns its component red. A page with no components shows everything under one group.
  </Step>

  <Step title="Brand it">
    Add your logo, set the accent color, and toggle the "Powered by Tallwatch" footer. Save, and the page is live.
  </Step>
</Steps>

## Public or private

A page is public by default: anyone with the link sees it. Set its visibility to **private** in the page settings to require a password instead. A private page needs a password, and visitors enter it once to unlock the page; their unlock lasts for the session, so they don't re-enter it on every visit. Use a private page for internal status you don't want indexed or shared openly.

## What visitors see

* **Current status** per component, rolled up from the underlying monitors.
* **A 90-day uptime bar** for each, with the daily uptime percentage and which days had incidents.
* **Incident updates** you publish, plus a **previous-incidents history** grouped by month so visitors can browse past events. See [Posting updates](/status-pages/updates).
* **An RSS feed** of published incidents, for readers who'd rather follow the page than load it. See [Posting updates](/status-pages/updates#rss-feed).

## Next

<Columns cols={2}>
  <Card title="Domains" icon="https://mintcdn.com/tallwatch/F-dDcxhw3J2Q0xWz/icons/globe.svg?fit=max&auto=format&n=F-dDcxhw3J2Q0xWz&q=85&s=0d9e1420faf63fb95a88a6ac62e2f137" href="/status-pages/domains" width="24" height="24" data-path="icons/globe.svg">
    Put the page on `your-slug.tallwatch.com` or your own domain.
  </Card>

  <Card title="Posting updates" icon="https://mintcdn.com/tallwatch/F-dDcxhw3J2Q0xWz/icons/megaphone.svg?fit=max&auto=format&n=F-dDcxhw3J2Q0xWz&q=85&s=e73bc276bf8c4ee17f04b2326a176ad7" href="/status-pages/updates" width="24" height="24" data-path="icons/megaphone.svg">
    Post incident updates and manage email subscribers.
  </Card>
</Columns>