# Status pages

Source: https://getuptimely.com/docs/status-pages

> Branded public or private pages, subscribers, custom domains, and status badges.

A status page shows the live state of the monitors (or monitor groups) you
put on it, plus active incidents, announcements and scheduled maintenance.
Each project on the Free plan includes one status page; Pro raises the limit.

## Building a page [#building-a-page]

Create a page under **Status Pages**, then attach resources (monitors and
monitor groups) and arrange them. Pages support:

* **Branding** — logo, colors, and custom CSS.
* **Public or private** — private pages require viewer authentication.
* **Announcements, incidents and maintenance** — shown with their timelines
  and public notes.
* **Overview history** — per-resource uptime bars rendered in the viewer's
  timezone.

## Subscribers [#subscribers]

Visitors can subscribe to a status page and get notified about incidents and
scheduled maintenance. Deliveries run in background workers with per-attempt
logging.

## Custom domains [#custom-domains]

Serve a status page on your own domain (say `status.example.com`):

1. Add the domain on the page's **Custom Domains** tab.
2. Prove ownership of the parent domain (an apex TXT record) and point a
   CNAME at Uptimely. The **guided setup** opens your DNS provider's flow in
   an embedded window and can finish both records in one pass — on providers
   with one-click connect (like Cloudflare) it's a single approval. Manual
   record instructions are always available as a fallback.
3. Once DNS verifies, the page serves on your domain with TLS, and Uptimely
   keeps monitoring the records for drift.

## Status badge [#status-badge]

Every public status page exposes a live SVG badge at
`app.getuptimely.com/status/<slug>/badge` — embed it in a README or wiki.
Badge variants can show uptime percentage or response time.
