StatusPage | Uptime Monitors & Public Status Page for WordPress

StatusPage | Uptime Monitors, a Public Status Page, Incidents & Alerts for WordPress

StatusPage watches your websites, APIs, ports, certificates and domains from your own WordPress, publishes a status page your customers can subscribe to, and tells your team the moment something breaks — by email, Slack, Discord, Telegram or a webhook. Incidents and maintenance have timelines, every week brings an SLA report as PDF, and other installs can act as probe locations so "down" really means down.

Key Features

• Seven monitor types: HTTP(S) with expected codes, keyword present / absent, response-time limit, custom headers (sealed) and HEAD / GET / POST; TCP port; ping (or a labelled TCP probe where ICMP is not allowed); SSL certificate expiry; domain expiry via RDAP
• Intervals from 1 to 60 minutes, timeouts, retries, "alert after N failed checks", private monitors; checks from WP-Cron or from real cron through a keyed URL
• Locations: this server plus probe peers (other StatusPage installs running your checks over REST); a monitor is down only when N locations agree
• Public status page as a shortcode or block: overall state, grouped components, 90-day uptime bars with daily tooltips, response-time sparklines, open incidents and maintenance, history, optional password, auto-refresh
• Incidents with investigating / identified / monitoring / resolved and a timeline; maintenance windows that pause alerts; automatic incidents when a monitor goes down, resolved on recovery
• Subscribers: double opt-in form on the page, unsubscribe in every notice, admin import and CSV export; PushPress in-app notices when installed
• Alerts to email, PushPress, Slack, Discord, Telegram, a signed JSON webhook and an SMS-gateway webhook, per monitor, with cooldown and recovery notices
• Dependency groups: when a parent is down its children show degraded and stay quiet
• Weekly SLA report by email with a PDF (uptime, average response, checks, outages, incidents) and CSV downloads; SVG status badges per monitor or for the whole page
• REST statuspage/v1 (status, incidents, monitors, check, probe) with an API token for CI; wp statuspage list|check|incident|report|subscribers; Site Health check

How a Check Becomes an Incident

1. A monitor fails its check; retries run first, then it must fail N times in a row
2. With probe peers, the other locations must agree before it counts as down
3. An incident opens by itself, subscribers and your alert channels are told (once, with a cooldown)
4. When checks pass again the incident resolves and a recovery notice goes out

Installation

1. Download the zip from your Library
2. In wp-admin go to Plugins › Add New › Upload Plugin, choose the zip and activate it
3. A new menu entry appears in the admin sidebar; open it
4. StatusPage › Monitors: add your sites; Page: create the public page in one click; Settings: copy the cron URL into a real crontab for exact intervals

Requirements

• WordPress 6.0 or newer (tested up to 7.0)
• PHP 8.0 or newer
• Outgoing HTTPS from the server for HTTP, SSL and RDAP checks
• Optional: a real cron job (every minute) for exact intervals

What You Get

• StatusPage 1.0.0 for WordPress (statuspage-1.0.0.zip)
• Full, readable PHP and JavaScript source, no obfuscation
• Updates for the term of your licence

Works With

Part of the Alpha WordPress line, built with one admin kit; PushPress delivers its notices in-app: PushPress, ServerPulse, MailDoctor, SiteStats, SecureShield, AlphaLogin.

The screenshots show the plugin on our demo site with sample data.