Communicate

Status Pages

Create beautiful, real-time status pages for your services. Support for custom domains, white-label branding, and a live status badge.

Overview

Status pages are the public face of your monitoring setup. They let your users, customers, and stakeholders see the current health of your services at a glance. Uptimy status pages are hosted at {slug}.upti.my and update automatically as your healthcheck and heartbeat results come in.

Every status page includes a component list with live status indicators, uptime percentage bars, active incidents, a full incident history, and an upcoming maintenance schedule. On plans with subscriber access, your users can subscribe to receive notifications when something changes.

Creating a Status Page

To create a status page, open Status pages in your dashboard and click New status page. It asks only for a name, shown at the top of the page. The page gets an upti.my address you can change under Page slug, and it starts private: turn on Public access when it's ready for visitors. Then add sections and put services and heartbeats in them to represent the individual parts of your infrastructure.

Service Components

Each status page is made up of sections, and each section lists components. A component represents a distinct part of your system, such as "API," "Web Application," "Nightly backup" or "Payment Processing." It is either a service (with or without a healthcheck) or a heartbeat, and displays its own real-time status indicator under the name you give it.

StatusDescription
HealthyThe component is functioning normally with no detected issues.
DegradedThe component is working but with reduced performance or intermittent errors.
DownThe component is completely unavailable or non-functional.
UnknownThe component status cannot be determined. This is the default fallback when no monitoring data is available yet.

Components keep their own status during maintenance. While a maintenance window is in progress, the banner at the top of the page says Maintenance in progress.

Services and Heartbeats

A service with a healthcheck takes its status and its daily uptime bars from the healthcheck, so the page always reflects the real state of your services without manual updates.

A heartbeat shows whether your scheduled jobs ran. Each day's bar is the share of runs that arrived on time, for example "23 of 24 runs on time". A run that's late but still inside its grace period counts as healthy, and a paused heartbeat shows as paused. Visitors only see the heartbeat's name, status and bars, never its schedule or ping URL.

Status Page Content

Every status page displays the following sections to give visitors a complete picture of your service health.

  • Component list with real-time status: Each service component shows its current status with a colored indicator.
  • Uptime percentage bars: Visual bars showing uptime over the period.
  • Active incidents: Ongoing incidents published to the page, listed below the components with their public updates.
  • Incident history: A chronological log of past incidents with their full timeline of updates.
  • Maintenance schedule: Upcoming and in-progress maintenance windows are listed so users know what to expect.

Custom Domain Support

On Growth, Scale, and Enterprise plans, you can serve your status page from a custom domain such asstatus.yourcompany.com. Uptimy provisions and renews a free SSL certificate automatically, so your custom domain is always served over HTTPS.

To set up a custom domain:

  1. Open the status page's Custom domain tab, enter a subdomain like status.yourcompany.com (without https://) and click Add domain.
  2. Add the Ownership record it shows at your DNS provider: a TXT record on _uptimy.<host> (for example _uptimy.status under yourcompany.com) with the value uptimy-verification=<token>. Then click Verify domain.
  3. Once the domain is verified, add the CNAME shown under Routing record, from your subdomain to domains.upti.my. Visitors reach your page there as soon as it resolves. If it doesn't resolve right away, leave it in place and check again later.
DNS records
_uptimy.status.yourcompany.com.  TXT    "uptimy-verification=<token>"
status.yourcompany.com.          CNAME  domains.upti.my.

Branding and White Label

Make the status page look like it belongs to your company. The Branding settings work on every page, on every plan:

  • Page name: shown at the top of the page and in the browser tab.
  • Website URL: where your logo links to.
  • Logo: one for light backgrounds and one for dark, so it reads in both themes.
  • Favicon: the browser tab icon, a square image of at least 32×32. Without one, the Uptimy icon is used.
  • Accent color: used for buttons, and for section headings when it reads on both the light and the dark background. A color too dark or too light for one of them colors only the buttons, so the page stays readable in both modes.
  • Font: the default (Plus Jakarta Sans), Inter, Roboto, Open Sans, Montserrat, Poppins, IBM Plex Sans, Source Serif 4, JetBrains Mono, or System (each visitor's own font). Your status page hosts the font itself, so visitors never load fonts from Google or anywhere else.

Through the API, the accent color and font are the page's theme: primaryColor (a hex color such as #268256) and fontFamily (one of the font names above). Both are optional, and the API refuses any other key.

On Starter and above, White label hides the sticky Uptimy bar across the top of the page. The "Powered by Uptimy" line in the footer stays on every page.

The page's other settings choose what it shows: the monitors (grouped into sections), incidents, maintenance, response time charts, and uptime per region, each of which you can turn off.

Status Badge

Every public status page has a live badge you can embed in a README, wiki, runbook, or your own website. It is a plain SVG image in the shields.io style, refreshed every minute from your monitors, and it links back to your status page:

https://www.upti.my/badge/<status-page-id>.svg

The id is your status page's identifier, not its slug, so the badge keeps working if you rename the page or move it to a custom domain. Open the Badge tab of your status page in the dashboard for a preview and ready-to-paste Markdown and HTML. The badge works anywhere an image does, needs no script, and is served from the edge, so embedding it on a busy site costs nothing. Private and password-protected pages have no badge, since it would reveal a state the page itself does not show.

Subscriber Notifications

On Growth and above, visitors can subscribe to your status page and hear about what it shows without checking back. Subscribers are told when an incident or maintenance is published on the page, when you post a public update, and when its status changes (including when a monitor recovers and resolves it). No workflow is needed. Private updates never go out. Turn on Subscriptions in the page's settings to show visitors the subscribe options.

  • Email: visitors enter their address and confirm it from the email they get (double opt-in).
  • Slack, Discord and Microsoft Teams: visitors paste an incoming webhook URL for their channel. Uptimy posts a confirmation message there right away, and every update after that.
  • Webhook: any https URL receives a signed JSON POST for every update (format below).

Every message has an unsubscribe link. A subscription whose URL stops working (a deleted Slack webhook, a removed Discord channel, or an endpoint failing for about nine hours) is removed. Every channel counts towards the subscriber limit, which applies to each page separately. In the app, a page's subscriber list shows each channel and where it posts, but never the URL itself: it lets anyone post to that channel.

Webhook format

Each update is a POST with a JSON body. type is one of incident.published, incident.updated, incident.status, maintenance.published, maintenance.updated or maintenance.status. A new subscription first receives subscription.created. Answer with any 2xx. Failed deliveries are retried for about nine hours, and a 410 Gone unsubscribes.

incident.status
{
  "id": "6b1d2c3e-…",
  "type": "incident.status",
  "occurredAt": "2026-11-12T10:42:00.000Z",
  "statusPage": { "name": "Acme", "url": "https://status.acme.com" },
  "incident": { "title": "API errors", "status": "Resolved", "message": null },
  "unsubscribeUrl": "https://status.acme.com/unsubscribe/…"
}

Maintenance updates carry maintenance instead of incident, with startAt and finishAt. Every request is signed with the secret shown once when the webhook subscribes: Uptimy-Signature: t=<unix seconds>,v1=<signature>, where the signature is the hex HMAC-SHA256 of <t>.<raw body>. Compare it in constant time and refuse old timestamps:

verify.js
import { createHmac, timingSafeEqual } from "node:crypto";

function verify(rawBody, header, secret) {
  const { t, v1 } = Object.fromEntries(header.split(",").map((p) => p.split("=")));
  if (Math.abs(Date.now() / 1000 - Number(t)) > 300) return false;
  const expected = createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex");
  return v1.length === expected.length && timingSafeEqual(Buffer.from(v1), Buffer.from(expected));
}

Atom feed

Every public status page, on every plan, has an Atom feed at /feed.atom (for example https://status.acme.com/feed.atom) listing its incidents and maintenance with their public updates. Feed readers, Slack's RSS app and chat bots that follow feeds can use it without subscribing. Private and password-protected pages have no feed.

Internationalization (i18n)

Status pages ship in English. To show a page in another language, you write the translations yourself in the page's Translations tab.

  • Default language is the language every visitor sees, and the one used for date and time formatting.
  • Add language opens an editor for it with every string on the page, grouped by section, next to the English text. A field you leave blank shows the English text.

The editor offers Spanish, French, German, Italian, Portuguese, Dutch, Polish, Russian, Turkish, Arabic, Japanese, Korean, Chinese and Bosnian. You can also change the English strings themselves.

Privacy and Access Control

New status pages start private: only members of your workspace, signed in to Uptimy, can see them. Turn on Public access to make a page visible to anyone with the URL. Keep a page private for internal services.

You can also protect a status page with a password. Visitors enter a shared password to view the page, with no Uptimy account required. This is a good fit for sharing status with customers or partners who should not have full public access.

On Enterprise plans, single sign-on can be placed in front of a custom-domain status page via Cloudflare Access, so visitors authenticate with your identity provider (SAML or OIDC — Okta, Microsoft Entra ID, Google, and others). The Uptimy team configures this with you during onboarding.

Private Status Pages

Private status pages work on every plan, with no limit on how many you have. On plans with subscribers, a private page's subscribers still get its updates.

Automatic Updates

Status pages refresh their data automatically, so visitors never need to reload the page manually. When a healthcheck result changes the status of a component, or when an incident is created or updated, the page reflects the change within about a minute.

Best Practices

  • Name components after user-facing services (e.g., "Web App" or "Payments") rather than internal infrastructure names.
  • Link components to healthchecks so status updates are automatic and always accurate.
  • Use a custom domain to build trust with your users and reinforce your brand.
  • Encourage users to subscribe so they receive proactive notifications instead of repeatedly checking the page.
  • Post clear, honest incident updates. Transparency builds trust with your user base.
  • Schedule maintenance windows in advance so the status page reflects upcoming downtime.
  • Review your status page regularly to remove deprecated components and keep the layout clean.

Plan Limits

Free includes 1 public status page, which shows the Uptimy bar. Starter includes 1 public status page with white label. Neither includes status page subscribers (the Atom feed works on every plan). Growth plans support 2 white-label public status pages and 100 subscribers per page. Scale plans offer 5 white-label public status pages and 250 subscribers per page. Enterprise plans offer unlimited status pages and custom subscriber limits. Every plan includes unlimited private status pages.