---
title: Status pages can say why something is down
description: An auto-published incident always read "db-01 service disruption", whether a disk had filled up or a site was returning errors — visitors had to wait for…
canonical: https://watchfor.io/changelog/2026-09-23-status-page-incident-cause
---

[All updates](/changelog/page/2#2026-09-23-status-page-incident-cause) ✨ New Sep 23, 2026 · v 8.2.9

# Status pages can say why something is down

An auto-published incident always read "db-01 service disruption", whether a disk had filled up or a site was returning errors — visitors had to wait for someone to write an update. Each status-page component now chooses how much it explains: Status only (the default, unchanged), Cause — the kind of problem in plain words, such as "Disk space running low" or "Returning errors", never a value or path — or Full detail, the detected value ("Disk / is 92.0% full") for internal pages. It works for monitors and servers alike.

Pick how much the notice explains; the example underneath follows your choice.

## The problem

When an incident went to your status page automatically, it always read "db-01 service disruption". Visitors couldn't tell a full disk from a site returning errors, so someone on your team had to write an update by hand before anyone outside knew what kind of problem it was.

## Three levels, chosen per component

In a component's settings, Incident details on the public page offers:

- Status only , the default and unchanged: down or up, nothing about why.

- Cause : the kind of problem in plain words, such as Returning errors , SSL certificate expiring , Missed its scheduled check-in or Disk space running low . Never a value, a path or a process name.

- Full detail : what was detected, for example "Disk / is 92.0% full". Meant for password-protected or internal pages.

## Example

Your API starts answering 500. With Cause set on the API component, the notice that appears on the status page is titled "API: Returning errors" instead of "API service disruption". Customers know what kind of problem it is while your team writes the follow-up.

## Good to know

- An incident shown under several components says only as much as the most private of them allows.

- The setting applies to incidents published after you change it. Earlier notices keep their wording, and you can still edit any notice by hand.

- Credentials inside URLs are masked at every level. Data-breach checks always keep the generic wording.

Open a status page, click the pencil on a component and pick a level. See [Incident details on the public page](/docs/status-pages/components#incident-details-on-the-public-page).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-23-status-page-incident-cause · Site guide: https://watchfor.io/llms.txt