Published pages
2
Published status pages
Status pages you choose to publish on Monitorwise. Figures come from real monitors and checks — not demo data or invented uptime.
Only monitors and components you publish appear on public status pages. Private monitors and account data stay private unless you share a link.
Across all published public status pages
Published pages
2
Pages with published monitors
1
Open public incidents
0
Public pages appear here when enabled. A page only shows operational health after active monitors are published to it.
Pages listed here once an account enables and publishes them. Empty slots stay visible until monitors are published to a page.
Monitorwise Status
OPERATIONALMonitorwise Status
ReadyPublished page — no public monitors yet
This page is published, but no active monitors are visible to visitors yet.
Public status pages show selected monitors that the account owner has published. Private monitors and account data are not exposed unless published or shared.
Status pages are generated from configured checks and incident history. They help communicate operational status but do not guarantee zero downtime.
Monitorwise lets each account publish a public status page for the websites they monitor. This overview lists the pages that have been published. There is no league table, no aggregated marketing metric.
A public status page gives clients one link to read during an incident. It replaces ad-hoc “is it down?” emails with a clear, dated record.
Check success is the share of successful health checks versus failures over a rolling window (not calendar time-based uptime). We aggregate results per monitored URL, then roll them up to each customer’s public status page and to this overview.
Yes. Figures and incident counts come from monitoring of endpoints that account holders have chosen to publish. We do not fabricate or demo-fill this dashboard.
This page refreshes its numbers about every 30 seconds. Individual monitors run on each account’s check interval, so underlying data may update more or less often per service.
Rolling check success window applied per page.