WordPress uptime monitoring for every site in the fleet
A fleet status matrix shows which sites are up, degraded, or down in real time. Response-time trends, TLS expiry warnings, and instant alerts mean you know before your clients do.
Finding out a site is down from a client message is already too late
Uptime tools that only ping a URL once a minute miss degraded responses, slow TLS handshakes, and partial outages that look fine from the outside. A fleet manager needs to distinguish a site that is genuinely unreachable from one that is just quiet, and alert the right person within seconds, not minutes.
Under the hood
The steps that make it work, and what each one does.
Fleet status matrix at a glance
Every connected site is shown in a status matrix: up, degraded, or down. The matrix updates in real time over a server-sent events connection, so you see state changes as they happen.
Response-time trends over 7, 30, and 90 days
Per-site response-time history is plotted at 7, 30, and 90 day horizons. Latency spikes and gradual degradation stand out before they become customer-visible outages.
TLS expiry and PHP fatal tracking
WPMgr warns when a TLS certificate is approaching expiry and tracks PHP fatal errors reported by the agent, so infrastructure health is visible alongside application health.
Down and recovery alerts
Configure email or webhook alerts for down and recovery events per site. Alert channels are scoped to a site or the whole fleet, and repeated alerts are suppressed while a site stays down.
What's included
Every capability ships in the open-source release.
Fleet status matrix
Up, degraded, and down states across every connected site in a single view, updated in real time over SSE, no manual refresh.
Response-time history
7, 30, and 90 day response-time trends per site. Spot gradual degradation before it becomes a complete outage.
TLS expiry warnings
Certificate expiry dates are tracked and surfaced in the dashboard with configurable early-warning windows.
Incident history
Every down and recovery event is recorded with a timestamp and duration, giving you a durable log to draw on for client reports.
Accurate idle vs unreachable detection
The sweeper verifies quiet sites directly rather than relying only on heartbeats, so the status badge accurately shows unreachable versus idle.
Screenshot-backed site cards
Each site in the grid view shows its live screenshot alongside uptime, latency, SSL expiry, and backup health, so you can see the visual state of the site alongside its health metrics.
Questions answered
Common questions about this feature.
How does WPMgr detect a site that is down versus just quiet?
WPMgr uses a sweeper that probes quiet sites directly, not just heartbeats from the agent. A site that has not sent a heartbeat for a while but responds to a probe is marked idle, not unreachable. The status badge reflects this distinction.
Can I get alerted when a site goes down?
Yes. You can configure email or webhook alerts for down and recovery events, scoped to individual sites or the whole fleet. Repeated alerts are suppressed while a site stays down to prevent notification spam.
How far back does the response-time history go?
WPMgr stores response-time data at 7, 30, and 90 day horizons. Per-site detail pages show all three views. The fleet uptime page shows the aggregated status matrix and incident history across all sites.
Are TLS certificates monitored automatically?
Yes. WPMgr tracks the expiry date for each site's TLS certificate and surfaces an expiry warning in the dashboard with a configurable early-warning window.
Run your whole fleet from one dashboard.
Free and open source. No per-site fee. The full release is on GitHub.