Ping & TCP Port Monitoring

Make sure your servers are actually reachable.

Ping and TCP port monitoring for servers, databases, email, and remote access—with latency charts, uptime history, and clear error insights.

Setup takes 30 seconds. No credit card required.

Why network monitoring matters

Uptime checks alone aren't enough. Sometimes your app is fine, but the network or port isn't reachable. Catch these silent failures before they become disasters.

Firewalls fail silently

A misconfigured firewall can block access without warning. Your service is up, but nobody can reach it.

Databases need ports

Your database might be running, but if port 5432 or 3306 isn't responding, your app is broken.

Network latency creeps up

Slow routing, overloaded switches, or VPN issues add latency that degrades user experience over time.

Services crash without logs

Redis, SSH, SMTP—these can all crash silently. Port monitoring catches it before your users do.

Everything you need at the network layer

Monitor your infrastructure from the network's point of view—without the complexity.

Ping monitoring

Check if hosts are reachable and measure network latency over time. Perfect for servers and infrastructure.

TCP port monitoring

Verify specific ports are open and responsive. Monitor databases, mail servers, SSH, Redis, and more.

24h sparkline overview

See latency and connection time trends at a glance with mini charts on each monitor card.

90-day uptime history

Visual calendar showing daily uptime percentages. Prove reliability and spot patterns over time.

Network Monitors Dashboard

All your network monitors in one view

Group all ping and TCP port monitors under a unified dashboard. Switch between views, filter by type, and spot issues instantly.

Tab filtering

Switch between All, Ping, and TCP Ports tabs to focus on what matters.

Mini sparkline charts

See latency or connection time trends over 24 hours directly on each card.

Key stats at a glance

Current value, average, max, and uptime percentage—all visible without clicking.

Fast visual overview

Understand your network health in seconds without digging through tables.

server.example.com
Ping
Current
24ms
Avg
27ms
Uptime
99.9%
db.example.com:5432
TCP
Current
18ms
Avg
21ms
Uptime
100%
server.example.com
Last checked 1 minute ago
RTT (Round-Trip Time) - 24h
24h ago Now
Current RTT
24ms
Avg RTT
27ms
Max RTT
89ms
30d Uptime
99.9%
Ping Monitor Detail

Understand network latency at a glance

Every ping monitor shows you exactly how fast (or slow) your network is performing. Spot instability, degradation, and routing issues before they impact users.

RTT chart

Visualize latency over time. See spikes, patterns, and trends instantly.

90-day uptime bar

Visual calendar showing daily uptime. Hover to see detailed stats per day.

Latency distribution

See percentiles in plain English: "Most pings under 30ms, worst-case 89ms this week."

Recent pings table

Browse every ping with timestamp, RTT, status, and TTL. Perfect for debugging.

TCP Port Monitor Detail

See exactly which services are responsive

TCP port monitoring goes deeper than ping. It verifies that specific services—databases, email, SSH—are actually accepting connections.

Connection time chart

Track how long it takes to establish a TCP connection over time.

Port info box

Shows host, IP address, port number, and protocol type at a glance.

Common use cases

Monitor databases (5432, 3306), mail (25, 465, 587), SSH (22), Redis (6379), and more.

Clear error messages

Connection refused, timeout, or host unreachable—know exactly what went wrong.

db.example.com:5432
PostgreSQL Database
Connection Time - 24h
Port Information
Host db.example.com
IP Address 192.168.1.10
Port 5432
Protocol TCP
Current
18ms
Avg
21ms

Setup in seconds

No complex configuration. Just fill in a few fields and start monitoring your network immediately.

Creating Ping monitors

Perfect for servers, VPN endpoints, routers, and any host you want to keep an eye on.

Host or IP address
server.example.com
Check interval
Every 5 minutes
Timeout
5 seconds
Latency threshold
100ms

Creating TCP monitors

Quick port selection for common services, or specify any custom port your services use.

Host
db.example.com
Port
5432 (PostgreSQL)
Check interval
Every 5 minutes
Connection timeout
10 seconds

Features that save you time

Built for teams managing multiple servers and services

Common ports reference

Handy reference grouping ports by category—web, email, database, remote access. Makes setup faster for non-network-experts.

PostgreSQL 5432
MySQL 3306
SSH 22

Bulk operations

Add multiple hosts at once or import CSV files. Ideal for agencies, MSPs, and teams managing many servers.

Import format
host,port,name
db1.com,5432,Database 1
db2.com,3306,Database 2

Clear error messages

No cryptic codes. Get clear explanations that help you fix problems fast.

Connection refused
Timeout after 10s
Host unreachable

Built for real infrastructure

Whether you're running databases, managing client servers, or monitoring home labs

SaaS teams

Monitor database ports, cache servers, message queues, and internal services that power your application.

  • Database connection health
  • Redis and cache availability
  • Message broker status

Agencies & MSPs

Monitor client infrastructure across email servers, databases, and remote access. Catch issues before clients call you.

  • Client server monitoring
  • Email infrastructure health
  • Bulk import for multiple clients

Makers & indie founders

Monitor your VPS, VPN connections, and home lab setups. Keep side projects healthy without complex tools.

  • VPS and server reachability
  • Home lab and NAS monitoring
  • Simple setup, zero complexity

Frequently asked questions

Everything you need to know about ping and TCP port monitoring

Ping monitoring checks if a host is reachable by sending ICMP echo requests and measuring the round-trip time (RTT). It's the simplest way to verify network connectivity and measure latency. If a host stops responding to pings, you know there's a network or server issue.
TCP port monitoring checks if a specific port on a host is open and accepting connections. It attempts to establish a TCP connection to verify the service is running and responsive. This is crucial for monitoring databases, email servers, SSH access, and any service that listens on a specific port.
It depends on your infrastructure. Common ones include: PostgreSQL (5432), MySQL (3306), Redis (6379), SMTP (25, 465, 587), SSH (22), RDP (3389), HTTP/HTTPS (80, 443). PerkyDash includes a reference guide with common port numbers grouped by service type to make selection easier.
Absolutely. TCP port monitoring is perfect for this. You can verify that your PostgreSQL, MySQL, MongoDB, or any database port is accepting connections. Same for email servers on ports 25, 465, or 587. If the port stops responding, you get alerted immediately.
Timeouts define how long to wait before considering a check failed (e.g., 5 seconds for ping, 10 seconds for TCP). Thresholds define when performance is degraded (e.g., latency over 100ms or connection time over 200ms). You set these based on what's acceptable for your service.
We detect timeouts (host not responding), connection refused (port closed or service not listening), host unreachable (network routing issues), DNS resolution failures, and latency threshold breaches. Each error comes with a clear explanation to help you diagnose the problem quickly.

See your infrastructure from the network's point of view.

Ping and port checks that catch connectivity issues before your users do.