Check whether a host port is open and reachable from every region
Enter a target to test from multiple regions
Global latency distribution
| Region / ISP | Fastest | Slowest | Average |
|---|---|---|---|
DNS resolution statistics
When to use TCPing
TCPing measures how long a TCP connection to a particular port takes from each probe. A successful handshake shows that the port is reachable from that location.
TCPing measures TCP connection time instead of ICMP: it opens a TCP three-way handshake to a specific port and records how long the handshake takes. A completed handshake proves that the port is open and reachable from that location, which makes TCPing the right test when a server blocks ping.
Common uses include confirming that a new service is reachable from the internet, checking whether a firewall or security group blocks some regions, and testing whether SSH (22) or RDP (3389) is blocked by a carrier.
Frequently asked questions
What does a successful test confirm?
It confirms TCP reachability. Use an HTTP test to verify the TLS handshake and application response.
What is the difference between TCPing and Ping?
Ping uses ICMP and tells you whether a host is reachable. TCPing uses TCP and tells you whether a specific port accepts connections. Use Ping to judge route quality and TCPing to check whether your service is reachable. If the server blocks ping, only TCPing works.
Which ports do common services use?
HTTP uses 80, HTTPS 443, SSH 22, RDP 3389, MySQL 3306, Redis 6379 and FTP 21. To check that a website is reachable, test port 443.
What does a connection timeout mean?
Either nothing is listening on the port, a firewall or cloud security group drops the traffic, or a network on the path blocks it. If only some regions time out, the service itself is running; check source-IP rules and the network policy in those regions.