Pay for how far back you can look.
The agent measures the same way on every tier and stores everything locally regardless. What a paid tier buys you is depth of readable history in the cloud — and because the measurements are physically kept for 30 days for everyone, an upgrade shows you the history you already had rather than starting a new one.
Subscriber plans
For one connection you want to keep honest
3 days of readable history
- Continuous measurement, unlimited
- Link Troubleshooter, on demand
- Speed tests with a bufferbloat grade
- Local history, kept as long as you keep it
- Share with your ISP and raise tickets
For arguing about an intermittent fault
10 days of readable history
- Everything in Free
- Ten days is long enough to cover a working week and the weekend either side of it
- The window most intermittent faults need before a pattern is visible
For reporting upward, across sites
30 days of readable history
- Everything in Pro
- The full physical retention window — nothing measured is out of reach
- Multi-device dashboards
What the tiers actually change, today. The enforced difference between them is the depth of history the cloud will serve you — 3, 10 or 30 days. Everything else in the product behaves identically on every tier. We list it that way because a feature grid with ticks in columns that the code does not check would be a nicer page and a false one.
The tier is an access entitlement, not a deletion schedule.
Why upgrades are instant
Raw measurements are physically kept for 30 days for every account, free included. A free subscriber's fourth-day data exists; it is simply not served. Upgrade and it is there immediately — you are not starting a fresh 10-day collection.
Shortening physical retention per tier would have been cheaper to run and would have put a hole in the history of exactly the person who just paid to see it.
Why we never call it a deletion schedule
The documented storage-limitation policy for raw telemetry is a uniform 30 days, for everyone. Describing 3 days as “free-tier retention” to a user or a regulator would be describing the wrong thing, so we do not.
Asking for more than your tier allows
A request for a longer window is narrowed to what your tier entitles, and the response says it was narrowed. Silently returning three days to someone who asked for thirty is indistinguishable from having no data at all — and would send an ISP looking for an agent that is running fine.
Downsampled history outlives the raw
Rolled-up summaries persist while the account is active on every tier, and are deleted with the account. The 30-day figure is about raw, full-resolution probe data.
Quoted per opted-in subscriber, with a monthly minimum.
ISP pricing is per subscriber who has actually opted in to share with you — not per subscriber on your network, and not per seat on your support desk. There is a monthly minimum. We would rather scope it against your subscriber count and the pilot you want to run than publish a figure that fits nobody.
What a pilot includes
- Organisation verification and your service-ID format
- Portal accounts for your desk, with capability-based roles
- The subscriber-side quality view and the ticket queue
- The NMS integration credential and the published contract
- The onboarding call, and the gap list read out before you sign anything
Talk to us
Tell us your subscriber count, whether you hold your own ASN, and what your support desk uses today.
Contact: [email protected]
Read what the platform does not do yet before you get in touch. It is a real list and it is on the public site on purpose.
Start on the free tier.
The agent runs locally whether or not you ever sign in.