How Uptime Snooper Keeps Your Site Online — Features & Pricing Explained

Getting Started with Uptime Snooper: Setup, Alerts, and Best Practices

What Uptime Snooper does

Uptime Snooper continuously checks your website, API, or service endpoints and notifies you when they become unreachable or slow. Use it to detect outages, verify SLAs, and reduce mean time to repair.

Quick setup (5 steps)

1. Create an account and verify your email.
2. Add a monitor: enter the target URL or IP, select HTTP(S)/TCP/ICMP, set the expected response code or port.
3. Choose check frequency (default: 1–5 minutes).
4. Configure notification channels (email, SMS, webhook, Slack).
5. Enable alert escalation and on-call rotation if available.

Recommended monitor settings

• Check frequency: 1–5 minutes for public services; 5–15 minutes for noncritical internal services.
• Timeout: 5–10 seconds for web endpoints; reduce for APIs with strict SLAs.
• Retry policy: 1–2 retries before triggering a full alert to avoid false positives.
• Geographical probes: enable probes from multiple regions to detect localized network issues.
• SSL/TLS validation: keep enabled to detect certificate expiry or misconfiguration.

Alert configuration best practices

• Use multiple channels: combine email + Slack + webhook for redundancy.
• Create concise alert messages: include monitor name, region, error code, timestamp, and a direct link to runbooks or incident page.
• Set severity levels: informational (latency increase), warning (partial degradation), critical (down).
• Escalation policy: notify on-call immediately for critical alerts, escalate to team leads if unresolved after defined time (e.g., 15–30 minutes).
• Silence/maintenance windows: schedule for planned deployments to avoid alert noise.

Incident response workflow

1. Triage: confirm the alert from the dashboard and probe logs (determine scope and affected regions).
2. Check recent deploys and status pages of upstream providers.
3. Follow the runbook: restart services, rollback deployments, or open tickets as required.
4. Communicate: update stakeholders via status page and team channels.
5. Post-incident: run a blameless postmortem and add preventive actions to monitoring rules.

Reducing false positives

• Require a small number of consecutive failures before firing critical alerts.
• Monitor both synthetic checks and real-user metrics (RUM) to correlate user impact.
• Use health-check endpoints that validate downstream dependencies rather than generic homepages.
• Whitelist maintenance IPs and schedule expected downtime.

Performance and uptime metrics to track

• Uptime percentage (30/90/365-day windows)
• Mean time to detect (MTTD) and mean time to restore (MTTR)
• Average response latency and p95/p99 latency
• Number of incidents and incident duration distribution

Security and privacy tips

• Store notification webhooks and API keys in a secrets manager.
• Use least-privilege API tokens for integrations.
• Restrict monitor creation and alerting configuration to trusted roles.

Checklist before you finish

• Monitors created for all critical endpoints.
• Alerts tested with a simulated outage.
• Escalation and on-call rotations configured.
• Runbooks linked in alert messages.
• Status page and stakeholder notification processes set.

Follow these steps and best practices to get reliable, actionable uptime alerts from Uptime Snooper while minimizing noise and improving incident response.