An availability report takes the continuous Up/Down tracking described in Availability Monitoring and rolls it up into a summary for a chosen period — the figures most often shared with management, customers, or anyone who needs the uptime story without digging through raw history.
What's in an availability report
- Uptime percentage per host or service, over the selected period
- Total downtime, both as a duration and a count of separate outage events
- A breakdown of individual downtime events, with start and end times
- Scheduled maintenance excluded from the figures, provided maintenance windows were set up correctly at the time (see Availability Monitoring for how that exclusion works)
Scoping a report
Reports can cover a single host, a host group (for example, everything at one site), or your whole monitored environment. Scoping to a meaningful group — rather than everything at once — usually produces a far more useful report: "Core Network — August" tells a clearer story than an undifferentiated list of every host you monitor.
Common uses
- Monthly operations review, giving a team or manager a regular pulse on infrastructure reliability
- Customer- or vendor-facing reporting, where a client needs evidence that agreed service levels were met
- Post-incident context, showing how a specific outage affected that host or service's uptime figures for the period it fell in
Where availability reports stop short
An availability report tells you uptime happened, but not whether a target was actually met — that comparison against a defined target, plus tracking of breaches, is what SLA Reports adds on top of the same underlying data.