Siteligent monitors your websites using two separate layers. One checks whether your website is actually reachable by visitors, while the other checks whether Siteligent can still communicate with the Siteligent Connector installed on your WordPress site.
This distinction is important because a website can be completely accessible to visitors while its management connection is offline. In that situation, the website may continue to load normally, but Siteligent may no longer be able to perform tasks such as backups, synchronization, or management operations.
Two Layers of Website Monitoring
Siteligent runs two monitoring systems in parallel.
Layer 1: Uptime Monitoring
The first layer checks whether your website is available over HTTPS.
The uptime monitor checks your website at regular intervals.
The typical monitoring interval is every 5 minutes (300 seconds), although this can be adjusted to as frequently as every 1 minute for sites where availability is particularly important.
What Uptime Monitoring Measures
The uptime layer tracks:
Server availability
HTTP status codes
Response time
Website reachability
Siteligent also tracks response-time information based on the monitoring checks, allowing you to see whether your website is responding quickly or becoming slower over time.
When Is a Site Considered Down?
Siteligent records a downtime event when the monitoring system cannot successfully reach the website.
This can happen when:
The server returns a 5xx server error
The request receives a 4xx response caused by a client or security block
The server fails to respond within the connection timeout
When the monitoring system detects a qualifying outage, Siteligent records the downtime event so it can be investigated.
Layer 2: Connector Connection Monitoring
The second monitoring layer checks something different: whether Siteligent can communicate with the Siteligent Connector on your WordPress site.
A website might still be loading perfectly for visitors while this connection is unavailable.
For example, the Connector could have been deactivated, a firewall could have started blocking Siteligent requests, or a security plugin could have restricted REST API access. The website would still appear online to visitors, but Siteligent would be unable to communicate with it.
How Connector Monitoring Works
The Connector status checker runs automatically at:
:00 of every hour
:30 of every hour
This means Siteligent checks the management connection every 30 minutes.
The checker connects to the authenticated Siteligent REST API namespace:
/wp-json/siteligent/v1/
It verifies that the Siteligent Connector is:
Active
Updated
Properly authenticated
Reachable by Siteligent's servers
Protection Against Temporary Connection Problems
A single failed check doesn't immediately mean that your site is disconnected.
Temporary network problems, hosting restarts, or short-lived outages can cause an individual request to fail even though the site is otherwise healthy.
To avoid unnecessary alerts, Siteligent uses Consecutive Failure Protection.
A site is marked as Disconnected only after two consecutive failed connection checks.
Because the checks occur 30 minutes apart, two consecutive failures represent approximately 60 minutes of sustained connection failure before the site is flagged and an alert is generated.
This helps prevent repeated alerts caused by brief network interruptions.
SSL Certificate Monitoring
Siteligent also monitors your site's SSL certificate separately from its normal uptime checks.
The SSL monitor checks:
Certificate validity
Certificate issuer
Certificate expiration
Siteligent generates a warning when the certificate has fewer than 14 days remaining before expiration.
This gives you time to renew the certificate before visitors begin receiving browser security warnings.
Domain Expiration Monitoring
Siteligent also checks your domain registration information using domain registry/WHOIS data.
The domain expiry monitor tracks the domain's renewal date and sends warnings:
30 days before expiration
7 days before expiration
Keeping these alerts enabled can help prevent an otherwise healthy website from becoming inaccessible because its domain registration expired.
Understanding Website Statuses
Your site's status badge in the Siteligent Dashboard reflects the current health and connection state.
Up: Up indicates that the website is online and responding normally. The site is reachable, its response is within expected limits, and the Siteligent Connector is authenticated and available for management operations.
Down: Down indicates a website availability problem. The uptime monitoring system cannot successfully reach the site, or the server is returning an error such as:
500
502
503
This generally indicates a server-side or availability problem that should be investigated.
Disconnected: Disconnected means the website itself may still be accessible, but Siteligent cannot communicate with its Connector.
Common causes include:
The Siteligent Connector was deactivated
A firewall started blocking Siteligent
A security plugin restricted REST API access
The Connector authentication failed
A hosting or network configuration changed
Visitors may still be able to browse the website normally while the management connection remains unavailable.
Paused: Paused means monitoring has been intentionally suspended. Background uptime heartbeats and status checks are paused while the site is in this state.
Unknown: Unknown generally indicates that the site has recently been added and hasn't completed its initial scheduled status check yet.
Down vs. Disconnected
One of the most important distinctions to understand is the difference between Down and Disconnected.
Status | What it means |
Up | Website is reachable and the Connector is available |
Down | Website availability or server response is failing |
Disconnected | Website may be online, but Siteligent cannot communicate with the Connector |
Paused | Monitoring has been suspended |
Unknown | Initial monitoring check hasn't completed |
For example, if you can open your website normally in a browser but Siteligent shows Disconnected, don't immediately assume the website itself is down. Check the Connector, firewall, and security-plugin configuration first.
If Siteligent shows Down, investigate the website's server, hosting environment, network, and HTTP response instead.