Status page settings

Everything lives under Status Pages → your page, split across tabs.

General

  • Name — the title at the top of the page and in notifications.
  • Timezone — the time all timestamps are shown in: on the page, in the RSS feed and in notification mails. It is also the time you enter incidents and maintenance in on the dashboard. Use your customers', not your server's. The calendar feed (.ics) and the API return times with their offset; your calendar or script converts them itself.
  • Language — German or English. It applies to everything visitors and subscribers see: the public page, the RSS and calendar feeds, the badge and every email, SMS and webhook text sent to subscribers — from "New incident" to dates and times. Your own texts (titles and messages) stay as you write them, so set the language to the one you write your updates in. Independent of your dashboard language; a new page starts in your dashboard language.

Branding

  • Logo — replaces the name at the top, 48 pixels high. SVG, PNG, JPEG, WebP or GIF up to 2 MB. SVG is best: it stays sharp everywhere. A raster image should be at least twice that height.
  • Logo for the dark theme — optional. Shown when the page is dark (with System, the visitor's browser decides), so a dark logo does not disappear.
  • Favicon — the browser tab icon. SVG, PNG, ICO, WebP or GIF up to 512 KB.
  • Primary colour — colours buttons, links and charts. Text on it turns black or white automatically, whichever reads better.
  • Operational colour — optional. Colours the uptime bars, the status badges and the banner while everything works. Left empty, it stays the default green. Yellow, orange, red and blue for incidents and maintenance stay fixed, so a problem looks the same on every page. In the API the field is operational_color; null resets it.
  • Theme — light, dark, or System (follows the visitor's own setting).

Logo, favicon, colour and theme are in every plan. A status page without your own logo looks like a wrong turn.

Through the API you upload logo, dark-theme logo and favicon with POST /api/v1/statuspage/logo, /logo-dark or /favicon, in the same formats.

SVG is stored sanitized. An SVG file can carry scripts. On upload we remove scripts, event handlers and references to other files; what is no usable SVG afterwards is refused. Because Gmail and Outlook show no SVG, notification mails automatically get a PNG version of your logo.

Display

  • Published — the master switch. Off means nobody can reach the page under its address; whoever opens it sees “This status page is not available right now”. Your team still sees it: in the list of status pages and on the edit screen, Preview opens the page with a note that it is not published. Subscribers get no notifications until the page is published; their unsubscribe and manage links keep working. For an internal page others should open, there are password protection and the IP allowlist.
  • Password protection and Restrict to networks — see Private status pages.
  • Show uptime, Uptime days, Degraded threshold — see Uptime.
  • Show combined uptime chart — the chart at the top of the page, the average across all components. Off to show only the per-component bars.

Headings

Your own wording for the page's headings: Active incidents, Scheduled maintenance, Service uptime per component, Timeline, System metrics, Incident history and Past maintenance. An empty field shows the default in the page's language; the placeholder tells you which. Up to 80 characters each, text only. The history link in the footer carries the same heading as the history page. On every plan. In the API the field is section_titles, an object with the keys active_incidents, scheduled_maintenance, component_uptime, timeline, metrics, incident_history and past_maintenance; only the keys you send change, null resets one.

Subscriptions

Here you decide which channels visitors may subscribe to: email, SMS, webhook and RSS/calendar. The master switch Allow subscriptions hides the sign-up area entirely.

SMS and webhooks depend on your plan. If your plan includes SMS, a new page starts with it switched on. Details under Subscribers.

Domain

  • Subdomain — your address under statuswerk.eu.
  • Custom domain — your own address, certificate included. See Custom domains.

SEO

  • Meta title and meta description — what appears in search results and link previews. Left empty, we use the name and a default that names the page. We add " - Status" to the title unless the word is already in it ("Rechnungskit Status" stays as it is).

  • Hide from search engines — sets noindex, nofollow. Search engines that respect it will not list the page.

    This is not access control: anyone with the address still gets in. For real restriction see Private status pages.

    From the Basic plan.

Preview when shared

When someone shares the link to your status page — in Slack, Teams, LinkedIn or a messenger — a preview picture appears: your logo, the page's name, its current state ("All Systems Operational", "Major Outage" …) in its colour, and the address. With it, the meta title and meta description from the SEO section.

The picture is made automatically and redrawn as soon as the state, logo, name or colour changes. Platforms do keep previews for a while, though; a link that was shared before may still show the older picture there.

On a private status page the picture sits behind the password or IP allowlist too — whoever may not open the page gets no preview of its state either.

Visitor analytics

How many people look at your status page during an outage is a useful number. Under Custom code → Analytics you pick a privacy-friendly provider:

  • Plausible (plausible.io) — the domain you registered the page under in Plausible.
  • Umami Cloud — the website ID.
  • Matomo Cloud — the site ID and your instance's address, e.g. https://your-company.matomo.cloud. With us, Matomo always runs without cookies: status pages have no consent banner, and someone checking during an outage should not have to dismiss one.

We write the code for it from your settings. No custom JavaScript is needed, and it stays excluded.

Self-hosted servers (your own Plausible, Umami or Matomo) are not possible for now: a server of your choosing could load any script onto the page — exactly what we exclude for custom code.

Name the provider in your privacy policy; it processes your visitors' page views.

From the Pro plan.

Custom code

Three fields for your own HTML and CSS: header HTML (before </head>), footer HTML (before </body>) and custom CSS.

Meant for web fonts, verification tags and a fit to your design system.

Scripts do not run. Your status page lives on our domain, so we serve markup and styling, but nothing that executes. When you save, we remove:

  • <script>, <iframe>, <object> and similar embeds
  • event handlers such as onclick or onload
  • javascript: links

In the header only <link> and <meta> stay. Put styling in the CSS field. What the form shows after saving is exactly what the page serves. An analytics snippet therefore does not belong here but under Visitor analytics.

If you move to a plan without custom code, the page stops serving it. It stays stored and is back as soon as the plan includes it again.

From the Business plan.

White label

On Business the "Powered by Statuswerk" line disappears from the page footer — and from the calendar feed, which otherwise shows up in the customer's calendar app. There is no switch for it: the plan is enough.

Several status pages

Depending on your plan you can run several status pages in one workspace — a public one and an internal one, say, each with its own domain, components and subscribers. The number is in the pricing table. Who may see and change which page is set under Team.

Deleting: in the page's settings with Delete at the top right, through the API with DELETE /api/v1/statuspages/{id}. It is final: components, incidents, maintenance, subscribers and the custom domain go with it; subscribers are not notified.