Skip to content

Reports

Turn service health into clear impact reports.

Summarize downtime, affected services, incident duration, and operational impact for the people who need the answer without the raw noise.

Four ways to answer "what happened?"

Executive Summary

A weekly, stakeholder-level view of service health: uptime, incidents, and what changed. Give leadership a clear answer without sending raw monitoring noise.

Impact Report

Downtime, degraded time, affected services, and confirmed incidents for a period, ranked by criticality. Explain what happened, why it mattered, and how the team responded.

Scheduled report emails

Daily, weekly, or monthly service-health summaries delivered by email to the people who asked for them. Set it once in Notifications.

Export data

Export check results, incidents, and monitor configurations as CSV or JSON for any date range, to build your own reports, feed a BI tool, or keep an archive.

Inward and outward

One report for the team, one page for everyone else.

Impact Report. Downtime, degraded time, affected services, and confirmed incidents for any period, ranked by criticality.

Public status page. What customers and clients see: history, resolved incidents with a plain-language message, upcoming maintenance.

For agencies

Clients ask what happened after an issue. Tag services by client, pull the Impact Report for the period, and send a summary instead of assembling a spreadsheet from alert emails.

Monitoring for agencies

For customers

Reports look inward. Public status pages communicate outward, with incident messages, maintenance notices, and optional 24-hour history, listing only the services you choose.

Status pages and badges

Make reporting a habit, not a scramble.

Executive Summary is included from the Growth plan. Impact Report and data export are included in Business.