Billing & Invoicing
Details on Pro vs. Enterprise tiers, prorated upgrades, and annual discount structures.
FAQ - Common Questions
Real-time infrastructure monitoring for DevOps
Browse by Topic
Categories
Jump directly to the information you need regarding account management, API constraints, notification routing, and historical metrics storage.
Technical Limits
API rate thresholds, concurrent monitor caps, and payload size restrictions for webhook endpoints.
Alerting Logic
Downtime confirmation windows, escalation paths, and false-positive suppression rules.
Data Retention Policies
Historical uptime log storage durations, metric granularity, and export compliance standards.
Frequently Asked
Questions
Detailed answers to the most common inquiries from our engineering and operations teams.
How are overage charges calculated when I exceed my 500 monitor limit on the Pro plan?
StatusPulse bills overages at a flat rate of $0.12 per additional monitor per month. Charges are applied in real-time and appear on your next monthly invoice under the "Usage Overage" line item.
What is the default check interval for HTTP and ICMP monitors?
Standard HTTP and TCP monitors run at 60-second intervals. ICMP (ping) checks execute every 30 seconds. Enterprise customers can configure custom intervals down to 15 seconds via the REST API.
How does the downtime confirmation window prevent false alerts?
By default, StatusPulse requires two consecutive failed checks from geographically distributed nodes (e.g., Ashburn VA and Frankfurt DE) before triggering an incident. This eliminates transient network blips from spamming your Slack or PagerDuty channels.
Can I export raw uptime logs for compliance audits?
Yes. You can export CSV or JSON datasets covering the last 18 months directly from the Dashboard. Logs include timestamp, response code, latency in milliseconds, and originating check node.
What happens to my historical data if I downgrade from Enterprise to Starter?
Downgrades preserve your existing monitor configurations, but historical metrics older than 30 days are archived and become read-only. Real-time monitoring continues uninterrupted for up to 25 active endpoints.
How do I configure escalation policies for critical production outages?
Navigate to Alerting > Routing Rules. You can set time-based triggers (e.g., 5 minutes unresolved) to automatically route SMS and voice calls to secondary on-call engineers after the primary responder is notified.