# Status pages A status page tells your customers which of your services work and which do not. Spectate status pages show components, 90 days of uptime, incidents and scheduled maintenance. Each page has its own address on `spectate.page`, or on [your own domain](/status-pages/custom-domains). ## What a status page shows | Part | What visitors see | |---|---| | Headline | The worst status of all [components](/status-pages/components), for example "All systems operational" or "Partial outage". | | Happening now | Open [incidents](/status-pages/incidents) and [maintenance](/status-pages/maintenance) in progress. | | Components | Each component with its status, grouped if you use groups. | | Uptime bars | One bar per day for the last 90 days, under each component. | | Latency chart | The response time of the last 24 hours, for components linked to a monitor. | | Past incidents | Incidents of the last 7 days, with a link to the full history. | | History | The **History** page: past incidents and the daily uptime of each component. | Visitors can open each incident and each maintenance on its own page, at `/incidents/` and `/maintenances/`. The main page refreshes itself every 60 seconds. ## Display settings You choose which sections the public page shows in **Settings → Display**. All of them are on by default. | Setting | What it controls | |---|---| | **90-day uptime history** | The daily bars under each component. | | **Latency charts** | The latency chart of components linked to a monitor with charts enabled. | | **Incidents** | Active incidents and the incident history. | | **Scheduled maintenance** | Upcoming and in-progress maintenance. | | **Subscriptions** | The **Subscribe** button for [email subscribers](/status-pages/subscribers). | | **Uptime bars** | **Fill by duration** (default) colours the part of a day that a problem lasted. **Whole day** colours the full bar. | | **Incident history layout** | **90-day calendar** (default) or **Timeline** on the **History** page. | With **Fill by duration**, a 20-minute outage colours a small part of the bar, not the full day. Days in the uptime bars and the history are UTC days. Other times show in the time zone of the visitor. ## Default address Every status page has the address `https://.spectate.page`. The slug is one DNS label: lowercase letters, digits and hyphens, at most 63 characters. Some slugs, such as `www`, `api` and `status`, are reserved. The default address continues to work when you add a custom domain. If you change the slug in **Settings → General**, the old address stops working. ## Create a status page Owners, managers and admins can create and change status pages. Members can see them. 1. In the dashboard, go to **Status pages**. 2. Select **Create status page**. 3. Type a **Name**, for example `Acme Cloud`. 4. Optional: change the **Slug**. Spectate makes it from the name. 5. Select the **Visibility**: **Public** or **Private**. 6. Select **Create status page**. The new page has no components. Add them on the **Components** tab, then publish incidents and maintenance from the **Incidents** and **Maintenance** tabs. The **Overview** tab shows the public URL, the subscribers, the page views of the last 7 days and the open incidents. ## Plan limits The number of status pages depends on the plan of the team. | Plan | Status pages | Private pages | |---|---|---| | Starter | 1 | No | | Team | 5 | Yes | | Business | No limit | Yes | During the 14-day trial, a team has the limits of the Team plan. All paid plans include custom domains and password protection. If a team has more pages than its plan allows, Spectate pauses the newest pages. The oldest pages stay online. A paused page is not served until the plan has room for it again. See [plans and billing](/account/plans-and-billing) and the [pricing page](https://spectate.net/pricing). ## Feeds Every status page has an RSS feed and an Atom feed with its incidents and scheduled maintenance: - RSS: `https://.spectate.page/feed/rss` - Atom: `https://.spectate.page/feed/atom` The feeds contain the 20 newest items, newest first. Spectate sorts incidents and maintenance together by the time you posted them. A maintenance item starts with "Scheduled maintenance:" and shows its status, its window and its affected components. See [scheduled maintenance](/status-pages/maintenance#feeds). The feeds follow the **Settings → Display** settings of the page. If you clear **Incidents**, the feeds contain no incidents. If you clear **Scheduled maintenance**, the feeds contain no maintenance. Each item keeps the same ID when you edit it, so feed readers do not show it again as a new item. The footer of the page links to both feeds. The **Subscribe** dialog shows them under **RSS / Atom**. The feed title, the maintenance labels and the dates use the language of the page. For a private page, add the access key to the feed URL: `/feed/rss?key=`. See [access and visibility](/status-pages/access). ## Share image and status favicon When someone shares a link to the page in Slack, X or LinkedIn, the preview shows a share image. The image shows the current status, or the incident or maintenance of the link. Spectate makes a new image URL when the status changes, so these platforms show the new status. The browser tab icon follows the status. With all components operational, the tab shows a check. During an incident, it shows an exclamation mark in the status colour. During maintenance, it shows a clock. If you uploaded your own PNG, JPEG or SVG favicon, the tab shows your favicon with a dot in the status colour. ## Accessibility Status pages meet WCAG 2.1 level AA: - Text and status colours have a contrast of at least 4.5:1. Spectate adjusts the text colours of a [custom theme](/status-pages/appearance) until they meet this ratio. - A **Skip to content** link lets keyboard users go past the header. - Visitors can move through the days of an uptime bar with the arrow keys. - The `lang` attribute of the page is the language that the visitor sees. - Animations stop when the visitor's device asks for reduced motion. Visitors can switch between light and dark mode with a button in the header. ## Related Add components and link them to monitors. Publish incidents and updates for your customers. Serve the page from your own domain. Read the status in the Atlassian Statuspage format.