One probe lies. Forty probes tell the truth.
On-demand network testing from 40+ probes across 7 cloud providers. Run a ping or traceroute from five continents at once — and see exactly where the problem is.
Your monitoring tool sees one path. Your users take forty.
A single test server only knows its own path to your site. If that path is clean but a user in São Paulo hits a congested transit link, you’ll never see it. One green checkmark, one false sense of security.
Test from North America, Europe, Asia-Pacific, South America, and Africa simultaneously. When results disagree by region, you’ve found the problem — and you know exactly which network path to chase.
7 cloud providers means 7 sets of upstream transit and peering relationships. You’re not just testing from different cities — you’re testing across genuinely different network paths.
Run a test the moment a complaint lands. No waiting for the next scheduled check, no configuring a monitor. Paste a target, pick your probes, go.
Export any result as a shareable link, JSON, or CSV. Hand a vendor hard data instead of “it feels slow.”
Five continents. Seven providers. One test run.
Coverage spans North America, Europe, Asia-Pacific, South America, and Africa, deployed across AWS, Vultr, DigitalOcean, Linode, GCP, Hetzner, and Azure. Multi-provider is intentional — path diversity, not just dots on a map.
Representative probe distribution. Network spans 40+ probes across 7 providers; map is stylized, not geographically precise.
Two test types. Full control over how they run.
Ping
ICMP latency and loss from every probe you select. The fastest read on whether a host is reachable and how it performs by region.
Traceroute
Hop-by-hop path analysis. See exactly where latency spikes or packets drop along the route — the difference between “it’s slow” and “hop 9 at your transit provider is the problem.”
Count, speed, packet size
Configure how many packets, how fast (interval), and at what packet size. Reproduce a specific failure condition or stress a path the way your real traffic does.
Shareable link, JSON, CSV
Every result is exportable. Drop a link in a ticket, pipe JSON into your own tooling, or hand a CSV to a vendor as SLA evidence.
Every result comes with the routing story behind it.
PingForce surfaces WHOIS, IRR, and RPKI data for every target right in the results view. You don’t just see that a path is bad — you see who owns it and whether the route is even supposed to exist.
WHOIS
Registration details, owning organization, and ASN for the target. Know who’s actually responsible for the network you’re testing.
IRR
Internet Routing Registry route objects — the routes the operator has formally declared. Spot mismatches between what’s advertised and what’s registered.
RPKI
Resource Public Key Infrastructure origin validation. See whether a route is cryptographically authorized — a fast tell for hijacks, leaks, or misconfiguration.
What people actually use Global Testing for.
Troubleshooting regional complaints
“Site is slow from Singapore” — test from Singapore and five neighbors, confirm or refute it in seconds.
Validating CDN / anycast routing
After a CDN config change, verify users actually hit the nearest edge from every region.
Pre-deployment BGP / peering checks
Confirm a new peering or BGP change behaves as expected before — and after — you push it.
SLA evidence
Export hard latency and loss numbers as third-party proof when a provider disputes your SLA claim.
Geographic performance benchmarking
Compare your performance against a competitor’s, region by region, with real numbers.
Questions about Global Testing.
How is this different from the Monitor feature?
Global Testing (the Ping feature) is on-demand — you run a test when you want answers, from as many probes as you like. The Monitor feature is continuous — it checks your endpoints on a schedule and alerts you when something breaks. Most teams use both: Monitor tells you something is wrong, Global Testing tells you where.
How many probes can I test from at once?
Up to 50 simultaneous probe tests per run, depending on your tier. Your Flex slots determine how many you can fire at the same time — the free Specialist tier includes 3 Flex slots, scaling up to 50 on Colonel.
What kinds of tests can I run?
Ping (ICMP latency and loss) and Traceroute (hop-by-hop path analysis). You can tune the packet count, interval, and packet size on each run to reproduce specific conditions.
What are the WHOIS, IRR, and RPKI lookups?
For every target you test, PingForce pulls registration and routing data: WHOIS (who owns the network and its ASN), IRR (the routes the operator has declared), and RPKI (whether a route is cryptographically authorized). It turns a latency number into the full routing context behind it.
Can I share or export results?
Yes — every result can be exported as a shareable link, JSON, or CSV. Drop a link straight into a support ticket, feed JSON into your own tooling, or hand a vendor a CSV as SLA evidence.
Can I try it for free?
Yes. You can run a free ping test right now without an account, and the free Specialist tier includes 3 Flex slots for ongoing on-demand testing. No credit card required.
Stop guessing.
Start testing.
Run a free ping test from 40+ probes worldwide. No account, no credit card.