February 3rd, 2025

Improved

TCP Checks—Now in open beta with new features!

TCP checks are now available in open beta for all plan types! We’ve made several updates that we’re excited to share.

With TCP checks, you can monitor infrastructure components like databases, message queues, and mail servers—ensuring they stay connected and reliable.

For details on usage, reporting, and billing, check out the TCP checks documentation. You can also configure TCP checks via the CLI and Terraform provider—learn more in our developer docs.

✨ What’s new?

Alongside private location support (available from Checkly agent v4.0.3) and an IP family selector, we’ve rolled out several new capabilities for TCP checks:

  • Monitoring as Code (MaC): Define and manage TCP checks via the CLI (v4.19.1) and Terraform provider (v1.9.0). Support for the Pulumi provider is currently in development.

  • Assertions: Validate ‘response time‘ and expected ‘response data‘ to ensure your checks meet performance expectations.

  • Data exchange: Send data to the target port and define assertions for expected responses, ensuring your service is both reachable and functioning correctly.

  • “This request should fail” option: Mark TCP checks as successful when a connection fails, making it easy to test intentional unreachability. Once enabled:

    • Failed connections (e.g. timeouts or connection refusals) will be marked as passed.

    • Failing assertions will still cause the check to fail, regardless of connection status.

    • Successful connections will be marked as passed as usual.

✨ What’s next?

We’re continuing to improve TCP checks and will keep you updated on our progress!

Is there anything else you’d like to see? We’d love your feedback—Share your thoughts on our feedback hub or connect with us in the Checkly community Slack.

Happy monitoring!