How stable were we last month?A number you can present.
This report is for when you owe an answer to a manager, a customer, or yourself: how much we were up, how often it broke, how long recovery took, and how far we are from the target we set.
Free plan: 3 monitors and one vantage point · 14-day Pro trial
What gets calculated
Uptime
From the real check cycles inside the period you chose.
Downtime and incident count
From recorded incidents, with exact overlap against the reporting window.
Mean time to recovery
On average, how long it took for the service to come back.
Error budget
Against the target you set: how much downtime was allowed, and how much is spent.
Targets at several levels
One number for the whole organisation is rarely enough.
From workspace to single monitor
Set a target for the workspace, a group, a tag, or one monitor.
A clear precedence
A monitor's own target beats a tag, a tag beats a group, and a group beats the workspace default.
Breaches marked
When spending passes the budget, the report says so.
Planned maintenance counted separately
Planned versus unplanned
Time inside a maintenance window is reported apart from real outages.
Your choice
You can exclude maintenance from the SLA calculation or include it.
Presentable output
The same report as a PDF to present, and CSV to work with.
Where this stops
The window follows your plan
You cannot report further back than your plan's history retention.
No per-group breakdown yet
Groups and tags are filters for now; an aggregate "by group" report is not built.
From the Pro plan
Reliability reports and SLA targets are available on the Pro plan.
Related features
Start building next month's number now
A report only means something if the data was already being collected.
Create a free account