--- title: Uptime & SLA Reports, Scheduled by Email description: Uptime reports by email, weekly or monthly: uptime, incidents, MTTR and response time vs the previous period, with the monitors behind the trouble ranked first. canonical: https://watchfor.io/reporting --- # Uptime Reports That Say What Changed An uptime percentage alone doesn't say whether things got worse or why. Each WatchFor report compares with the previous period and says what changed. [Get started for free](/auth/sign-up)[View pricing](/pricing) ## One Report Engine, Every Surface The email, the dashboard and the API are rendered by the same engine, so their numbers match ### Scheduled Email Reports Weekly on Mondays for the previous 7 days, or monthly on the 1st for the previous calendar month. Up to five recipients per cadence, with no WatchFor account needed, and a one-click unsubscribe in every email. ### Every Number Has a Baseline Uptime, incidents, downtime, MTTR, MTBF and response time each come with the value for the previous period of the same length and the difference between the two. ### Plain-Language Insights “checkout caused 7 of 10 incidents this period — a single root cause is likely.” Rules read the numbers and write findings ranked by severity: uptime drops, incident concentration, slower resolution or acknowledgement, slower responses, and failed checks that never became incidents. The report leads with the two that matter most. ### Response Time and Check Success Average and p95 response time against the previous period, with the slowest monitor named when things got slower. Check success sits next to uptime, so failed checks that never became incidents are explained instead of puzzling. ### Same Uptime Math as the Dashboard Uptime counts only time spent in confirmed critical incidents, minus scheduled maintenance. A failed check that never became an incident does not lower it, and incidents marked as false positives are left out. ### On-Demand in the Dashboard The last 7 or 30 days on every plan, from the same engine as the email. Print it, save it as PDF or download it as CSV. ### The Same Report for Scripts and Agents GET /api/v1/reports returns the full report as JSON. The MCP server has a get_report tool and the A2A agent an org-report skill, so an agent asked how the week went quotes the numbers the email showed. ### Worst-First Monitor Table The ten monitors with the most trouble, each with uptime and its change, average and p95 response time and incident count, sorted so the worst one is row one. ## What a report contains Monitors ranked worst-first, with uptime, response times and incidents. Type-aware sections: SSL, domains, Web Vitals, cron jobs, blocklists, MCP. Per-host uptime and resources, and the report by email weekly or monthly. ## Why WatchFor Reports? An uptime report that is just a percentage and an average response time gives the same two numbers for an HTTP check and an SSL certificate, and no way to tell if this week was better than last. WatchFor reports count confirmed incidents across every monitor type, and every figure carries the previous period. That answers three questions: is it getting better or worse, what caused it, and what needs attention before it pages someone. [Start monitoring now](/auth/sign-up) Weekly and monthly emails, up to five recipients per cadence Every headline number compared with the previous period Insights name the monitor behind most of the incidents The ten monitors with the most trouble, ranked worst-first Failed checks that never became incidents explained, not hidden Uptime excludes scheduled maintenance and unconfirmed failures The same JSON over REST, MCP and A2A for agents and scripts Every change to email settings is recorded in the activity log ## How Reports Work From raw checks to a sentence that matters 1 ### Checks Accumulate Your monitors run from the locations you picked; every result is stored with its location, and incidents count only once they are confirmed. 2 ### The Engine Aggregates For the report period and the one before it: uptime per monitor, response times, incident MTTR and MTBF, and downtime with maintenance subtracted. 3 ### Insights Are Derived Rules read the numbers (uptime drops, incident concentration, slower resolution, slower responses) and write findings ranked by severity. 4 ### Delivered Everywhere Rendered to email on your schedule, to the dashboard on demand, and served as JSON to the API, MCP and A2A. One engine, so the numbers match. ## Reporting Use Cases Who reads a WatchFor report ### The Monday Ops Review The weekly report arrives on Monday: what broke, what got slower and which monitor caused most of it. The team starts the week from the same facts. ### Stakeholders Without Dashboards Add a manager or a client as a recipient. They get the numbers every month without logging in. ### Agencies Reporting to Clients Add the client as a recipient and they get the numbers every week or month without an account. Before a meeting, print the on-demand report as PDF or download it as CSV. ### AI Agents on Duty An agent connected over MCP answers “how reliable were we this month?” with get_report, using the same numbers the email showed. ## Frequently asked questions Everything about WatchFor reports [All questions→](/faq)[Ask us directly](/contact) When do scheduled reports send? Weekly reports send on Monday and cover the previous 7 full days; monthly reports send on the 1st and cover the previous calendar month (both in UTC). The weekly email is on by default for new organizations and goes to the owner. The email always states the exact period it covers. Who can receive report emails? What are type-aware sections? How is uptime in the report calculated? What does the comparison show? Can I get the report without email? Can I export a report? Can I get these numbers into Grafana? Can AI agents read the reports? What's on the free plan? ## From our blog Guides, deep-dives, and best practices from the WatchFor team [Reliability ### How to read (and write) an SLA report that isn't lying Aug 23, 2026·4 min readRead article](/blog/honest-sla-reports)[Engineering ### What it actually took to make a monitoring platform agent-ready Aug 28, 2026·7 min readRead article](/blog/what-it-took-to-make-monitoring-agent-ready)[Reliability ### Incident Severity Levels (SEV1–SEV4) Explained Nov 20, 2025·3 min readRead article](/blog/incident-severity-levels) ## Your First Report Arrives Monday New organizations get the weekly email by default, addressed to the owner. Add recipients or turn on the monthly report under Reports, and open the on-demand report whenever you need it. Free plan available, no credit card required. [Get started for free](/auth/sign-up)[View documentation](/docs/reports) --- Canonical page: https://watchfor.io/reporting · Site guide: https://watchfor.io/llms.txt