Port Monitoring (TCP) Features
Database Monitoring
Monitor MySQL (3306), PostgreSQL (5432), MongoDB (27017), Redis (6379), and any database service.
Mail Server Monitoring
Track SMTP (25, 587), IMAP (143, 993), POP3 (110, 995). Ensure email delivery works 24/7.
SSH & Remote Access
Monitor SSH (22), RDP (3389), VNC (5900). Know instantly when remote access goes down.
Custom Services
Monitor any TCP service on any port (1-65535). Game servers, APIs, microservices, anything.
Connection Time Tracking
Measure TCP handshake time. Detect slow connections before they timeout.
Multi-Region Checks
Test connectivity from 25+ locations. Find regional routing or firewall issues.
How Port Monitoring (TCP) Works
Enter Host & Port
Specify hostname/IP and port number (e.g., db.example.com:5432).
Set Timeout
Configure connection timeout (default: 10 seconds). Lower for fast services, higher for slow ones.
Get Alerts
Receive instant notifications when ports become unreachable or connections timeout.
Who Uses Port Monitoring (TCP)?
Database Administrators
Monitor all database servers from one dashboard. PostgreSQL, MySQL, MongoDB, Redis—track them all.
Game Server Operators
Monitor Minecraft, CS:GO, Rust, ARK, and any game server. Know instantly when servers go offline.
DevOps Teams
Track microservices, APIs, message queues (RabbitMQ, Kafka). Ensure distributed systems stay healthy.
Email Administrators
Monitor SMTP, IMAP, POP3 across all mail servers. Prevent email delivery failures.
Port Monitoring (TCP) FAQ
What ports can you monitor?
Any TCP port from 1 to 65535. Common examples: SSH (22), HTTP (80), HTTPS (443), MySQL (3306), PostgreSQL (5432), MongoDB (27017), Redis (6379), SMTP (25, 587).
Can you test specific protocols (like SSH or MySQL)?
TCP monitoring tests basic connectivity only (can we connect?). For protocol-specific checks (can we login? query database?), contact us about custom monitoring.
What if my service is behind a firewall?
Port monitoring won't work if your firewall blocks connections from our IPs. You'll need to whitelist our monitoring locations or use internal agent monitoring.
How often are ports checked?
Free plan: every 5 minutes. Pro: every 1 minute. Business/Enterprise: every 1 minute or 30 seconds.
What counts as 'down' for port monitoring?
Connection refused, connection timeout, or TCP handshake failure. We don't inspect application-level responses—just TCP connectivity.
Can you monitor UDP ports?
Currently no—only TCP ports. UDP monitoring is planned for future release. Contact us if you need it urgently.
Do you support IPv6?
Yes! Monitor both IPv4 and IPv6 TCP ports from our dual-stack monitoring locations.