TCP connection checks
Verify that the selected port accepts a connection from a probe region. Use it for public listeners that are not covered by an HTTP check.
An open port.
A useful signal.
Check whether a public TCP service accepts connections. Watch mail, SSH, database gateways and other listeners that need a more focused check than a website monitor.
Part of your Upty workspace · One workspace. Every signal.
RESPONSE TIME38 ms
- Target
- mail.example.com
- TCP port
- 587
- Connection
- Accepted
- Connect time
- 38 ms
Some of the services you rely on do not speak HTTP. Port monitoring opens a TCP connection to a host and port, giving you a straightforward availability signal for a service listener.
Keep connection timing and status history beside your other monitors. An open port is a starting point for reliability checks; combine it with application-level monitoring when you also need to verify the response.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
Choose the actual service
Specify the host or IP and a port from 1 to 65535. Separate monitors for separate listeners make it clear which service has become unreachable.
Connection timing
Review DNS lookup, TCP connection and total connection time in the latest result. Timing detail helps distinguish slow setup from a refused connection.
Check from selected regions
Use the regions relevant to the service. Comparing their results can help identify firewall rules or path differences that affect only part of your audience.
A history of availability
Follow status, uptime and response time across checks. The historical view gives useful context when intermittent connection problems are difficult to reproduce.
Alerts on changes
Choose your failure policy and destinations. Notify the team when a listener goes down and when it begins accepting connections again.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Mail services
Check that the expected SMTP or IMAP listener can be reached. The connection check is useful alongside the operational checks you use to verify message delivery.
Remote access gateways
Watch public SSH or other controlled entry points. Keep your existing access policy; a monitor should fit the service’s intended exposure.
Custom TCP services
Monitor non-HTTP listeners such as a game service or integration gateway. Use a separate application check when the protocol response itself must be validated.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Choose Port and enter a hostname or public IP address together with the TCP port number.
- 02
Configure the check.
Choose the check regions and interval. Confirm that the service is intended to accept those connections under your existing access policy.
- 03
Follow the signal.
Set alert channels and the consecutive failure setting. Compare connection details when a result differs between regions.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationDoes this validate the service protocol?+
No. A successful check means the TCP connection was accepted. It does not prove that a database query, mail delivery or application-level operation will succeed.
Are UDP ports supported?+
This monitor checks TCP connections. It is not a UDP protocol check.
Should I expose a private database for monitoring?+
No. Keep private services private. Public probe checks should only target services that are already intended to be reachable under your access policy.
Why can I connect but a probe cannot?+
The service may restrict source networks or a firewall may reject probe traffic. Compare the regional results and your access rules before changing the monitor.
Are port monitors available on every plan?+
Port monitors have a plan-specific allowance. The monitor form and your billing page show the capacity available to your workspace.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring port monitoring into your workspace.