If you're running a business, then you know that ensuring your website and servers are running optimally is essential. One way to do this is by using TCP port monitoring. This process involves constantly checking the status of certain ports on your machines in order to ensure they are open and accessible.
Port monitoring is a vital part of keeping your network running smoothly. By monitoring TCP ports from outside your network, you can quickly identify and fix problems before they cause downtime.
Pinger Man can monitor public TCP ports on an IP address to make sure that they are accessible from outside. You can also track the response time and take action when performance degrades or the service is unreachable.
All valid port numbers in the range 0 to 65535 can be monitored. Typically, our users monitor ports 80 and 443 on a web server to verify that they are accepting connections. Pinger Man uses the TCP protocol's connect method to reach the services running on the port.
Read the TCP Port Monitoring documentation to know how to create port monitors. Our is better suited for monitoring web pages because of it's advanced HTTP capabilities.
You can also use Pinger Man as a reverse monitor to make sure that the ports are not accessible from outside.
Pinger Man sends alerts when the state of your monitor changes between Up and Down.
The initial state does not trigger an alert. As such, a port that is meant to be blocked from public access will be marked as Down when the monitor is first created. But, no alerts will be sent If the port somehow becomes accessible from outside, Pinger Man would mark the monitor as Up and send the alerts you have configured.
Pinger Man sends you a notification via email, SMS, Slack or Twitter when a port can not be reached. You can even receive notifications via webhooks.
Check out the alerts documentation for information on how to setup these actions.
We offer a free plan with support for 5 port monitors.