Unlisted Entries

Sometimes something only affects a single customer. Maintenance on one volume pool, an outage in an environment nobody else uses. It needs communicating — but not on the front page of your status page, where it reads as a general disruption.

That is what unlisted incidents and maintenances are for. They get a full page of their own under your official status page address. They simply never show up anywhere Statuswerk publishes on its own.

What the switch does

An unlisted entry

  • keeps its own URL and renders in full, with title, timeline and every update
  • does not appear on the status page — not under active incidents, not in the timeline below, not among upcoming maintenances
  • does not appear on the history page
  • does not appear in the RSS feed, and maintenances additionally stay out of the calendar feed
  • does not show up in the uptime bar tooltips

That URL is the entire point. You hand it out deliberately — by email, in a ticket, through your customer portal.

Creating one

  1. Status Pages → Incidents → New (or Maintenances → New)
  2. Fill it in as usual
  3. Turn on Unlisted
  4. Save

The form then shows a Public link field with the address to share, copied with one click. In the overview list, the link icon at the end of the row copies the same address.

You can flip the switch at any time. An entry that turns out bigger than expected becomes visible the moment you turn it off; one that turns out to be a footnote disappears from the page just as quickly.

Subscribers are still notified

Important: Unlisted controls where an entry is shown — not who hears about it. With Notify subscribers on, the notification goes to every subscriber of your status page, unlisted entry or not.

For most unlisted entries you want both together: switch on, notification off, link sent by hand to the customer concerned. The dashboard warns you when both are active at once.

Your team's chat integrations (Slack, Teams, Discord, Google Chat, webhook) report unlisted entries too. They go to your team, not to your customers.

Affected components

If you pick components, they take on the entry's state — and everyone sees that on the status page, even though the entry itself is unlisted. To leave the status page unchanged, leave the components empty and name what is affected in the text.

Uptime

Incidents carry a second switch, Do not count towards uptime. It is off by default, so an unlisted incident counts towards uptime exactly like any other to begin with.

Taking an incident out applies retroactively: the uptime bars are recalculated immediately, including for days already past. The same happens if you put it back in later.

It is the right switch for work too small to describe your service's availability honestly. Use it sparingly — an uptime figure that hides everything inconvenient is worthless to your customers.

Maintenances have no such switch: in Statuswerk, scheduled maintenance never counts as downtime in the first place.

Not an access control

The page of an unlisted entry is not password protected. Anyone with the URL can open it, and anyone who forwards it forwards the access. It is simply linked nowhere and listed in no feed.

For incidents with confidential content this is the wrong switch. Either put the details where access is controlled and keep the entry brief — or put the whole page behind a password, see Password-protected Pages.

Through the API

Both fields are available over the REST API:

curl -X POST https://statuswerk.eu/api/v1/incidents \
  -H "Authorization: Bearer $STATUSWERK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Maintenance on volume pool nbg1-dc3",
    "message": "Only volumes in this pool are affected.",
    "is_unlisted": true,
    "excluded_from_uptime": true,
    "notify_subscribers": false
  }'

Both fields default to false, so an entry is listed normally unless you say otherwise. Maintenances take is_unlisted as well; excluded_from_uptime does not apply to them.

The response carries the link to share in public_url — full description in the API reference.

Over MCP, create-incident and create-maintenance take the same is_unlisted and notify_subscribers and return public_url.