DNSprobe Wiki - IP
Latency
The Latency section measures the approximate network response time between DNSprobe and the tested IP address.
Latency depends on network path, distance, routing, firewalls, and the moment of the test.
It is a useful indicator, but it does not replace multi-region monitoring or full application measurements.
1. Overview
A latency test measures how long a packet takes to reach the host and return, when the host responds.
Some servers block ICMP/ping. In that case, no ping response does not necessarily mean the web or mail service is down.
2. What DNSprobe checks
DNSprobe runs the check asynchronously to avoid slowing the full report.
- Response-time measurement from the DNSprobe server location.
- Reporting of timeouts or hosts that do not answer ping.
- Separate port checks when application availability needs to be distinguished from ping.
3. Interpreting results
Latency should be compared with the target audience and test-server location.
- Low latency: short or well-optimized network path from DNSprobe.
- High latency: distance, congestion, indirect routing, or network protection may be involved.
- Timeout: ICMP blocked, filtered host, or connectivity issue.
4. Best practices
- Test from multiple regions when user performance is critical.
- Do not conclude that a service is offline only because ping fails.
- Monitor sudden latency changes after DNS or CDN migrations.
- Compare ping, port checks, and real HTTP measurements.
5. Manual tests
Measure from your local network.
ping -c 4 203.0.113.10
traceroute 203.0.113.10
curl -w '%{time_connect} %{time_starttransfer}\n' -o /dev/null -s https://example.comYour workstation result can differ from DNSprobe because the network path is not the same.