ilert Documentation
WebsiteAPI ReferenceLoginStart for Free
  • Getting Started
    • Core concepts
    • FAQ
      • Renaming of Incidents to Alerts
    • Import from PagerDuty
    • Import from StatusPage.io
  • Alerting
    • Dashboard
    • Alert sources
    • Notification settings
      • Mute notifications
    • Support hours
    • Maintenance windows
    • Heartbeat monitoring
      • Prometheus Heartbeat Example
      • CLI Heartbeat Examples
    • Deployment events
    • 🏛️Understanding event flows
    • ilert sender IDs, domains and IPs
      • SMS and voice alerts in China
  • On-call management & Escalations
    • Escalation policies
    • On-call schedules
      • My on-call shifts
      • Recurring schedules
      • Static schedules
    • Coverage requests
  • ChatOps
    • Overview
    • Integration for Slack
      • Receive and respond to alerts in Slack
      • Create a dedicated Slack channel for an existing alert
      • Create alerts in Slack
      • Look up who is on-call
    • Microsoft Teams Integration
      • Microsoft Teams Chat Integration
        • Microsoft Teams Integration via Incoming Webhook
        • Microsoft Teams Integration via Workflows
      • Microsoft Teams Meeting Integration
      • Create a channel for an existing alert in Microsoft Teams
      • Create alerts in Microsoft Teams
      • Look up who is on-call in Microsoft Teams
  • Incident comms & status pages
    • Getting started
    • Services
    • Incidents
    • Status pages
      • Public vs private status pages
      • Audience-specific status page
    • Metrics
      • Import metrics from Datadog
      • Import metrics from Prometheus
  • 🪄ilert AI
    • Introduction
    • Using ilert AI for efficient incident communication
    • Using ilert AI for post-mortem creation
    • Using ilert AI for schedule generation
    • Using ilert AI for alert grouping
    • Global Search enhanced by ilert AI
      • Bulk resolving similar alerts
  • Call Routing
    • Getting started with call routing
    • Routing calls using call flows
    • Call routing (legacy)
      • Routing calls based on support hours
      • Voicemail only mode
      • Managing call routing alerts
      • Adding webhooks and outbound chat messages
      • Uploading custom audio responses
  • User Administration
    • User roles and permissions
    • Team-based organisation
    • Single sign on
      • Setting up SSO with GSuite
      • Setting up SSO with Microsoft Azure Active Directory
      • Setting up SSO with Okta
      • Setting up SSO with Auth0
      • Auto provisioning users & teams
    • 🔐Two-factor authentication / MFA
  • INTEGRATIONS
    • Types of integrations
    • Inbound integrations
      • 4me Integration
      • Ansible Automation Platform AWX Integration
      • Amazon CloudWatch Integration
      • Amazon SNS Integration
        • Amazon SNS Inbound Integration
        • Amazon SNS Outbound via AWS Lambda
      • Azure Alerts Integration
        • Azure Activity Logs
        • Azure Metric
        • Azure Logs
        • Azure Service Health
        • Azure Sentinel
        • Budget Alert
      • Apica Integration
      • AppDynamics Integration
      • AppSignal Integration
      • AWS Budgets Integration
      • AWS Cloudtrail Integration
      • AWS DevOps Guru Integration
      • AWS GuardDuty Integration
      • AWS Personal Health Dashboard Integration
      • AWS Security Hub Integration
      • Autotask Inbound Integration
      • Auvik Integration
      • Catchpoint Integration
      • Checkly Integration
      • Checkmk Integration
        • Checkmk Integration (v 1.x)
        • Checkmk Integration (v 2.0+ )
      • Cisco Meraki Integration
      • Cisco ThousandEyes Integration
      • Cisco Webex
      • Cloudflare Integration
      • ClusterControl Integration
      • Connectwise Manage Integration
      • Cortex Integration
      • Cortex XSOAR (formerly Demisto) Integration
      • CrowdStrike Integration
      • Dash0 Integration
      • Datadog Integration
      • Dynatrace Integration
      • Elastic Watcher Integration
      • Email Inbound Integration
        • Email Key Extraction and Resolve Examples
        • Automatically resolve Alerts with Emails
      • FreshService Integration
      • Gatus Integration
      • GitHub Integration
        • GitHub Advanced Security Integration
        • GitHub Inbound Check Run (Actions) Integration
        • GitHub Inbound Issue Integration
        • GitHub advanced settings
      • GitLab Integration
      • Google Cloud Monitoring (formerly Stackdriver) Integration
      • Google Security Command Center
      • Grafana Integration
        • Grafana Integration
        • Grafana Integration (v 9.x)
      • Graylog Integration
      • HaloITSM Integration
      • HaloPSA Integration
      • HashiCorp Consul
      • Healthchecks.io Integration
      • HetrixTools Integration
      • Honeybadger Integration
      • Honeycomb Integration
      • Hyperping Integration
      • CrowdStrike Falcon LogScale Integration
      • IBM Cloud Functions Integration
      • Icinga Integration
      • InfluxDB Integration
      • Instana Integration
      • IT-Conductor Integration
      • IXON Cloud Integration
      • Jira Inbound Integration
      • JumpCloud Integration
      • Kafka Integration
      • Kapacitor Integration
      • Kentix AlarmManager
      • Keep Integration
      • Kibana Integration
      • Kubernetes Integration
      • Lightstep Integration
      • Loki integration
      • Mezmo Integration
      • Microsoft SCOM
      • Mimir Integration
      • MongoDB Atlas Integration
      • MXToolBox Integration
      • MQTT Integration
      • Nagios Integration
      • N-central Integration
      • Netdata Integration
      • New Relic Integration
        • New Relic Integration (deprecated)
        • New Relic Workflow Integration
      • Oh Dear Integration
      • PandoraFMS Integration
      • Particle Integration
      • Pingdom Integration
      • PostHog Integration
      • Postman Monitors Integration
      • Prometheus Integration
      • PRTG Network Monitor Integration
      • Prisma Cloud Integration
      • Push Notifications
      • RapidSpike Integration
      • Raygun Integration
      • Rollbar Integration
      • Salesforce Integration
      • Samsara Integration
      • Search Guard Integration
      • Sematext Integration
      • Sensu Integration
      • Sentry Integration
      • Server Density Integration
      • ServerGuard24 Integration
      • ServiceNow Inbound Integration
      • SignalFx Integration
      • Site24x7 Integration
      • SMS Integration
      • SolarWinds Integration
      • Splunk Integration
      • StatusCake Integration
      • StatusHub Integration
      • StatusPage Integration
      • Sumo Logic Integration
      • Sysdig Integration
      • TOPdesk Inbound Integration
      • Terraform Cloud / Terraform Enterprise
      • Tulip Integration
      • Twilio Alarms Integration
      • Twilio Errors Integration
      • Ubidots Integration
      • Uptime Kuma Integration
      • UptimeRobot Integration
      • VictoriaMetrics Integration
      • Zabbix Integration
        • Zabbix 4.4+ Integration
        • Zabbix 2.2 – 4.3 Integration
      • Zammad Inbound Integration
      • Zapier Inbound Integration
      • Zendesk Inbound Integration
    • Outbound integrations
      • Autotask Outbound Integration
      • DingTalk Integration
      • Discord Integration
      • Email Outbound Integration
      • Jira Outbound Integration
      • GitHub Outbound Issue Integration
      • Mattermost Integration
      • ServiceNow Outbound Integration
      • Telegram Integration
      • TOPdesk Outbound Integration
      • Webhook Integration
      • Zammad Outbound Integration
      • Zapier Outbound Integration
      • Zendesk Outbound Integration
      • Zoom Integration
        • Zoom Chat Integration
        • Zoom Meeting Integration
    • Deployment integrations
      • API deployment pipeline
      • Argo CD deployment pipeline
      • Github deployment pipeline
      • GitLab deployment pipeline
  • Reports
    • Overview
    • Alerts
  • API
    • API Reference
    • API Version History
      • API user preference migration 2023
      • Discontinuation of Uptime Monitoring
    • Rate Limiting
    • Client Libraries
      • ilert Agent - ilagent
      • Go Client
      • Rust Client
      • Javascript / Node.js Client
    • Terraform
      • Importing ilert UI resources into Terraform state
    • 👩‍💻ICL - ilert condition language
    • ➿ITL - ilert template language
    • API endpoints / samples
      • Creating alerts through events
      • Importing public status page subscribers
    • 🔥Developing ilert Apps
      • Get started with ilert Apps
      • Understanding OAuth2
      • Developing a Backend App with OAuth2
      • Developing a web or native App with OAuth2 and PKCE
      • Token lifetimes, error codes, app verification, etc.
  • Contact us
  • ilert Release Notes
  • Mobile App
    • Getting started with ilert mobile app
    • Mobile app notification settings
    • Critical push notifications and DND overrides
      • iOS critical alerts configuration
      • Android Push Notification DND Configuration
    • On-call widget
Powered by GitBook
LogoLogo

Product

  • Alerting & Notification
  • On-call Management & Escalations
  • Call Routing
  • Status Pages

Resources

  • Blog
  • Case Studies
  • Security
  • API Reference

Legal

  • Privacy policy
  • Imprint

Increase Your Uptime

  • Start for Free
  • Get a Demo

(c) 2011 - 2025 ilert GmbH

On this page
  • Create a status page
  • Update the status of your status page
  • Automation with alert sources
  • Status page appearance
  • Status page layout options
  • Setting up your custom domain
  • Status page analytics
  • Embed the status of your status page on your website
  • Announcement Bar
  • FAQ

Was this helpful?

Edit on GitHub
  1. Incident comms & status pages

Status pages

PreviousIncidentsNextPublic vs private status pages

Last updated 14 days ago

Was this helpful?

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)

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)

Status page appearance

You can adjust the appearance of your status page to reflect your company brand. Choose between light and dark mode and upload your logotype and favicon.

Note: If you are using a private (including audience-specific) status page, your logotype, name of the page, and favicon will also be visible on the login page of your status page.

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).

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.

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.

Status page analytics

For pages with custom domains, it is possible to use external analytics tools. External tools can help you gain insights into your status page's most common traffic channels and user behavior.

You can choose from two options—Google Analytics and PostHog. You need a key for both solutions to connect an analytics platform and ilert.

Please beware that using external analytics often requires user agreement with data collection and processing. Consult with your legal department regarding the best approach to collecting information.

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 <head> section of your target page.

  7. Test the widget by creating a test maintenance window or incident.

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.

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.

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. Invite your customer to ilert choosing the Stakeholder role

  2. Add the customer to the respective customer team.

  3. 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.

an that affects any of the services from your status page

Automatically create an incident on your status page using an and (optionally) notify subscribers

Both cases work by using the ilert incidents alert action on an alert source. See for more information.

Create a team for every customer and make the team

https://www.youtube.com/@ilertVideos
https://www.youtube.com/@ilertVideos
incident is created
-> How to create an incident
incident template
-> Services: automation with alert sources
private
Announcement bar settings
Example of the annoumcement bar