ROUND-TRIP TIMING

How long does a round trip actually take?

Measures real round-trip response time from your browser to a handful of public network endpoints.

Ping Targets
Ready when you are
TargetMinAvgMaxStatus
ipify (IP API)———Idle
GitHub API———Idle
JSONPlaceholder———Idle
Cloudflare———Idle
Good to know

Why this isn't a traditional ICMP ping

The classic ping command sends raw ICMP packets — something a web browser is deliberately not allowed to do for security reasons. This tool measures the same underlying thing latency describes — round-trip time — by timing an HTTP request/response cycle to each target's API instead.

The numbers you'll see are typically a few milliseconds higher than true ICMP ping, since an HTTP request involves a bit more overhead than a bare ICMP echo. But the relative comparison — which targets are closer or more congested — holds up.

Reading your results

  • Under 30ms — excellent, typical of a nearby server or the same region.
  • 30–80ms — good, normal for cross-country or regional routing.
  • 80–150ms — noticeable but workable for browsing; may feel sluggish in real-time apps.
  • 150ms+ — high latency, often international routing, satellite, or network congestion.