Monitoring
Solutions
Resources
Free Tools
Pricing
Products / Server monitoring / TCP Server Monitoring
Any TCP port

TCP Server Monitoring

Check that any TCP service accepts connections on its port, and optionally send a string and verify the reply. From databases to game servers, if it listens on TCP you can watch it.

9 check locations1–120 min check interval8 alert channels10 monitors free
db.example.com:5432 · TCP
Portopen
String sentPING
String expectedmatched
Response time41 ms
Illustrative example of a check result.

The universal monitor

Not every service speaks HTTP. Databases, message brokers, custom daemons and game servers all listen on raw TCP ports. If the port stops accepting connections, the service is effectively down.

A TCP monitor tests exactly that, and can go one step further: send a string and require a specific reply to prove the service is actually answering, not only listening.

What Upzilla checks

Every check is stored in a full log, so you can see exactly when and how something changed.

Port reachability

Confirms the port accepts a connection.

Send and expect

Send a string and require a string back for a deeper check.

Any service

PostgreSQL, Redis, MQTT, SMTP, custom protocols.

Multiple locations

Test from different regions and networks.

How it works

From sign-up to your first alert in a few minutes.

Enter host and port

Any TCP service.

Optional send and expect

Prove the service answers correctly.

Alerts

Get notified on failed connections.

Settings you can control

Sensible defaults get you started; every option below can be tuned per monitor.

SettingWhat it does
Domain / IPThe server to monitor.
PortThe TCP port.
String to sendData sent after connecting.
String to expectText the response must contain.
FrequencyHow often the check runs: 1 to 120 minutes. The Free plan checks from every 15 minutes; Premium from every minute.
LocationsRun the check from one or several of 9 locations: Spain, France, United Kingdom, USA (New York, Los Angeles), Australia, Singapore, Japan and Germany.
NotificationsPick any of your pre-configured alert channels: e-mail, SMS, Telegram, Slack, Messenger, voice call, webhooks and more.
Status pageMake the statistics of this monitor public or private.
TagsGroup monitors with tags to keep large accounts tidy.
IP versionForce IPv4, IPv6, or let Upzilla use whichever is available.
Full setup guide in the documentation →

Common use cases

Databases and caches

PostgreSQL, Redis, MongoDB and more.

Message brokers

RabbitMQ, MQTT and Kafka ports.

Game servers

Check that players can connect.

Custom daemons

Anything with a TCP listener.

Alerts where your team already is

Create as many notification methods as you like, even on the free plan.

Slack
Telegram
Telegram group
Facebook Messenger
Email
SMS
Voice call
Webhooks

Related monitors and tools

UDP Server MonitoringPing MonitoringSSH MonitoringMySQL MonitoringTCP/UDP port numbers (free tool) →

Questions about tcp server monitoring

Which ports can I monitor?

Any TCP port. Our port numbers list helps you find the right one for a service.

What does String to expect do?

It requires the server’s reply to contain specific text, which proves the service, not just the port, is working.

TCP or HTTP monitor?

Use HTTP for web endpoints. Use TCP for everything else that speaks a raw TCP protocol.

Is it free?

Yes, within the 10 free monitors.

If it listens on TCP, Upzilla can watch it

No card required. 10 monitors of any type, free.

Create free account →