SLA windows
Report uptime over the 7, 30, and 90-day windows that show recent health and longer-term reliability.
Client uptime reports
Client-ready uptime reports.
Before they ask.
StatusPulse turns endpoint check history into reports agencies can use with clients: selectable uptime windows, successful and failed totals, average and P90 latency, plus weekly digest summaries.
Built for SLA conversations, incident reviews, and client portfolio operations.
Readable evidence
Clients need answers, not raw check logs.
When a client asks about reliability, the useful answer is short: what was checked, how many checks passed or failed, how available it was, and how latency behaved.
P90 latency
Show the slow tail clients feel. Averages can hide painful requests; P90 latency makes the complaint visible.
Failure totals
Keep successful and failed check counts beside the uptime percentage so the result has a visible denominator.
Report output
Checks, failures, uptime, and tail latency in one table.
Weekly digest
Send the uptime conversation before it becomes a ticket.
Every workspace can send its team a weekly SLA summary. That keeps client stakeholders informed before a renewal call, monthly review, or outage question forces the report to be assembled by hand.
Per workspace
Reports follow the same client boundary as endpoints, users, incidents, and status pages.
Service context
Each report starts from the services the workspace actually monitors, not a generic dashboard export.
Retained measurements
Reports read the workspace’s retained check logs, keeping calculated uptime and latency tied to recorded requests.
Make uptime reporting part of the client workflow.
Create one workspace, add the first endpoint, and let reports accumulate from real checks.
Create a workspace