> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Getting started with the Status Page

*Learn how to create, customize, monitor, and notify users with Crisp Status Page.*

Crisp Status Page lets you publish a public status page, monitor services and nodes, receive downtime alerts, and communicate incidents or planned maintenance to your users.

__Use this guide to configure the feature end to end:__
* [Check requirements](#1-check-requirements) → confirm the plan needed for Status Page
* [Create your Status Page](#1-create-your-status-page) → initialize the page and domain
* [Customize your Status Page](#1-customize-your-status-page) → logos, colors, and header background
* [Configure monitoring](#1-configure-services-and-nodes) → services, nodes, modes, and statuses
* [Receive notifications](#1-receive-downtime-notifications) → email, Slack, push, and Pushover
* [Communicate incidents](#1-publish-service-announcements) → announcements and downtime warnings

---

# ${color}[#0080dd](Check requirements)

||| The Status Page feature is available on the Crisp Essentials and Plus plans.

You can review plan availability from the [Crisp Pricing page](https://crisp.chat/en/pricing/). Once your workspace is on a compatible plan, open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page**.

---

# ${color}[#0080dd](Create your Status Page)

Before your Status Page can be used, it must be initialized from your workspace settings.

__To create your Status Page:__
* Open [Crisp](https://app.crisp.chat)
* Go to **Settings → Status Page**
* Click the initialization notice
* Follow the setup flow to choose the page name and domain

![Initialize a Crisp Status Page](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/cleanshot-2026-02-02-at-123519_1i60mtw.png =1000xauto)

![Configure the Status Page name and domain](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/cleanshot-2026-02-02-at-123655_1l6lfs1.png =1000xauto)

|| Your Status Page may take a few minutes to become available while the SSL certificate is generated. Once it is ready, you can configure monitored services and nodes.

---

# ${color}[#0080dd](Customize your Status Page)

You can customize the Status Page so it fits your brand. Open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page → Customize your Status Page**.

![Status Page customization settings](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/cleanshot-2026-02-02-at-123744_85x3wr.png =1000xauto)

#### ${color}[#445055](Upload logos)

You can customize the **Header logo** and **Footer logo** from the Status Page customization settings. SVG images are recommended because they scale better across screen sizes.

| Use a light logo for the header and a dark logo for the footer so both remain readable against their backgrounds.

![Customized Status Page header logo](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111453_171x6hy.png =1000xauto)

#### ${color}[#445055](Change the main color)

The main Status Page color follows your Crisp Chatbox color. If you want to change it, update your chatbox color settings first.

You can learn more in [How to customize the Crisp chatbox](https://help.crisp.chat/en/article/how-can-i-change-the-chatbox-color-1txcz7t/).

|| Colors configured through the Crisp customization plugin are also used by your Status Page when available.

#### ${color}[#445055](Change the header background)

If your chatbox uses a pattern image, the same pattern is used in the Status Page header. You can also upload a custom header background image from **Customize your Status Page**.

![Customized Status Page header background](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111518_7077ty.png =1000xauto)

---

# ${color}[#0080dd](Set a custom domain)

By default, Crisp provides a hosted Status Page domain such as `acme.crisp.watch`. You can also configure a custom domain such as `status.acme.com`.

Open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page → Setup your Status Page**.

__To configure a custom domain:__
* Enter your desired domain in **Custom domain**
* Click **Use this domain**
* Add the displayed DNS records in your DNS provider
* Give your DNS provider a short moment to propagate the change
* Click **Verify domain setup**
* Check the domain again once the SSL certificate has been generated

![Status Page custom domain setup](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111639_18iw1wg.png =1000xauto)

||| Do not click **Verify domain setup** before adding the required DNS records. If verification fails, check that every record was added exactly as shown in Crisp.

---

# ${color}[#0080dd](Configure services and nodes)

Crisp Status groups monitored nodes into **services**. A service is a group of related nodes that usually serve the same purpose, such as **Websites**, **APIs**, or **Email servers**.

Open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page → Monitored services**.

__To create a service and monitor a node:__
* Click **Add a new Service** and give it a name, such as `Websites`
* Open the service, then click **Add a new Node**
* Give the node a name, such as `Crisp Landing Page`
* Select **HTTP / TCP / ICMP service (poll mode)** for a public HTTP URL
* Open the node and click **Add a replica**
* Enter the URL or endpoint to monitor, such as `https://crisp.chat/en/`
* Save the configuration, then check your public Status Page

|| A new replica appears grey while the first check is pending. Crisp Status checks `poll` mode nodes every 2 minutes, so wait up to 120 seconds before reviewing the first status.

| You can order services and nodes by editing them and setting an order number from 1 to 100. Lower numbers appear first.

![Editing Status Page monitored nodes](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111745_1rc2t7q.png =1000xauto)

---

# ${color}[#0080dd](Understand monitoring modes and statuses)

Crisp Status can monitor different kinds of infrastructure, including websites, APIs, email servers, database servers, and application servers.

#### ${color}[#445055](Monitoring modes)

__Available monitoring modes:__
* **Poll mode** → monitors public HTTP/HTTPS, TCP, and ICMP services directly from Crisp
* **Push mode** → lets application servers report their own health to Crisp Status with a reporter library
* **Local mode** → monitors private or LAN nodes through a local daemon installed on your infrastructure

For `push` mode, read [How to setup the Crisp Status Reporter library](https://help.crisp.chat/en/article/how-to-setup-the-crisp-status-reporter-library-1koqk09/). For `local` mode, read [How to setup the Crisp Status Local service](https://help.crisp.chat/en/article/how-to-setup-the-crisp-status-local-service-1vbyqkt/).

#### ${color}[#445055](Status values)

A **replica** is the smallest monitored unit with a health status. It can be an HTTP endpoint, a TCP socket, an ICMP host, or an application report.

__Crisp Status uses three statuses:__
* **${color}[#0EB033](Healthy)** → the replica is responding fast and is not overloaded
* **${color}[#F18000](Sick)** → the replica is slower than expected or overloaded
* **${color}[#E10000](Dead)** → the replica did not answer recent probes or stopped reporting

|| Status rolls up from the most severe affected item. A node takes the worst status of its replicas, a service takes the worst status of its nodes, and the Status Page takes the worst status of its services.

---

# ${color}[#0080dd](Configure monitoring options)

You can tune the monitoring bot depending on the selected node mode.

#### ${color}[#445055](Options for `poll` mode nodes)

__Poll mode options include:__
* **Number of failed-check retries** → how many failed checks are retried before considering the replica `dead`
* **Seconds after which node is dead** → how long the replica can take before it is considered `dead`
* **Seconds after which node is sick** → how long the replica can take before it is considered `sick`

#### ${color}[#445055](Options for `push` mode nodes)

__Push mode options include:__
* **Seconds after which node is dead** → how long Crisp waits for the next report before considering the replica `dead`
* **Load ratio above which node CPU is sick** → CPU threshold above which the replica is considered `sick`
* **Load ratio above which node RAM is sick** → RAM usage threshold above which the replica is considered `sick`

#### ${color}[#445055](Options for `local` mode nodes)

__Local mode options include:__
* **Number of failed-check retries** → how many failed checks are retried before considering the replica `dead`
* **Seconds after which node is dead** → how long the replica can take before it is considered `dead`
* **Seconds after which node is sick** → how long the replica can take before it is considered `sick`

![Monitoring bot options for poll mode nodes](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111815_5fd5r8.png =1000xauto)

---

# ${color}[#0080dd](Receive downtime notifications)

When a replica goes down and its status changes to `dead`, Crisp can notify your team through several channels. Open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page → Notification channels**.

#### ${color}[#445055](Email notifications)

Email notifications are useful when you want downtime alerts sent to a shared or operational inbox.

![Downtime notification email](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-111847_shwg2y.png =1000xauto)

To configure them, open **Email (to address)**, enable the notifier, and enter the target email address.

![Email notifier settings](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112048_1cd9ehd.png =1000xauto)

#### ${color}[#445055](Slack notifications)

Slack notifications send downtime alerts to a team channel. This lets team members follow or mute the channel based on their role.

![Downtime notification in Slack](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112122_rjtcoe.png =1000xauto)

To configure them, open **Slack (to channel)**, enable the notifier, and enter your Slack Webhook URL. Slack explains how to create one in its [Incoming Webhooks documentation](https://get.slack.help/hc/en-us/articles/115005265063-Incoming-WebHooks-for-Slack).

![Slack notifier settings](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112157_5tunsw.png =1000xauto)

#### ${color}[#445055](Push notifications)

Push notifications send alerts to selected operators through their connected Crisp apps.

![Downtime push notification on iOS](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112234_ox2eol.png =1000xauto)

To configure them, open **Push (to operators)**, enable the notifier, and select the operators who should be notified.

![Push notifier settings](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112302_1cq5yhm.png =1000xauto)

#### ${color}[#445055](Pushover notifications)

Pushover notifications send downtime alerts to your own Pushover application on the devices where it is installed.

|| Pushover is an external service and may be paid depending on your usage. Review [Pushover's website](https://pushover.net/) and [Pushover API documentation](https://pushover.net/api) before configuring it.

![Downtime alert in Pushover](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112412_hrdut8.png =1000xauto)

To configure it, open **Pushover (to application)**, enable the notifier, then add your application token and recipient keys.

![Pushover notifier settings](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112438_m5j6w2.png =1000xauto)

---

# ${color}[#0080dd](Receive status change Web Hooks)

When the general health of your Status Page changes, such as from `healthy` to `dead`, Crisp can send a Web Hook to your servers.

__To configure a health-change Web Hook:__
* Read the [Web Hooks Quickstart](https://docs.crisp.chat/guides/web-hooks/quickstart/)
* Configure a Web Hook for the event namespace `status:health:changed`

Example payload:

```js
{
  website_id: "",
  event: "status:health:changed",

  data: {
    "website_id": "-JzqEmX56venQuQw4YV8",
    "health": "dead",

    "nodes": [
      {
        "label": "Primary load balancers",
        "replica": "tcp://edge-3.pool.net.crisp.chat:80"
      }
    ]
  },

  timestamp: 1506985696616
}
```

__Payload fields to review:__
* **`health`** → general Status Page health, such as `healthy`, `sick`, or `dead`
* **`nodes`** → affected nodes; this list is empty when the Status Page returns to `healthy`

---

# ${color}[#0080dd](Publish service announcements)

For planned maintenance or prolonged downtime, you can publish a service announcement on your Status Page.

![Maintenance announcement on a public Status Page](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112507_opwsst.png =1000xauto)

Open [Crisp](https://app.crisp.chat), then go to **Settings → Status Page → Configure service announcements**. Click **Add announcement**, then write and publish the announcement.

| Announcements can expire automatically at a chosen date, which is useful for planned maintenance windows.

---

# ${color}[#0080dd](Show downtime warnings in Crisp)

When your systems go down, you can warn users before they contact support. By default, when your Status Page reports as `dead` for more than 3 minutes in a row, a warning appears on the Crisp Chatbox and Crisp Knowledge Base when they are used.

![Downtime notification on a Crisp Knowledge Base](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-112532_jq1796.png =1000xauto)

|| If you do not want these warnings, review the relevant settings in your **Chatbox Settings** and **Knowledge Base Settings**.

---

# ${color}[#0080dd](Find Status Page utilities)

Crisp Status has two companion utilities for monitoring modes that need additional setup.

__Useful Status Page resources:__
* **Crisp Status Reporter libraries** → use them for `push` mode nodes; read [How to setup the Crisp Status Reporter library](https://help.crisp.chat/en/article/how-to-setup-the-crisp-status-reporter-library-1koqk09/)
* **Crisp Status Local service** → use it for `local` mode nodes; read [How to setup the Crisp Status Local service](https://help.crisp.chat/en/article/how-to-setup-the-crisp-status-local-service-1vbyqkt/)