> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/next/basics/status-pages.md).

# Status Pages

What a status page shows your customers and stakeholders, the three kinds of notices you publish on it, how visitors subscribe, and the features that make it yours.

A status page is a hosted page where your customers and stakeholders check the current health of your services, follow active incidents and maintenance windows, and subscribe to notifications.

<figure><img src="https://4089725725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQG79S8GZWmqk3Plak6MO%2Fuploads%2Fgit-blob-18ecb199ca5071006a817f2e116ebacf08045d96%2Fbasics-status-pages-public.png?alt=media" alt="A status page showing an All Systems Operational banner, services grouped by EU and US containers, and a 90-day uptime graph"><figcaption></figcaption></figure>

## What's on the page

Every status page shows:

* **Overall status**: a banner at the top that reflects the worst status across all your services: Operational, Degraded, Partial outage, or Unavailable.
* **Services and containers**: your individual components, such as API, database, or CDN, grouped into containers, each showing its current status: Operational, Degraded, Partial outage, Unavailable, or Under maintenance. See [Services and containers](/next/status-pages/services-and-containers.md).
* **Uptime graph**: a rolling history for the whole status page over the last 30, 60, or 90 days.
* **Active notices**: ongoing incidents, in-progress maintenance windows, and current announcements, each with a full timeline of updates.
* **Notice history**: past incidents and maintenance windows in reverse chronological order.

## Notices

Notices are the posts you publish to keep your audience informed. Three types cover every situation:

| Type            | When to use                                           |
| --------------- | ----------------------------------------------------- |
| **Incident**    | An unplanned service disruption                       |
| **Maintenance** | A planned or essential maintenance window             |
| **Info**        | A general announcement with no implied service impact |

Each notice can have multiple updates posted over time, letting you communicate as the situation evolves. See [Incident, Maintenance & Info Notices](/next/status-pages/incident-maintenance-and-info-notices.md).

## Subscriptions and notifications

Visitors can subscribe to your status page and receive notifications when a notice is created or updated. Three channels are available: **email**, **Slack**, and **RSS**. Subscribers can filter notifications to only the services they care about. See [Subscribers and notifications](/next/status-pages/subscribers-and-notifications.md).

{% hint style="info" %}
Subscriber Slack notifications, where your customers connect a channel in their own workspace, are separate from the organization-level Slack integration used by Incident Management. See [Respond from Slack](/next/incident-management/respond-from-slack.md).
{% endhint %}

## Key features

**Custom domains**: serve the page at your own address, such as `status.acme.com`, with automatic DNS verification and SSL. Once active, the custom domain becomes the canonical URL. See [Custom domains](/next/status-pages/custom-domains.md).

**Access control**: keep the page open to anyone, restrict it to signed-in organization members, or limit access to specific IP addresses or CIDR ranges, entered one per line. The two restrictions can be combined. Both live under the status page's **Settings** → **Security** and are available on paid plans.

**Customization**: set your brand colors, logos, and header and footer content to match your product. See [Customize your page](/next/status-pages/customize-your-page.md).

**Automations**: connect incoming webhooks so your monitoring or alerting tools create and resolve notices for you. See [Automate status updates](/next/status-pages/automate-status-updates.md) and [Connect checks to status pages](/next/monitoring/connect-checks-to-status-pages.md).

**Multiple pages**: one organization can run several status pages, for separate internal and external audiences or different product lines.