Features /
Monitoring
Port monitoring for any TCP service
If a service listens on a TCP port, FrogStatus can check that the port accepts connections. It works for databases, mail servers, SSH and anything else that is not a web page.
14 days, no commitment. Cancel any time.
How it works
- 1
Enter host and port
For example mail.example.com:25 or db.example.com:5432.
- 2
Set the interval
Pick how often to connect, within the minimum of your plan.
- 3
Choose the alert
Select the channels. The alert can repeat while the port stays closed.
What you get
Any TCP service
SMTP, IMAP, PostgreSQL, MySQL, Redis, SSH: if it opens a TCP connection, it can be checked.
Connection time
The time to open the connection is recorded on every check.
Catches firewall mistakes
A port closed by a rule change is noticed in minutes, not when a user complains.
Same alerts as the rest
Same channels, reminders and recovery notices as the other monitors.
Where it helps
Databases
Know when the database stops accepting connections.
Mail servers
Check that port 25, 465 or 587 is open and answering.
Remote access
Watch SSH or a VPN endpoint that must always be reachable.
Questions
Which plans include it?
Plus and above. Solo covers website (HTTP and HTTPS) and ping monitoring.
Does it check the protocol?
No. It checks that a TCP connection can be opened, not that the service speaks correctly. For web servers, use website monitoring.
Can I check a port on a private address?
No. Private and internal addresses are blocked, so only public targets can be checked from our probes.
What if the port is open only for my own IP?
The check will fail, because it comes from our servers. Allow the addresses listed in the monitor’s settings, or monitor through a public endpoint.
Related features
Try it on your own services.
Add your first monitor in a couple of minutes. The trial lasts 14 days.
Start free trial