---
title: X
description: When someone asks for proof of last quarter's uptime, a screenshot of a dashboard does not cut it. You can now generate a printable uptime and SLA report over…
canonical: https://watchfor.io/changelog/2026-06-22-sla-report
---

[All updates](/changelog/page/9#2026-06-22-sla-report) ✨ New Jun 22, 2026 · v 3.0.6

# Printable uptime SLA report

When someone asks for proof of last quarter's uptime, a screenshot of a dashboard does not cut it. You can now generate a printable uptime and SLA report over any custom date range, ready to hand to a customer or attach to a review.

Uptime by day, week, month or a range you pick, ready to export.

## What the report shows

Open a monitor's Uptime SLA tab. You see uptime for the last 7, 30 and 365 days, and below it a table by day, week, month or year, or for any range you pick. Each row has the uptime, the downtime, the number of incidents and the mean time between failures. Export report gives you a printable version.

Only critical incidents count as downtime, so a warning about slow responses doesn't eat into your SLA.

## Example

A customer's contract promises 99.9 % a quarter, and they ask for proof. Select July 1 to September 30 on the API monitor, check the rows and export the report: 99.97 % and one 26-minute incident, on one page you can attach to your reply.

See [The Uptime SLA tab](/docs/monitors#the-uptime-sla-tab).

Since then, planned work inside [maintenance windows](/changelog/2026-08-10-maintenance-windows) is left out of the numbers, and the tab [follows the same uptime rule as everything else](/changelog/2026-09-06-uptime-sla-accuracy): an acknowledged incident counts until it resolves, false positives don't count, and days follow your profile's time zone. [Reports](/changelog/2026-09-01-reports) now cover your whole organization.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-06-22-sla-report · Site guide: https://watchfor.io/llms.txt