WISP SLA & Uptime Reporting: What to Track and How to Report It

Most WISP SLAs are simple uptime percentages — 99%, 99.5%, 99.9% — sometimes scoped per tower, per customer tier, or fleet-wide. The number matters less than being able to prove it, consistently, over the period a contract actually covers (monthly or quarterly, not “since I last checked”).

Most monitoring dashboards — including the classic ones WISPs grew up on — show you the last few hours or the current poll window. That's exactly what you need to react to an outage live, and exactly the wrong data to prove a month of uptime. Without retained history, “how did tower 14 do last month” is a question you can't actually answer after the fact.

• Daily uptime % per device, rolled up to per-site and per-customer.
• Latency and CCQ trend, not just the current value — a slow decline over weeks is as real a problem as a hard outage, and it's the thing retained history is for.
• Worst-day flags — the single worst day in the period is usually what a customer asks about first.
• At least 30 days, ideally 90, so a monthly SLA report and a quarterly review both have real data behind them.

Hand over a report, not a screenshot. A simple exportable table — site, average uptime, average latency, worst day, and whether the period met the agreed SLA target — is both easier to produce and harder to argue with than a narrative summary. Flag breaches clearly rather than burying them in an average; customers trust the numbers more when the bad ones aren't hidden.

The 📊 Trends & SLA tab retains 30/90-day latency, CCQ, traffic and uptime history per site from the day it's deployed — not just the live poll window — with a selectable SLA target and a one-click CSV export per site. It's built to be handed to a customer or kept for your own records, not just looked at on a screen.