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 checks and incident history into reports agencies can use with clients: 7, 30, and 90-day uptime, P90 latency, averages, affected services, and 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 available it was, how latency behaved, and which incidents explain the exceptions.
P90 latency
Show the slow tail clients feel. Averages can hide painful requests; P90 latency makes the complaint visible.
Incident history
Tie downtime back to timestamped investigating, identified, monitoring, and resolved updates.
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.
Operational memory
Incident timelines preserve what happened and when, so reports do not depend on someone remembering the outage later.
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