> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/status-pages.md).
# Status pages
## Create a status page
Creating a status page is a matter of few clicks.
1\. Navigate to **Status pages** in the navigation bar and click on the **Create status page** button
2\. Select your page type, ilert URL and the teams that should manage the status page.
3\. Select the services that you would like to include in the status page. You can also create new service and add them to the status page from the drop down list.
4\. Optionally add your own logo and fav icon and click on **Save**.
5\. Click on the **Visit status page** button to preview your status page. Once you are satisfied with your status page, click on the **Activate** button to make your page available and viewable to your users.
## Update the status of your status page
The status of your status page is automatically updated whenever
* the status of a service that is included in the status page is updated (e.g. by setting a service to *Degraded*)
* an [incident is created](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/incidents.md#create-and-communicate-incidents) that affects any of the services from your status page
[-> How to create an incident](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/incidents.md#create-and-communicate-incidents)
{% embed url="" %}
{% endembed %}
### Automation with alert sources
You can automatically update your status page in the following ways:
* Automatically update the status of a service (for example, set the status to *Degraded*)
* Automatically create an incident on your status page using an [incident template](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/incidents.md#create-an-incident-template) and (optionally) notify subscribers
Both cases work by using the **ilert incidents** alert action on an alert source. See [-> Services: automation with alert sources](/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/services.md#automation-with-alert-sources) for more information.
{% embed url="" %}
{% endembed %}
## Status Page Layout Options
### Service groups: how to group related services together
Service groups let you group related services together on a status page. This allows users to quickly see the overall health of a system and identify any issues that may be impacting multiple services.
Below is an example service group from our status page. When the service group is collapsed, it shows a combined status and uptime graph. When the service group is expanded, it shows the status and uptime graph for each service individually. The overall status of multiple services in a service group is calculated by taking the status of the service with the highest impact. Similarly, the uptime percentage and outage graph is calculated by combining the outages of all services.
To create a service group
1. Navigate to the status page for which you want to create a service group
2. Go to the **Services** tab.
3. Click on the **Create service group** button and give it a name.
4. You can add services to the service group during creation or later in the by dragging and dropping services into the group
Use the following settings on a service group and service to further customize how they appear on your status page:
* **Expand group on page**: Activate this option if you want to expand the entire service group by default on your status page
* **Show uptime history:** Activate this option if you want to show the service's historical uptime and its SLA
### Services layout: single vs responsive columns
You can choose between two layout options for displaying services on your status page.
* **Single column** presents items in a vertical list.
* **Responsive columns** arranges items in a grid with up to 3 columns that adapts to your screen size.
| Single column | Responsive columns |
| :-----------------------------------------------------------------: | :-----------------------------------------------------------------: |
| | |
To change the service on a status page
1. Go to **Status pages** and click on the status page you want to change its layout
2. Click on the **Services** tab
3. Select your layout option and click save
## Setting up your custom domain
Every status page (both private and public) comes with support for custom domains, so that you can make your status page accessible from your own subdomains (e.g. status.example.com).
Setting up a custom domain consists of the following steps:
1. Set the custom domain in ilert
2. Configure DNS
3. Wait for the changes to take effect
#### 1. Set the custom domain in ilert
Go to your status page settings, enter a custom domain, and click **Save**.
#### 2. Configure DNS
Configuring DNS happens outside of ilert, at the DNS provider you are using for your domain.
1. Create a new DNS record and select **CNAME** as the record type
2. Enter the name for the CNAME record. The **name** or **DNS entry** is where you enter your subdomain. You might need to enter it in full (e.g. **status.example.com**) or you might just need to enter the part before your apex domain (e.g. **status**). If you're not sure which to use, check with your DNS provider.
3. Enter the ilert URL of your status page as the value for the CNAME record. The **target** or **value** or **destination** is where the subdomain should be pointed. Taking the screenshot from above as an example, you would need to enter `ilert-demo.ilert.io` .
You might also see a field named **TTL**, which stands for Time To Live. It's the number of seconds that the DNS record can be cached for. If you're not sure what to set, look at the TTL for your existing DNS records. You could set the same number. If you're still not sure, we suggest setting 43200 seconds (12 hours) or 86400 seconds (24 hours).
{% hint style="warning" %}
**Are you using Cloudflare?**
Whenever possible, please **turn off Cloudflare proxying** (the orange cloud, also called "Proxy status" in your domain settings) to ensure that your status page is served without issues and can be monitored by ilert.
{% endhint %}
#### 3. Wait for the changes to take effect
You might need to wait 1-48 hours for the DNS changes to take effect. This depends on the TTL setting of your DNS record and the time it takes until the DNS change is propagated throughout the internet.
## Embed the status of your status page on your website
Communicate incidents to your users right where they are using your service: on your website or web app.
To embed the status of your status page in your web app or website, you can use ilert's floating status widget or status badge. The status page widget will only be visible if there is an ongoing incident or scheduled maintenance and will be hidden if all services are operating normally. The status widget will always be visible and show the overall status of your status page.
To configure your status page floating widget:
1. Go to **Status Pages**
2. Click on the Status Page where you would like to configure the widget
3. Click on the **Status embed** tab
4. Select **Floating widget**
5. Configure your widget by choosing your colors and widget position, copy the generated snippet code.
6. Paste the generated code snippet from step 4 into the `` section of your target page.
7. Test the widget by creating a test maintenance window or incident.
{% hint style="info" %}
**Making changes to your widget**
Changes to your status page will not propagate automatically to your pages. You need to update the code snippet in your target for any changes to take effect.
{% endhint %}
The localization of the widget will be automatically detected using the viewer's browser language. If you want to set the **language** to a fixed setting, you can optionally provide the query parameter `&lng=en` or `&lng=de` to the scripts already existing parameters.
## Announcement Bar
Share essential announcements via your status page. Enable an announcement bar in the status page settings. To make your message more engaging, use simple Markdown and emojis. The announcement bar will be shown at the top of your status page.
Announcement bar settings
Example of the annoumcement bar
## FAQ
#### We are a managed service provider and would like to use multiple status pages to communicate incidents to different customers with private pages without exposing data between customers. Is that possible?
Yes. Our Premium plan even gives you unlimited stakeholder licenses. That way, you can invite as many customers as you need without requiring a full license.
To isolate customers from each other, we recommend the following approach:
1. Create a team for every customer and make the team [private](/~/changes/vPSzQFfkdJCVWGT5AL1m/user-administration/teams.md#private-teams)
2. Invite your customer to ilert choosing the **Stakeholder** role
3. Add the customer to the respective customer team.
4. Assign the status page to the respective customer team.
#### I have set my status page to Public, but it's still not accessible from the internet. What am I missing?
You probably forgot to activate your status page. Once you are satisfied with your status page, click on the **Activate** button to make your page available and viewable to your users.
**Can I export a list of status page subscribers?**
Yes. To export a CSV file of your status page subscribers, go to Subscribers tab in Status Page Settings and click "Download subscribers" button in the upper right corner.
**What if a subscriber hasn't confirmed a status page subscription?**
No worries, ilert will automatically send double opt-in confirmation reminders to your subscribers after 24 hours, three days, and one week.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/incident-comms-and-status-pages/status-pages.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.