Monitoring, incident history, and service communication
Know what failed. See what happened next.
Monitor websites, HTTP APIs, SSL certificates, and scheduled jobs. Investigate retained history, coordinate planned maintenance, and keep service health clear.
Start with a public URL and interval. Add methods, headers, request bodies, expected status codes, and response-content rules when the effective plan includes advanced HTTP monitoring.
Give each scheduled process a private heartbeat URL. PingBeacons records every arrival and identifies a missed execution when the expected check-in does not arrive.
Read a week—or the year—as one operational record.
Compare all monitors or one. Move between week, month, year, and custom ranges across uptime, checks, failures, incidents, response time, trend charts, and the uptime calendar.
Maintenance windows scope a start, end, and selected monitors. Active windows suppress their ordinary scheduled-check path and can appear publicly as maintenance.
A public answer built from selected internal truth.
Publish selected components with safe incident information and maintenance state. Visitors can explicitly confirm email subscriptions for future incident updates.
Switch context without mixing monitors, status pages, alerts, billing, or history. Invite Owner, Admin, Operator, and Viewer roles with backend-enforced permissions and audit activity.