We’re excited to announce that TCP checks are now fully available in Checkly across all plan types! After a successful beta phase, we’ve expanded functionality, improved documentation, and refined features to make TCP checks a reliable tool for monitoring your infrastructure.

TCP checks allow you to monitor critical infrastructure like databases, messaging queues or mail servers, ensuring they are reachable and responsive. Simply specify a hostname and TCP port to start monitoring.

🔎 Example Use Cases

• Mail servers (e.g. mail.example.org:993): Ensure your mail server is online and accepting IMAPS connections. Set assertions on the response time to spot slowdowns and provide reliable email services for your users.

• Custom TCP Services (e.g. service.example.org:5000): Monitor internal services that use custom TCP-based protocols. Send a simple command like ‘HEALTHCHECK‘ and assert that the response contains ‘OK‘ to verify that the service is running and responsive.

• Firewalls (e.g. firewall-protected.example.org:8080): Confirm firewall rules are correctly applied by using the “should fail” option. If a port is intentionally blocked, this will mark the check as passed when the connection fails (e.g. due to a timeout or refusal).

🚀 Get started with TCP Checks

Check out the TCP checks documentation to get started and learn more about usage, reporting and billing. TCP checks are fully integrated into Checkly’s Monitoring as Code (MaC) workflows and available in the CLI starting v4.19.1.

The Terraform provider supports TCP checks from v1.9.0, and the Pulumi provider from v2.0.0.

📌 Pricing & Billing

TCP checks are billed at $2 per 10k runs. They share the same quota as API checks, meaning they are included in your existing API check allocation. For more details on individual plan types, visit our pricing page.

💬 Connect with us

Got feedback or questions? We’d love to hear from you! Share your thoughts on our feedback hub or join the Checkly community Slack.

Happy monitoring!