---
title: "Component impacts on status reports"
url: "https://www.openstatus.dev/changelog/status-page-components-impact"
date: "2026-06-11"
author: "openstatus"
description: "Tell visitors which components are affected and how badly — per update, over the whole incident."
category: "statuspage"
image: "https://www.openstatus.dev/assets/changelog/status-page-components-impact.png"
---

Status reports can now carry a per-component **impact**: `operational`, `degraded performance`, `partial outage` or `major outage`. Instead of a single coarse "degraded" signal, every report update snapshots how badly each affected component is hit — and you can change those impacts update by update as the incident evolves.

On the public status page:

- component rows and the top-level indicator derive their color from the worst active impact
- the report timeline shows impact change badges per update, so visitors can follow recovery (major outage → partial outage → operational)
- the bar hover card surfaces the day's worst impact
- manual uptime now weights time-in-status per component — a partial outage no longer counts the same as a full one

In the dashboard, pick an impact per component when creating a report or posting an update; you can also edit impacts on existing updates. Impacts are available on the API and importers from Atlassian Statuspage and Better Stack preserve per-update impacts on migration.

Check out the [status report reference](https://www.openstatus.dev/docs/reference/status-report#component-impacts) for more details.

Existing reports are untouched — they keep today's behavior until you set impacts on a new one.