Feature
Reports & analytics
Numbers that come from the checks that actually ran, which is what makes them worth putting in front of a client.
What it does
Uptime is calculated from recorded incidents and real downtime windows, not from a rolling average that quietly forgives the gaps. Response time is charted over the period so a site that is slowly degrading looks different from one that is simply slow.
The same data serves two audiences. Internally it is an overview of every site you look after, sorted by what needs attention. Externally it is a report for a client who wants to know what they are paying for.
That report does not have to come from you. The client can produce it from their own portal — monitoring, or usage and billing — for the period and the sites they pick, and take the PDF away. Each one is stored as a document rather than recomputed on demand, so the copy they filed in March still says in June exactly what it said in March.
A report states what it does not know. A period where no checks ran is not reported as perfect uptime, an outage still open at the period end is counted separately from those that closed, and a figure that cannot be derived says so in words rather than printing as zero.
Reports can also be shared by link for clients who will not sign in to anything, and exported when somebody needs the raw figures.
- Uptime percentages derived from measured downtime windows
- Response-time charts across the period
- Full incident history per site
- PDF reports the client can produce themselves, for the period they pick
- Documents stored once, so a report never changes after it is filed
- Shareable report links and data export
Works alongside
Uptime & performance
HTTP/HTTPS checks around the clock — down to every 30 seconds. Status codes, response time (TTFB), payload size, plus ICMP ping and TCP-port checks per site.
Read moreSSL, domain & security
Certificate-expiry and domain (WHOIS) expiry alerts days in advance, SSL chain validity, and a security-headers audit (HSTS, CSP, X-Frame-Options).
Read moreContent & keyword checks
Catch the “white screen of death” at HTTP 200: keyword present/absent, unexpected redirects to foreign domains, and page-defacement detection.
Read moreFAQ
About reports & analytics
How is the uptime percentage calculated?
From the downtime windows that incidents actually recorded — the time between a check failing and the site answering again — rather than a smoothed average.
Can I send a report without giving the client an account?
Yes. A report can be shared by token link, which shows the figures without a login.
Does the client have to ask me for a report?
No. They produce it in their own portal, choosing the type, the period and which of their sites to include. You see the same history of what was produced.
If a month had an outage that is still open, what does the report say?
It says so. Outages that closed in the period and one still running are counted separately, and the downtime figure names which of the two it covers. A period with no checks at all is reported as unknown, never as perfect.
How far back does the history go?
Checks and incidents are kept as a running history per site, so reports can be produced for past periods rather than only the current one.