Online Ping: test whether a server is alive and how fast it responds
Ping is the oldest and simplest way to ask a server: "are you there?" If it answers, you know the server is alive and you get a latency figure, the round-trip time of a packet. The smaller the number, the more responsive it feels.
The difference here is that this tool uses TCP, not ICMP like the ping built into your terminal. The reason is practical: many servers and hosts block ICMP for security, so a regular ping often goes unanswered even when the server is perfectly healthy. With TCP ping, we open a connection to a real port like 443, and that better reflects the actual user experience.
What latency is healthy?
There is no magic number, but there are rough benchmarks. A server in Indonesia accessed from Indonesia should ideally be under 50 ms. A regional server like Singapore is usually 30 to 80 ms. Once it touches hundreds of milliseconds, the delay becomes noticeable when opening pages. Honestly though, more important than the raw number is stability. A steady 120 ms is more comfortable than a number that jumps from 20 to 300.
Reading the ping results
The tool sends several attempts in a row, then summarizes: how many succeeded, the percentage of lost packets, plus the minimum, average, and maximum latency. Packet loss is what you should watch most. Losing a packet now and then is normal, but if half the attempts fail, there is a serious problem in the network path or the server itself.
If it times out
Do not panic right away. A timeout on one port does not necessarily mean the server is down. It could be that the tested port is closed while another is open. Try switching to 80 or 443. The server firewall might also be deliberately swallowing unknown connections. To be sure, pair ping with the port checker for a fuller picture.