# Status pages: components, incidents and subscribers

Source: https://frosvo.com/docs/status-pages
Updated: 2026-10-22

Publish a public status page with components, automatic checks, incidents, scheduled maintenance and email subscribers, so customers know what works before they ask.

A status page tells your customers what's working before they have to ask. Open **Status page** in the desk.

## Set it up

Choose the page's address (`/status/your-page`), name and logo. Then add **components** — the things customers rely on, like your website, API or email.

Each component shows one of: operational, degraded performance, partial outage, major outage or under maintenance, with 90 days of history.

## Automatic checks

Give a component an address to watch (and optionally a word the page must contain). Frosvo checks it regularly and marks the component down when it stops answering — and up again when it recovers.

## Incidents and maintenance

Post an **incident** when something's wrong, then add updates as you go (investigating, identified, monitoring, resolved). Schedule **maintenance** ahead of time the same way.

## Telling customers

- **Subscribers** confirm their email and get every incident and update; each email has an unsubscribe link.
- While an incident is open, your **chat widget** can show a notice linking to the page (a setting on the page).
- Tools can read `/status/your-page/api/v2/status.json` and `summary.json`.

## Good practice

- Keep components to what customers actually rely on, such as the website, the API and email.
- Post an incident as soon as you know, even if you have no cause yet. Update it as things change.
- Schedule maintenance ahead of time so subscribers can plan.

When an incident is open, point customers to it from the [inbox](/docs/inbox) with a saved reply.

## Related guides

Tell visitors about an incident inside the chat with a [saved reply](/docs/saved-replies-and-macros), reach your contacts with [campaigns](/docs/contacts-campaigns), and read the [developer docs](/docs/developers) if you want to show your status elsewhere.

## Common questions

**How many components should I add?** As few as customers care about. Four to eight is usual.

**Can customers subscribe by email?** Yes. They confirm their address and get every incident and update, each with an unsubscribe link.

## Common questions

### Can the page check my service by itself?

Yes. Give a component an address to watch and Frosvo marks it down when it stops answering, and up again when it recovers.

### Can the chat widget show an incident?

Yes. While an incident is open the widget can show a notice linking to the page. It is a setting on the page.

### Is there an API?

Tools can read the status.json and summary.json addresses of your page.