HTTP / HTTPS
Reads the response code, response time, and SSL certificate expiry, and can require a keyword in the body. Interval, timeout, and retries are set per monitor.
HTTP, TCP, ICMP, and Heartbeat monitoring inside WHMCS, with incidents, alerts, and status pages. Licensing is commercial, and Status Page Pro plus Multi-Region are optional.
HTTP and HTTPS checks read the response code, the response time, and the SSL certificate expiry, and can require a keyword in the response body before the service counts as up.
TCP confirms that a port accepts a connection. ICMP ping measures reachability and round-trip time. Heartbeat waits for the service to call its own monitor URL, and raises an alert when that rhythm stops.
Every monitor has an interval, a timeout, a retry count, and a fail-streak threshold. The default interval is five minutes, so one failed attempt does not mark the service down.
Status pages are public, limited to the client area, or password-protected, with a logo, custom CSS, and section grouping. Status Page Pro adds a standalone status.php page and a custom domain.
An incident moves from Investigating to Identified, then Monitoring, then Resolved. Severity is Critical, Major, Minor, or Info, with timeline updates and the affected monitors attached.
Alerts leave by email, by webhook to Slack, Discord, or any HTTP endpoint, and by Telegram. An escalation rule opens another channel if the outage is still open after the number of minutes you set.
Four checks in core, and Multi-Region agents when that extension is licensed. Each monitor is one endpoint with its own interval, timeout, and fail streak.
Reads the response code, response time, and SSL certificate expiry, and can require a keyword in the body. Interval, timeout, and retries are set per monitor.
Opens the port and confirms it accepts a connection. Use it for mail, databases, and game services that have no HTTP path.
ICMP measures reachability and round-trip time. It tells you whether the host itself answers before you test the service on top of it.
The service calls the monitor URL. If no signal arrives inside the expected window, the monitor opens a down state even when the host is up.
The Multi-Region extension runs PHP or Python agents in other locations. Each agent sends a version handshake, and a result is stored against that region.
Real screens from Uptime Monitor 2: monitoring, incidents, status pages, and alerts.
Three views from the addon: the overview, the monitor list, and the HTTP/HTTPS check setup.
The incident log, status pages in the admin, and the public Status Page Pro front.
Notification channels, multi-region agents, and the license screen with the SRVUPTIM prefix.
A complete incident system and announcement bar for communicating outages with defined severity levels and progress states.
Investigating: the outage is published as soon as it is detected, and the root cause is still open. Severity is Critical, Major, Minor, or Info.
Critical · Major · Minor · InfoIdentified: the cause is known. The timeline update names what broke and which monitors are linked to the incident.
Linked monitorsMonitoring: the fix is in place and the team watches stability before closing. Subscribers stay notified until the state changes.
Markdown timelineResolved: the service is back, the incident closes, and it remains in history. An announcement bar can stay in Info, Warning, Danger, or Success until the expiry you set.
Official closeShow the live state of your services to visitors, clients, and subscribers, with active incidents, recent history, and optional email subscription.
A live dashboard with KPI cards for total monitors, up/down/paused counts, and recent incidents — backed by retention policies and system diagnostics.
Publish incidents with severity levels and state transitions, plus Markdown timeline updates.
Advance warning when an SSL certificate will expire within a configurable number of days.
Trigger additional channels if a service remains down for a defined number of minutes.
Pause alerts during maintenance without deleting the monitor or losing history.
Email alerts for page subscribers and admin-defined channels, plus webhook and Telegram support with configurable escalation rules.
WHMCS email to status-page subscribers and to the channels an administrator defines. Public subscription is optional per page.
A webhook to Slack, Discord, or any endpoint that accepts HTTP. The payload carries the monitor state so the other side can open a message or a ticket.
A Telegram bot for the on-call team. That channel stays separate from client email, so an operations alert is not the same message a subscriber receives.
Escalation opens a second channel only if the service is still down after the number of minutes you set, instead of paging every channel in the first minute.
A clear comparison between core addon capabilities, Status Page Pro, and the Multi-Region extension.
| Capability | Core | Status Page Pro | Multi-Region |
|---|---|---|---|
| HTTP / HTTPS / TCP / Ping / Heartbeat monitoring | |||
| Status pages (public · client · password) | |||
| Incident and announcement management | |||
| Email, webhook, and Telegram notifications | |||
| Standalone status page and custom domain | — | — | |
| Distributed checks from multiple regions | — | — |
300 seconds (5 minutes) per monitor, with a 10-second timeout and a configurable retry count before marking a service down.
Four core types: HTTP/HTTPS, TCP port, Ping (ICMP), and Heartbeat. Geographic coverage can be extended with the Multi-Region extension.
From the Uptime Monitor 2 panel, create a status page, choose access (public, clients only, or password-protected), and link monitors to it. With Status Page Pro you can also use a custom domain and a standalone page.
WHMCS 9.0 or later, PHP 8.2 or later with curl, json, mbstring, and openssl, MySQL 5.7+ or MariaDB 10.3+, a cron job running at least every 5 minutes, and an active ServLayer license key with the SRVUPTIM- prefix.
Yes, via the Multi-Region extension: distributed checks from multiple geographic locations using native agents or API providers such as UptimeRobot, StatusCake, BetterStack, and Asura.
WHMCS 9.0 or newer, PHP 8.2 or newer, the curl, json, mbstring, and openssl extensions, and MySQL 5.7 or MariaDB 10.3 at minimum. APCu is optional and speeds repeated reads. Tables are created on activation, with no manual SQL.
At least every five minutes, because the default check interval is five minutes. The engine runs from the AfterCronJob hook, and an external cron URL can be added. Scheduled checks pause if the license is not valid.
The key starts with SRVUPTIM. The Info tab shows subscription status, billing, and support-window expiry, and it can save, clear, refresh, or force-check the key. If the installed build falls outside the support window, the admin panel limits itself to that tab. Public status pages keep working.
Core includes the monitor types, incidents, alerts, and status pages inside WHMCS. Status Page Pro adds status.php and a custom domain. Multi-Region adds PHP or Python agents in other locations. Both extensions need core 2.5.0 or newer and a valid license.
Yes. A retention policy sets how long check results and the activity log are kept, and daily cleanup runs on its own. Tools can force-run every check, purge old results by hand, and show PHP, WHMCS, and cron diagnostics.
The amount comes from the WHMCS product linked on this page. Monthly and annual are both on the billing switcher, and the order button opens the cart on the cycle you select. A savings chip is withheld when the longer cycle is not actually cheaper.
The log is read from srv-uptimemonitor2.json. The current release shown is 2.5.6, and the version badge at the top opens this history.
No release notes available yet.
The linked product is Uptime Monitor2. Choose monthly or annual, and the order button follows that cycle. The two extensions are enabled later from the same license.