Uptime Reporting Sample: What BPro Technologies Reports Every Month
Inspect a sample managed IT report covering availability, incidents, patching and backup checks. Understand uptime calculations and the questions to ask.
/ Guide map
What an uptime percentage actually means in minutes
Incident and uptime bands: reporting severity, not just availability
What separates a useful report from a tool export
Questions to ask about reporting before you sign
Best for
Buyers who want evidence behind monitoring and response and monitoring claims
Decision support
Direct answer
This guide explains how to read an uptime and incident report. Start with the monitored service, reporting period, measurement source, and treatment of maintenance windows. Then review outage duration, incident ownership, recurrence, and follow-up actions. Availability figures are only comparable when they use the same scope and calculation.
Example target only. Final SLA depends on monitored services and service terms.
Priority response targets are confirmed in the managed service agreement.
Ticket trends, risks, patching, and backup status
| Report section | What it should show | Why it matters |
|---|---|---|
| Availability | Uptime by service, site, or device group | Confirms whether systems met agreed targets |
| Incidents | Priority, cause, owner, resolution time | Shows whether recurring issues are being removed |
| Patching | Current, overdue, failed, deferred | Turns patching from a promise into evidence |
| Backups | Last successful backup and restore-test status | Shows backup status and evidence for the specific restore scenarios tested |
| Security | Alerts, contained events, exposed credentials, policy changes | Gives leadership a risk picture |
What an uptime percentage actually means in minutes
The examples below assume continuous coverage, a 30-day month and a 365-day year, before any contractual exclusions. Multiply the minutes in the period by the unavailable percentage. Use your actual reporting window and SLA definition when checking a service.
| Availability | Downtime per month | Downtime per year |
|---|---|---|
| 99.0% | 7 hours 12 minutes | About 3 days 15 hours |
| 99.5% | 3 hours 36 minutes | About 1 day 20 hours |
| 99.9% | About 43 minutes | About 8 hours 46 minutes |
| 99.95% | About 22 minutes | About 4 hours 23 minutes |
For a 30-day month, the difference between 99.5% and 99.9% is about 173 minutes of downtime. Set targets around business impact, dependencies and the cost of the required design and support. A percentage alone does not establish service quality.
Incident and uptime bands: reporting severity, not just availability
A single availability number hides the thing leadership actually cares about, which is whether the outage stopped work. Banding incidents by severity separates a monitoring blip from a day nobody could invoice, and it is what makes a report readable by someone who is not technical.
Band 1 — business stopped
A core system is unavailable and work cannot continue. Record impact, response, cause where known and corrective actions.
Band 2 — degraded but working
Slow performance, a failed integration or an affected team or site. Summarise trends, and describe individual incidents when their business impact warrants attention.
Band 3 — detected and contained
Detected and resolved before known user impact. Record what was observed, the action taken and any uncertainty about impact.
Report all agreed incident categories alongside their impact and recurrence. More detected events can reflect wider monitoring or increased threat activity, so interpret changes in counts with the underlying records rather than treating them as proof of prevention.
What separates a useful report from a tool export
An automated report can provide useful measurements. Review whether it explains business impact, exclusions, recurring problems and actions, with enough context for the intended reader.
- Written in plain language, not alert names and device identifiers
- Backup section shows the last successful restore test, not only the last successful backup
- Patching shows what is overdue and why, not just a compliance percentage
- Recurring issues are tracked across months rather than reset each period
- Every open risk has a named owner and a next action, not just a status
- It states what was not covered, so gaps are visible rather than implied
Questions to ask about reporting before you sign
- Can I see a real sample report, with client details removed?
- Which services are actually monitored, and which are excluded?
- How is downtime measured, and does it start when monitoring detects it or when a user reports it?
- Is a restore actually tested, and how often?
- Who reviews this report with us, and how often?
- What happens to an open risk that is still open three months later?
The third question separates providers more than any other. If downtime is only counted from the moment a user raises a ticket, an outage that started at 3am is measured from 9am, and the report will look considerably better than the month actually was.
Monitoring should create evidence
BPro Technologies reports monitoring outcomes in a format business owners can read, not only tool exports engineers understand.
Get Free IT Assessment/ Choose the next step
Move from guidance to a practical review path.
Pick the route that best matches the operational question behind this resource so the next conversation starts with the right scope.
Assessment path
Review support, monitoring, or ownership gaps
Use the free assessment when the issue involves helpdesk flow, documentation, Microsoft 365, Google Workspace, recurring support issues, vendor handoffs, or backup visibility.
Service path
Compare managed and co-managed support paths
See how BPro Technologies structures managed IT, co-managed escalation support, onboarding, reporting, and recurring operational ownership.
Team path
Share the support requirement
If you already know the problem area, send the users, tools, urgency, and support model question so the team can review the next step.
Questions buyers ask
What should a managed IT uptime report include?
Availability by service, incidents banded by severity, response and resolution times, patch status including what is overdue, backup health with restore-test evidence, security alerts and containment, and open risks with a named owner. It should also state what was not monitored, so gaps are visible rather than implied by omission.
What does 99.9% uptime actually mean?
For continuous coverage, 99.9% availability corresponds to about 43 minutes of downtime in a 30-day month or 8 hours 46 minutes in a 365-day year. At 99.5%, the same 30-day month allows 3 hours 36 minutes. Apply the actual SLA window and exclusions before comparing figures.
What is incident and uptime band reporting?
In this illustrative model, Band 1 means work stopped, Band 2 means degraded service and Band 3 means an issue detected and contained before user impact. Agree categories with your provider. Counts alone do not demonstrate improvement; review impact, recurrence, monitoring coverage and corrective actions together.
How do I know if an IT report is meaningful or just a tool export?
Check whether the report includes restore-test results, recurring incidents, measurement scope and open actions with owners. An automated or manually prepared report should be judged against the same evidence requirements.
When does downtime start being counted?
It depends on the agreement, and it is worth asking directly. If downtime is counted from when a user raises a ticket rather than when monitoring detects the fault, an outage beginning at 3am is measured from 9am. That single definition can make a poor month read as a good one, so confirm it before signing.
Is uptime the same as Microsoft 365 or cloud provider uptime?
A cloud-provider availability measure and your business service measure can have different scopes and calculation rules. Review both alongside identity, connectivity, devices and application dependencies. Define the systems and reporting period before drawing conclusions from either figure.
How do you calculate allowed downtime from an uptime SLA?
Multiply the minutes in the period by the share of time the system is allowed to be down. A 30-day month has 43,200 minutes, so 99.9% uptime allows 0.1% of that, about 43 minutes a month. 99.5% allows about 216 minutes (3.6 hours), 99.95% about 22 minutes and 99.99% about 4.3 minutes. To work out uptime from an incident log, divide the minutes the service was available by the total minutes in the period and multiply by 100, counting only the hours the SLA covers.