Updated: 10 November 2026 · Applies to: Uptime Kuma 2.5.9 (official Docker image) on Ubuntu 24.04 and 26.04 LTS
To create a public status page in Uptime Kuma, open Status Pages, click New Status Page, enter a Name and a Slug, and click Next. In the editor, add a description and footer, click Add Group, pick your monitors under Add a monitor, and click Save. The page is then live at https://your-uptime-kuma/status/your-slug.
This article used to cover Cachet on Ubuntu 18.04. Ubuntu 18.04 is out of standard support, so this guide now uses Uptime Kuma on current Ubuntu: it checks your services and publishes the status page from the same tool, so the page updates itself.
Before you start
You need Uptime Kuma running with at least one monitor. On a fresh Ubuntu 24.04 or 26.04 server, the shortest route is Docker from the Ubuntu repositories (version 29.1.3 on both at the time of writing):
apt update && apt install -y docker.io
Start Uptime Kuma 2. This is the official command from the Uptime Kuma README, with the port bound to 127.0.0.1 so the dashboard is not open to the internet until you put HTTPS in front of it:
docker run -d --restart=always -p 127.0.0.1:3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2
From your own computer, open an SSH tunnel and browse to http://127.0.0.1:3001:
ssh -L 3001:127.0.0.1:3001 root@your-server-ip
On first start, Uptime Kuma 2 asks Which database would you like to use? Choose SQLite for a single server, click Next, then create your admin account. Add your monitors with Add New Monitor before you build the page.
Step 1: Create the status page
- Click Status Pages in the top menu, then New Status Page.
- Enter a Name, for example
Example Services Status. This becomes the page title. - Enter a Slug, for example
example-status. The page address will be/status/example-status. The form accepts onlya-z,0-9and-, with no double dashes. - Click Next. The page opens in edit mode.
The special slug default makes the page show at /status when no slug is given.
Step 2: Add a description and footer
The sidebar on the left holds the page settings. The ones most people change:
- Title: the heading visitors see.
- Description: a line or two under the overall status, such as "Live status of our website, email and API". Markdown is supported.
- Footer Text: a contact line, such as where to email support. Markdown is supported.
- Refresh Interval: how often the page reloads itself, 300 seconds by default.
- Theme: Auto, Light or Dark.
- Show Powered By (on by default), Show Tags, Show Certificate Expiry and Show Only Last Heartbeat: switches for what visitors see.
- Custom CSS: optional styling to match your brand.
To add a logo, click the round icon next to the page title in edit mode and upload an image.
Step 3: Add monitors to the page
- Click Add Group. The first group is named Services. The name is editable in edit mode: click it and type, for example
Website. Each extra group you add appears at the top as Untitled Group. - Click the Add a monitor box and choose a monitor from the list. It is added to the top group.
- Repeat for each monitor. Drag a monitor by its handle to move it to another group, and click the red cross to remove it from the page.
Only add monitors your customers care about. Internal checks (database ports, backup jobs) usually belong on the dashboard, not on a public page.
Step 4: Save and publish
Click Save. The page is public straight away at /status/your-slug; visitors do not need to log in. In our test the published page showed the title, All Systems Operational, the description, the Services group with each monitor's uptime percentage and recent checks, the footer and "Powered by Uptime Kuma".
You can confirm what the public sees from the server with the status page API:
curl -s http://127.0.0.1:3001/api/status-page/example-status
Output (shortened):
{"config":{"slug":"example-status","title":"Example Services Status","description":"Live status of our website and DNS checks.","autoRefreshInterval":300,"theme":"auto","published":true,"footerText":"Questions? Email support@example.com","showPoweredBy":true, ...},"incidents":[],"publicGroupList":[{"id":1,"name":"Services","weight":1,"monitorList":[{"id":1,"name":"Example website", ...
According to the Uptime Kuma wiki, a status page caches results for 5 minutes, so a change can take a few minutes to show for visitors. We saw the same delay with a new incident in our test.
Optional settings
- Make it the home page: in Settings > General > Entry Page, choose your status page instead of Dashboard.
- Post an incident: in edit mode, click Create Incident, fill in Title and Content, choose a style such as info, warning or danger and click Post. Use Resolve when it is over.
- Search engines: Settings > General > Search Engine Visibility controls whether search engines may index the instance.
To serve the page on your own domain such as status.example.com with HTTPS, and to schedule maintenance so planned work does not show as downtime, see Uptime Kuma Status Page on Your Own Domain, with Maintenance Windows. For other monitoring tools, see Server Monitoring Software for Linux: Tools Compared.
Hosting your status page
Run Uptime Kuma somewhere other than the servers it watches, so the status page stays up when they go down. An Uptime Kuma VPS gives you root access with Uptime Kuma installed by our engineers; managed Uptime Kuma hosting is your own private instance that we host and update, with the status page on your own domain.
Official documentation: Uptime Kuma wiki: Status Page.