Everything you need to monitor with confidence.
Learn how to set up PingBeacons, monitor websites and APIs, track SSL certificates, watch scheduled jobs with heartbeats, and respond to incidents.
Start with the Getting Started guide. It walks you through creating your first monitor and understanding what happens when PingBeacons detects a problem.
Start here
PingBeacons monitors services that need to stay available and jobs that need to run on schedule. Choose the guide that matches what you want to monitor.
Getting started
Create your account, add your first monitor, and understand the PingBeacons dashboard.
Read guideWebsite monitoring
Monitor website availability, response times, outages, and recoveries.
Read guideAPI monitoring
Monitor API endpoints and quickly detect availability or response problems.
Read guideHeartbeat monitoring
Monitor cron jobs, backups, scheduled scripts, and other background tasks.
Read guideSSL monitoring
Keep track of SSL certificate validity and upcoming certificate expiry.
Read guideNotifications
Configure how PingBeacons alerts you about incidents, recoveries, and SSL expiry.
Read guideIncidents & history
Understand monitor checks, incident timelines, downtime, and recovery history.
Read guideSecurity
Learn how to safely handle heartbeat URLs, credentials, and monitoring endpoints.
Read guideMaintenance windows
Schedule planned periods when selected checks and alerts are suppressed.
Read guideStatus pages
Publish monitor health, customize eligible pages, and manage subscribers.
Read guideTeams and workspaces
Invite members, use roles, switch workspaces, and review audit activity.
Read guidePlans and billing
Understand live limits, paid checkout, pending upgrades, payments, and cancellation.
Read guideHow PingBeacons works
For website, API, and SSL monitors, PingBeacons performs the checks for you. Heartbeat monitoring works in the opposite direction: your scheduled job sends a signal to PingBeacons when it runs.
Create a monitor
Choose what you want to monitor and provide the required website, API, SSL, or heartbeat details.
PingBeacons watches it
Checks and heartbeats are recorded so you can see the latest status and monitoring history.
Problems become incidents
When a monitored service fails or an expected heartbeat is missed, PingBeacons can record the problem as an incident.
You receive an alert
Your notification preferences determine how PingBeacons keeps you informed about incidents, recoveries, and SSL expiry.
Recovery is tracked
When the service becomes healthy again, PingBeacons records the recovery so the incident history remains useful.
What can I monitor?
Websites
Check whether a website is responding and track response times, failures, incidents, and recoveries.
APIs
Watch API endpoints so availability problems can be detected without waiting for users to report them.
Scheduled jobs
Use heartbeat monitoring for cron jobs, backups, imports, reports, synchronization jobs, and scheduled scripts.
SSL certificates
Keep certificate validity and expiry visible so upcoming SSL expiry does not go unnoticed.
Quick heartbeat example
A heartbeat monitor gives you a unique URL. Call that URL after your scheduled job completes successfully.
curl -fsS "YOUR_HEARTBEAT_URL"For example, a daily backup cron job could use:
0 2 * * * /path/to/backup.sh && curl -fsS "YOUR_HEARTBEAT_URL"Do not commit a real heartbeat URL to a public Git repository or expose it in browser-side JavaScript. Anyone who knows the URL may be able to send a heartbeat to that monitor.
Recommended first setup
Add your main website
Start with the production website your users depend on most.
Add important API endpoints
Monitor APIs that are critical to login, checkout, application data, or other important workflows.
Monitor important scheduled jobs
Add heartbeat monitoring to backups and other jobs that could fail silently.
Review notification preferences
Make sure the alerts you care about are enabled before relying on your monitors in production.