Uptime & SSL Monitors
Learn how to customize ping configurations, set expected HTTP status codes, check keyword bodies, and track certificate expirations.
How to Add a Monitor
To monitor a website or API, log in to your Pingzo dashboard and follow these configuration steps:
- Friendly Name: Give the check a clear name (e.g.
Main StorefrontorAuthentication API). - Endpoint URL: Enter the full address, starting with
http://orhttps://. - Check Interval: Choose how frequently Pingzo will run the check.
- Free Plan: 15 minutes.
- Starter Plan: 5 minutes.
- Pro Plan: 2 minutes.
- Agency Plan: 1 minute.
Advanced Assertions & Configurations
Expected Status Codes
By default, Pingzo expects a 200 OK response. If your website has a redirect block, change this code to 301 or 302 so that Pingzo knows the redirect is intentional and doesn't trigger false downtime alerts.
Keyword Matching
Ensure your database is active by asserting that a specific term exists in the HTML body response (e.g., "database_status": "healthy" or a word like Welcome). If the keyword isn't found in the payload, the check is flagged as Degraded.
Check Timeout (ms)
Define the max duration (in milliseconds) Pingzo should wait for your server to respond. The default is 10,000ms (10 seconds). Slow responses exceeding this threshold trigger a timeout warning.
SSL Expiry Warnings
Daily security checks trace target SSL certificate validity. For paid tiers, alert emails and WhatsApp texts are sent **30 days, 14 days, and 7 days** before certificate expiration so you can renew it.
Domain Expiry Alerts
We run smart HTTPS RDAP queries to trace your domain registration status. Alerts are fired at **30 days, 14 days, 7 days, 1 day, and 0 days** before expiration. The check frequency automatically accelerates to daily when close to expiry.
DNS Change Detection
We resolve your domain's DNS mapping daily (A, AAAA, MX, TXT, NS, CNAME) and compare against cached results. If any change is detected, we alert you via your configured channels to guard against hijacking.
Cron & Heartbeat Monitoring (Pro & Agency)
For background workers, cron jobs, database backups, and scheduled scripts that do not have a public URL, Pingzo offers push-based Heartbeat Monitoring.
How It Works:
- Unique Ping Endpoint: When you add a Heartbeat monitor, Pingzo generates a unique ping URL (e.g.,
https://www.pingzoapp.com/api/ping/cmq-unique-id). - Integrate with Cron/Scripts: Make a simple
GETrequest to this URL at the end of your script or background task. - Grace Period: Set a grace time (in minutes) to prevent false alerts if your task runs slightly slower than usual.
- WhatsApp Downtime Alert: If Pingzo doesn't receive a heartbeat within your configured interval + grace period, it instantly sends an alert to your WhatsApp and other configured channels.
Advanced Feature: Custom Error Reporting
You can report errors directly from your application script to trigger instant alerts without waiting for the monitor to become overdue. Simply append ?status=fail&error=YourErrorMessage to your ping URL:
curl -G "https://www.pingzoapp.com/api/ping/your-secret-id" \ --data-urlencode "status=fail" \ --data-urlencode "error=DatabaseConnectionFailed"
Official Node.js SDK
Integrate heartbeats natively into Node.js application scripts using the official SDK:
npm install @pingzoapp/sdk
const Pingzo = require('@pingzoapp/sdk');
const pingzo = new Pingzo('your-secret-id');
// Report success
await pingzo.ping();
// Report failure
await pingzo.ping('fail', 'Out of Memory');Rate Limiting
To prevent performance degradation, success pings are rate-limited to **once every 30 seconds**. Pings arriving faster will receive an HTTP 429 Too Many Requests response, but rest assured, this rate limiting will **not** count as downtime or mess up your history checks.
Double-Check / Retry Policy
To prevent false positive alerts caused by brief network hiccups, Pingzo will retry checks 3 times from different server zones before triggering a downtime incident and alert notifications.