Free Tool — No Signup Required
Free Global Latency Detector
Measure exact latency from 15 real probe locations across AWS and DigitalOcean. See DNS resolution, TCP handshake, TLS negotiation, and TTFB broken down per region.
What We Check
- 1Enter URL or endpoint — Enter your URL or API endpoint.
- 2Simultaneous 15-region check — Latency checks fire from all 15 probe regions simultaneously.
- 3DNS resolution time — DNS resolution time measured per region.
- 4TCP connection time — TCP connection time measured per region.
- 5TLS negotiation time — TLS negotiation time measured per region.
- 6TTFB measurement — Time to First Byte (TTFB) measured per region.
- 7Total response time — Total response time measured per region.
- 8Latency heatmap — Latency heatmap generated showing fastest and slowest regions.
Running one-off checks manually? Run unlimited checks with PingSLA monitoring →
Frequently Asked Questions
- What is TTFB and why does it matter?
- TTFB (Time to First Byte) is the time from when the browser sends a request to when it receives the first byte of the response. It measures server processing time excluding network transfer. For users in India, a high TTFB from a server hosted only in the US can add 200–400ms to every page load.
- Why is my site slow in Australia but fast everywhere else?
- This is usually caused by CDN misconfiguration, missing POPs in the APAC region, or a server located in the US without edge caching. The Latency Detector shows exactly which phase (DNS, TCP, TLS, or server processing) is adding the delay in each region.
- What latency is considered good?
- Under 100ms TTFB is excellent. 100–300ms is acceptable. Over 300ms degrades user experience measurably. For API endpoints used by mobile apps, under 200ms total response time is the industry target.