ping123 Transparent IP Check
Auto IP check No silent WebRTC

External probe workflow

Multi-node Ping, Trace, and Latency Test

Check how a target looks from multiple regions. Cloudflare Worker aggregates results, while external probe nodes perform the real network tests.

Check IP risk first Run port scanner

Example ping123 result screenshot

The screenshot below uses the designated sample IP 89.116.88.34, not a current visitor IP. Use it as a visual reference for the fields explained on this page.

ping123 network diagnostic result interface.
Probe results are useful when latency, routing, or regional reachability matters.

Why external probes are required

A browser and Cloudflare Worker cannot provide a true ICMP ping or traceroute from several global locations. ping123 therefore treats probes as an external-node capability and keeps the Worker responsible for validation, signing, aggregation, and display.

If no probe nodes are configured yet, the page returns a clear unavailable state instead of pretending to run a real trace.

What the result fields mean

Target IP, domain, or URL to test.
Location Probe node region.
Latency Round-trip or connect timing from the probe node.
Ping ICMP-like result when supported by the node.
Trace Route hops when supported by the node.
Warning Unavailable node or missing signing secret.

Normal signals vs. risk signals

Usually normal

  • Important regions return stable latency.
  • No target region is unexpectedly unreachable.
  • Route signals match the expected hosting geography.
  • Probe node errors are isolated to one location.

Needs attention

  • A key market shows timeout or high packet loss.
  • Route hints point to an unexpected country or transit path.
  • All nodes are unavailable because probe endpoints are not configured.
  • Probe signing secret is missing.

Next action

Use probes after the IP looks clean

Risk score tells you whether an IP looks usable. Probe data tells you whether the route performs well from the regions that matter.

Run port scanner

Fixes and next steps

DNS leak Turn on DNS leak protection in the VPN or proxy client, disable browser Secure DNS if it bypasses the tunnel, set system DNS to the provider's DNS or a trusted encrypted resolver, then rerun the DNS check.
WebRTC leak Limit or disable WebRTC direct candidates, use a browser profile that blocks WebRTC IP exposure, restart the browser, then rerun the WebRTC check before logging in.
Datacenter ASN If the task needs a consumer-looking account environment, switch from a datacenter/VPS ASN to a stable residential, mobile, or dedicated ISP exit and keep the region consistent.
Blacklist or abuse history Do not keep using a high-risk or listed IP for important accounts. Change the IP range or provider, wait for reputation to stabilize, and retest before continuing.
Timezone or language mismatch Align the IP country, system timezone, browser language, account region, and DNS/WebRTC routes so the session tells one consistent location story.
  1. Configure external probe node URLs and shared secret.
  2. Retest from regions that match your users or accounts.
  3. Compare latency before choosing a proxy or server region.
  4. Treat missing nodes as an infrastructure issue, not a target verdict.

FAQ

Can Cloudflare Worker run traceroute directly?

No. The planned design uses external nodes for real network probing.

What happens before nodes are configured?

The API returns a clear unavailable warning.

Is the probe signed?

Configured nodes receive an HMAC signature from the Worker.

Before you continue

Pair route quality with IP purity

A fast route is not enough if the IP is risky, and a clean IP is less useful if it cannot reach the target market reliably.

Check IP risk first Run port scanner