Latency
Percentiles, not averages
p50, p95 and p99 response times per monitor. Averages hide the slow minute a customer remembers.
- Basic included
- Indie included
- Pro included
- Agency included
Features · Intelligent Analytics
An uptime percentage tells a client the site was up. The analytics tell you why it felt slow on Tuesday, which provider keeps dragging a project down and how long your team takes to notice and to fix. Everything is filed per client, so each answer is about one project at a time.
On every plan
No add-on and no separate tool: these views read the same checks your monitors already run.
Latency
p50, p95 and p99 response times per monitor. Averages hide the slow minute a customer remembers.
MTTR / MTTD
Mean time to detect and mean time to recover, per project. The two numbers a client asks about after an outage.
Trends
Latency and availability trends over the period — the endpoint that gets a little slower with every deploy.
Anomalies
Each monitor learns its own normal. Spikes that never cross a threshold are still marked on the charts for a look; alerts on anomalies come with Agency.
Providers
Compare the providers a project depends on by uptime and speed — useful when a client asks whether to switch.
Dependency map
Scan a client's site and see the third-party services it loads — payment, analytics, fonts, chat — then watch the ones that matter.
| Basic | Indie | Pro | Agency |
|---|---|---|---|
| 2 | 12 | 60 | 120 |
Heatmaps
The availability heatmap lays every hour of the period on one grid, so recurring trouble (the 3 a.m. backup that slows the database, the Monday traffic peak) stands out at a glance.
Availability heatmap
Hour-by-hour availability per monitor or per project, color-coded from 100% down to below 95%.
AI insights
A short note on what the heatmap suggests — written as a hypothesis to check, never as a verdict. How we use AI →
For agencies
When you answer for twenty-five projects, the useful question changes from “is it up?” to “who is affected and how much room is left?”
Cross-client impact
When a provider fails, see at once which clients depend on it — and who to warn before they call you.
SLA & error budget
Set an uptime target and track the error budget that remains, so a promise in a contract has a number behind it.
Predictions
Monitors whose recent behaviour suggests trouble ahead are ranked by risk, with the pattern that raised them.
Revenue correlation alerts
An alert when a drop in a client's revenue lines up with an incident or a latency spike — with a short hypothesis about the link. The correlation view itself starts on Pro. Traffic & Revenue →
Post-mortems
A post-mortem draft built from the incident timeline and the providers involved, for you to review before it goes to the client.
History
How far back every chart can read.
| Basic | Indie | Pro | Agency |
|---|---|---|---|
| 7 | 90 | 90 | 180 |