globalping-external-checks

Run a Globalping ping or HTTP measurement with locations set to "world" and a limit of 10-20 probes. Results are reported per probe location so you can see which regions succeed or fail rather than a single averaged figure.

Use the dns tool with locations set to "world", a limit of 15-30 probes, and your query type such as A. Report how many resolvers return the new record versus the old one, since disagreement between resolvers is the actual propagation signal.

The no_probes_found response means the measurement never ran because no probe matched your location filter; it is not an outage. Widen the location filter or call the locations tool first to confirm probe availability before retrying.

No, Globalping only measures public endpoints and rejects RFC1918, loopback, link-local, and private IPv6 targets. For internal reachability use pyATS or multivendor-cli, and for paths from your own host outward use gtrace.

Authenticated usage allows 500 probe-measurements per hour, where each probe in your limit counts as one unit. Call the limits tool first to check remaining budget, and prefer one right-sized call over many small ones.

Use ThousandEyes when the question involves trends or baselines, such as whether latency is worse than last week, since it provides continuous monitored history. Globalping is ad-hoc and holds no historical data for comparison.