Frequently Asked Questions
Uptime monitoring accurate to the second
Common Questions
Quick answers for setting up monitors, managing alerts, and reviewing your infrastructure status.
What counts as downtime?
Pulsely marks a monitor as down when it fails to return a successful HTTP 2xx/3xx status code or exceeds the configured response timeout (default 10 seconds). We also track TLS handshake failures, DNS resolution errors, and TCP connection resets. Partial outages where only one geographic probe fails are logged as degraded, not full downtime, unless you enable strict failover rules in your monitor settings.
How does the free tier work?
The Starter plan includes up to 3 active monitors, 1-minute check intervals, and email alerts for critical failures. You get a rolling 30-day history dashboard and standard TLS/DNS monitoring. If you add a fourth monitor or switch to 30-second intervals, you’ll be prompted to upgrade to the Pro plan at $12/month. No credit card is required to start, and you can downgrade anytime without losing your historical data.
Can I export my monitoring history?
Yes. Navigate to Reports > Export in your dashboard and select your date range. Pulsely generates CSV and JSON files containing timestamp, probe location, response time, status code, and error details. Enterprise users can also trigger automated S3 or Google Cloud Storage uploads via our REST API. Exports include SLA compliance percentages and are formatted for direct import into Datadog or Grafana.
Still need help?
Our engineering team responds to support tickets within 4 hours during business hours. For urgent production incidents, use the priority escalation channel.