1. Status Page System
  2. Reports and analytics
Reference

Reports for the questions your team asks

Review component condition, incident timing and communication history.

Overview
Status Page System · Overview

Status Page System dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Incidents by status

How far records got this quarter

StageReachedStep
Open45
Acknowledged1840%
Investigating528%
Resolved120%

Incidents by status

Sample counts per stage

100
-10Open
0Acknowledged
10Investigating
-30Resolved
-10Closed
Example screen with sample data

Questions to answer

What happened during an interruption?

Compare opening, acknowledgment, investigation updates and resolution.

What did customers hear?

Follow each published message, audience and incident link in time order.

Which planned work is close?

Review change windows and risk before the service owner prepares notice.

Which requests are late?

Compare due dates with the recorded completion outcome.

More reports

Component status by service Grouped

Group component status under each service to locate current degradation.

Incident priority and status List

Compare priority with the current incident state and assigned person.

Incident acknowledgment and resolution List

Compare opening, acknowledgment and resolution dates by service.

Public update chronology List

Read publication times and audiences alongside their linked incidents.

Planned change windows List

Review scheduled start and end dates by service and risk.

Request completion List

Compare request dates, due dates and completion dates with status.

Problem investigation List

Group current problem states by service and owner.

Integration receipt outcomes List

Review received, applied, rejected and failed events by provider.

Set up Status Page System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started