Watchtower Ping

Public demonstration · Fictional data

An uptime report under your brand.

A readable example of what you can share with a client: monitored sites, incidents and the calculation method.

Studio Horizon, Atelier Martin, the domains and all measurements below are fictional. This scenario illustrates the format; it is not evidence of a real client’s performance or an SLA.

Studio Horizon · Client report

Atelier Martin · September 2026

Period: September 1 at 00:00 to October 1 at 00:00, Paris time. Two sites, one HTTP check per minute per site, with no missing checks in this scenario.

99.96%Successful checks
30 minSummed downtime
2Resolved incidents

Tables scroll horizontally on narrow screens.

Fictional siteSuccessful / total checksUptimeDowntime
boutique-atelier.example43 188 / 43 20099.97%12 min
api.boutique-atelier.example43 182 / 43 20099.95%18 min

Fictional contact: maintenance@studio-horizon.example. Traffic statistics are disabled for this report.

Confirmed incidents in this example

Tables scroll horizontally on narrow screens.

SiteStart · Paris timeResolvedDuration
boutique-atelier.example08/09/2026 10:0008/09/2026 10:1212 min
api.boutique-atelier.example21/09/2026 14:0021/09/2026 14:1818 min

30 minutes is the sum of incidents across two sites, not a 30-minute outage of the whole portfolio.

How the numbers are calculated

Uptime = successful HTTP checks ÷ total checks × 100. Percentages are truncated to two decimals so near-perfect uptime is not shown as 100%.

Shop: 43,188 ÷ 43,200 = 99.97%. API: 43,182 ÷ 43,200 = 99.95%. Combined: 86,370 ÷ 86,400 = 99.96%. Durations come from confirmed incidents: 12 + 18 = 30 minutes. Check percentage and incident duration measure different things; they align in this simplified scenario.

In a real report, missing checks never imply 100% uptime. Reports default to the previous complete month. Detailed checks are retained for 60 days: print the report to PDF in your browser to keep a copy.