SLA reports
An SLA report is the document you hand to a customer, a boss, or an auditor: for every uptime and ping monitor your team runs, it states the uptime percentage over a period, the downtime recorded, the incidents that occurred, and — because ViewPeek checks from multiple regions — which monitoring zones verified the numbers.
What you get
- A summary across the whole team: overall uptime, total downtime, incident count.
- Per monitor: uptime % (SLA and raw), average and 95th-percentile response times, a daily uptime bar, per-zone breakdown, and the incident timeline for the period.
- PDF — a print-ready A4 statement — and CSV for your own spreadsheets.
Generating a report
- Go to Reports in the top navigation.
- Pick a period: last 30, 90 or 365 days, or the previous calendar month (the usual choice for a monthly SLA statement).
- Review on screen, then click Download PDF or CSV.
Reports cover every uptime and ping monitor owned by anyone on your team. There's nothing to configure per monitor — if it records checks, it appears in the report.
How the numbers are computed
Every check result is aggregated nightly into per-day, per-zone statistics. Uptime is the fraction of successful checks; downtime is estimated as failed checks × your check interval. Periods end yesterday — today's data is included after tonight's aggregation, so a report generated at 4pm doesn't show a half-day that would skew the numbers.
When a monitor is checked from more than one monitoring zone, the report shows each zone's view separately, plus the combined figure. The 95th-percentile response time is the checks-weighted average of daily p95 values, and the PDF labels it as such.
Maintenance & the SLA figure
Downtime recorded while a maintenance window covered the monitor is excluded from the SLA figure — the standard convention in SLA accounting. ViewPeek never hides it though: whenever the two differ, the report shows the raw figure right next to the SLA figure, and states how much downtime was excluded and across how many windows. Your customers see an honest document, not a laundered one.
Schedule maintenance windows before planned work. Windows can't be added retroactively, so downtime from an unannounced deploy counts against your SLA — as it should.
Plan availability
| Plan | SLA reports |
|---|---|
| Free | — |
| Basic | — |
| Pro | PDF + CSV, all periods |
On Free or Basic, the Reports page explains the feature and links to plans. Your monitoring history is being recorded regardless — upgrade later and the report covers the full period retroactively.
Troubleshooting
A monitor shows "no data" for the period. It was created (or resumed) after the period ended, or it was paused throughout. Paused monitors record no checks, so they contribute no data.
Yesterday's outage isn't in the report yet. Daily statistics are aggregated overnight. If the outage happened today, it appears in tomorrow's report.
The SLA figure and raw figure differ. That's maintenance-window exclusion working as designed — see above. The delta is itemised on the monitor's section of the PDF.