Your web server might be up, but what if the database crashes? Monitor underlying infrastructure sockets directly for absolute reliability.
Verify network availability at the transport layer. Monitor MySQL (3306), Postgres (5432), or SSH (22).
Eliminate false alarms caused by Nginx misconfigurations, SSL errors, or DNS propagation delays.
Ideal for tracking internal Docker containers, Redis caches, and custom application server ports.
You cannot use HTTP to monitor a database. Instead, use PingStag's TCP Port Monitoring. Simply enter your server's IP address and the designated port (e.g., 3306 or 5432). Our engine will attempt a raw TCP dial to verify the socket is accepting connections.
No. TCP monitoring is a network-layer check (Layer 4). It verifies that the server is physically online and the port is open to receive connections, without performing application-layer login authentication.