Monitor what the public internet can’t see.
Deploy a PingForce probe at a location you control — a branch office, a datacenter, a specific site — and test outbound from exactly that vantage point. See what the connection looks like from where it actually matters. Visible only to your account. Your vantage point, your data.
The public network tests from the outside. A private probe tests from a spot only you can reach.
The 40+ probes in the shared network test from public cloud locations — the outside looking in. They can’t tell you what a connection looks like from inside your branch office, your datacenter, or a specific site you operate. Not a flaw; just where they live.
A private probe runs on hardware you place — a branch office, a datacenter, a remote site. From there it tests outbound: how the internet looks from that location, how that site reaches HQ or a SaaS provider, what a specific egress path actually does. A vantage point no public probe can occupy. And only your account sees it.
Test from places only you can put a probe.
A SaaS or API from your office
Measure how a SaaS app, payment gateway, or API performs from your actual office network — not from a cloud probe that takes a completely different path. The latency your team really sees.
A specific egress point
Verify how traffic actually leaves a particular site or network segment. Confirm a new route or transit change behaves the way you intended, from the exact place it matters.
Branch & inter-office links
From a probe at one of your locations, test the path toward another — headquarters to branch, office to datacenter. Real numbers on links you can’t measure from the public internet.
Connectivity from a fixed point
Sometimes you need to test from a specific place — a customer site, a partner’s network, a remote office. Drop a private probe there and you’ve got a permanent vantage point.
Private means private.
Account-only visibility
A private probe never joins the shared network. It doesn’t appear on anyone else’s map, and no other PingForce user can test from it. It’s yours.
Runs where you put it
The probe lives on hardware you control — your cloud account, your datacenter, your office. You decide where it sits and what it can reach.
Dedicated Private slots
Private probes use Private slots — reserved capacity that’s separate from your shared Flex slots. Your private testing never competes with your public testing.
Private slots, by tier.
Each private probe you deploy uses one Private slot — reserved capacity separate from your shared Flex slots. Private probes are a paid-tier capability; here’s how the allocation scales.
The free Specialist tier doesn’t include Private slots — private probes start at Lieutenant ($7/mo). The free tier still gets 3 Flex slots for public testing and 3 Donated slots.
Keep it to yourself, or share it with the network.
Visible only to your account. A vantage point at a location you control — a branch, a site, a datacenter — for testing outbound from places no public probe can sit. Uses your Private slots. No reward — it’s reserved capacity for you.
Contributed to the shared network so every PingForce user can test from it. Earns you Donated ping slots as a reward. Best when you’ve got a public vantage point worth sharing.
Explore Community ServerQuestions about private probes.
What is a private probe?
A private probe is a PingForce probe you deploy at a location you control — and only your account can see it or test from it. It lets you run ping and traceroute tests outbound from that location: how the internet, HQ, or a SaaS provider looks from your branch office, datacenter, or remote site. A vantage point the public probe network can't occupy.
Can anyone else see my private probe or its data?
No. A private probe never joins the shared network. It doesn't appear on anyone else's map, no other user can test from it, and its results are visible only to your account. If you wanted a probe shared with the network, that would be a community probe instead.
What can a private probe actually test?
It tests outbound from wherever you install it. Put a private probe at a branch office and you can measure how that office reaches the internet, HQ, or a SaaS provider — the real path from that site. It's a vantage point, not a scanner: it tests from its location outward, so it won't reach sideways into private subnets it isn't sitting on. To test from a different spot, place a probe there too.
Which plans include private probes?
Private probes use Private slots, which start at Lieutenant ($7/mo): Lieutenant gets 1, Captain 3, Major 7, and Colonel 20. The free Specialist tier doesn't include Private slots — but it still gives you 3 Flex slots for public testing.
What's the difference between a private probe and a community probe?
A private probe is visible only to you and uses your Private slots — for internal or hard-to-reach infrastructure. A community probe is shared with the whole network and earns you Donated slots as a reward. Same probe software — different visibility and purpose.
How hard is it to deploy?
The probe is lightweight — it runs on a small cloud instance, an on-prem box, or office hardware, and needs outbound network access to report results. Once it's running, you assign it to a Private slot on your account and start testing from it.
What access does the probe need to set up?
Two things, and only at install time: SSH (port 22) and an admin username + password — we use these once to install Docker and the probe, and again only if you ever uninstall. After setup, the probe communicates over port 80 only for API calls back to PingForce; SSH and the admin credentials are no longer used for day-to-day operation. You'll also want to allow our trusted addresses through your firewall — the current list lives at app.pingforce.net/inventory/trusted-ip.
See inside.
Keep it yours.
Deploy a private probe on your own infrastructure and test what the public internet can’t reach. Visible only to you.