Uptime Monitoring

How Uptime Monitoring Works

StatusDude sends HTTP or TCP requests to your endpoints at regular intervals from cloud workers deployed across three regions: Europe, North America, and Asia. Each check measures response time, validates the HTTP status code, and verifies that your service is responding correctly.

When a check fails, the system automatically triggers a verification check from a different region. This multi-region verification prevents false positives caused by transient network issues, CDN routing problems, or regional DNS failures. Only confirmed outages generate alerts.

All results are streamed through a high-throughput processing pipeline. Results are batched, analyzed for state changes (UP to DOWN or DOWN to UP), and stored with full timing data. This architecture handles thousands of monitors without breaking a sweat.

HTTP Monitoring

HTTP monitors check your web endpoints by making real HTTP requests. StatusDude validates the response status code, measures the full request-response cycle time, and can extract SSL certificate details for expiry tracking.

• Configurable expected status codes (200, 201, 301, etc.)
• Response time tracking with historical graphs
• Automatic SSL certificate expiry detection
• Support for custom headers and authentication
• Timeout configuration per monitor

TCP Port Monitoring

TCP monitors verify that a host is accepting connections on a specific port. This is useful for monitoring databases, mail servers, game servers, or any TCP-based service where HTTP checks don't apply.

• Check any TCP port on any host
• Connection timeout measurement
• Ideal for databases (PostgreSQL, MySQL, Redis)
• Monitor SMTP, FTP, SSH, and custom services

Heartbeat Monitoring

Heartbeat monitors work in reverse: instead of StatusDude checking your service, your service sends periodic pings to a unique webhook URL. If StatusDude doesn't receive a ping within the expected interval plus a configurable grace period, an alert is triggered.

Heartbeat monitoring is perfect for cron jobs, scheduled tasks, backup scripts, and any process that runs on a schedule. If your backup job should run every hour, set a heartbeat monitor with a 60-minute interval and a 5-minute grace period. If the job fails to report in, you'll know immediately.

Flexible Check Intervals

Choose check intervals from 30 seconds to 10 minutes depending on how critical the monitored service is. Production APIs might warrant 30-second checks, while internal tools could use 5-minute intervals. Different tiers unlock different minimum intervals, so you can balance monitoring frequency with your plan.

Alerting & Notifications

StatusDude supports multiple notification channels that can be configured per monitor. Each channel has an independent cooldown period to prevent alert fatigue during prolonged outages.

• Email notifications with incident details
• Slack integration via incoming webhooks
• Custom webhook delivery for automation
• Browser push notifications for real-time alerts
• Configurable cooldown periods per channel