Documentation
Complete guide to setting up website monitoring with PingZen. API documentation, code examples, and best practices.
Incident Management
PingZen automatically creates incidents when monitors go DOWN and resolves them when they recover. You can update statuses, add comments, and track the full timeline.
Auto Detection
Incidents are automatically created when a monitor goes DOWN after confirmation (default: 3 consecutive failures).
Auto Resolution
Incidents are automatically resolved when the monitor recovers.
Event Timeline
Each incident contains a complete event history with timestamps.
Maintenance Exclusion
Incidents are not auto-created during scheduled maintenance windows.
Incident Statuses
Investigating
Initial state — looking into the issue to determine root cause.
Identified
Root cause identified, working on a fix.
Monitoring
Fix applied, monitoring for stability before closing.
Resolved
Incident is closed, monitor has recovered.
Filtering
Filter incidents by status (ongoing/resolved) and time range (24h, 7 days, 30 days).
Incidents API
Manage incidents programmatically via REST API.
List incidents with pagination and filters
Get incident details with timeline
Update status or add comment
Add a status update to an incident
Manually resolve an incident
Common Questions
What protocols can I monitor?
PingZen supports 23 protocols: HTTP/HTTPS, WebSocket (WS/WSS), TCP, UDP, ICMP Ping, gRPC, DNS, WHOIS, SSL certificates, Email (SMTP/IMAP/POP3), FTP/FTPS, DNSBL, PageSpeed, SOCKS5, MTProxy, API Check, and Transaction. You can monitor websites, APIs, servers, databases, and any network service.
How fast can I get alerts?
Telegram alerts are delivered within 1-2 seconds of detection. Slack and Discord notifications arrive almost instantly. You can configure multiple alert channels for redundancy.
Can I organize monitors by project?
Yes! PingZen supports workspaces, which let you organize monitors by project, environment, or team. Each workspace can have its own alert configurations and team members.
Is there an API for automation?
Absolutely. PingZen provides a full REST API with OpenAPI documentation. You can create, update, and delete monitors programmatically.
How do status pages work?
Status pages are public, branded pages showing your services' uptime. You can display real-time status and allow customers to subscribe for updates.
What happens if I reach my monitor limit?
We'll notify you when approaching your limit. You can pause some monitors or contact us for increased capacity. We never stop monitoring without warning, ensuring your critical services stay protected.
Ready to stop missing downtime?
Join thousands of teams who trust PingZen. Setup takes 30 seconds.