Security
Outbound-only probes
Probes initiate every connection. Nothing inbound to your network, no ports to open, no firewall rules to write. Your perimeter stays as locked-down as you set it.
FOR DATA CENTERS
Two data centers. One slow path. You'd know which.
A lightweight VM in each facility turns every DC into a network testing origin. Your customers diagnose latency to anywhere on the internet — from inside the rack where their workload runs.
No credit card 60-second signup Cancel anytime
- 1 vCPU
- 2 GB RAM
- Ubuntu/Debian
- Outbound only
BUILD YOUR OWN FLEET
Two ways to deploy. One for your customers. One for you.
Spin up a server in any facility you operate. A lightweight VM is all you need. Choose what role it plays based on who you want testing from it.
01 Add to inventory
From your account inventory page, click Add Server.
02 Enter the details
IP, city, DC name, distro, SSH credentials. Choose Community or Private.
03 Server appears in your inventory
We install the PingForce agent. After install, the probe is outbound-only. No persistent inbound access.
Community Probe
Public probe slot. Your customers test from your DC.
- Appears on every PingForce user's Inventory — including your tenants
- Customers diagnose latency from your facility to anywhere on the internet
- Any community probe you add doesn't count against your testing slots. Free testing capacity for your team.
Turn a 1U slot into a customer-facing feature.
Private Probe
Your fleet only. Test what you don't want on the public map.
- Visible only to your account. Doesn't appear in the community network
- Test internal endpoints, management networks, BGP sessions, peering links
- Use the same PingForce tooling — for ops work the public probes can't reach
Internal infrastructure testing, same platform your customers use.
Pain → Solution
Where it hurts, and how PingForce fixes it.
Customers complain about network issues you can't reproduce.
They're 1,500 miles away seeing 300ms latency. You're testing from inside your own facility seeing 15ms. The ticket sits open because no one has the data to point at where the problem actually is.
Drop a lightweight VM in each DC. Your customers get a global testing dashboard.
1 vCPU, 2 GB RAM, Ubuntu or Debian, outbound only. The probe becomes a network testing origin — your customers can run ping, traceroute, WHOIS, IRR, and RPKI lookups from inside your facility to anywhere in the world. The kind of telemetry that costs $30k/year elsewhere, included with your hosting.
Your customers want network testing tools you don't offer.
Real-time latency from your DC to anywhere. Hop-by-hop traceroute when BGP gets weird. ASN and RPKI lookups when routes look suspicious. Building all that yourself is a six-month engineering project. Buying it is a $30k/year contract.
40+ probes everywhere else. Yours plug into the same network.
Your customers don't just test from your DC — they test from your DC to any of 40+ probes worldwide. When the issue is between your network and AWS in Singapore, your support team can prove it in 30 seconds instead of escalating to engineering.
Single-source latency claims don't end arguments.
"Our SLA says 99.99% — but the customer says they saw 5 minutes of timeouts." Without independent multi-location data from outside your network, every disagreement turns into a he-said-she-said. You need third-party telemetry on the record.
Free for you. Earn donated probe slots for hosting.
Community probes don't count against your testing slot quota — host one for free, host ten for free. Every probe you deploy expands what your customers (and your own ops team) can test, troubleshoot, and prove.
What this looks like
Your customer asks for proof. Here's what they get.
Multi-probe verification turns latency disputes into 30-second resolutions. Pull the data, share the link, close the ticket.
Cloud Providers
7
Multi-cloud verified
Global Probes
40+
Network reach
Detection Time
<3 min
3-check confirmation
Incident History
1 year
SLA evidence retention
Every test result is a shareable link. Hand the customer permanent evidence.
Trust the foundation.
Built to host in your facility.
Lightweight, transparent, and operationally low-risk. Six things the security and ops teams will want to know before they sign off.
Security
Open-source agent
The probe code is fully inspectable. Audit what's running, verify what it does, sign off on every release. Trust requires being able to look.
Privacy
No customer data on the wire
Probes test latency and reachability. They measure how fast packets travel — not what's in them. Your customer traffic is untouched.
Reliability
99.97% probe network uptime
Verified across 40+ probes worldwide. Real number, not a marketing target. The network is multi-cloud, multi-region, and resilient by design.
Resilience
Multi-cloud, no single point of failure
Probes deployed across AWS, GCP, Azure, Vultr, DigitalOcean, Linode, and Hetzner. If one provider has a regional outage, the rest of the network keeps testing.
Operations
Integrations on day one
Slack, Microsoft Teams, PagerDuty, Opsgenie, and generic webhooks. Hook PingForce into your existing alerting and ticketing without a custom integration project.
Tools For The Job
Features built for this work.
Global Testing
Multi-probe ping and traceroute from 40+ globally distributed probes. The reach your customers test against.
Network Intelligence
WHOIS, IRR, RPKI, ASN lookups built into every test result. The data your support team needs when BGP is the suspect.
Incident Monitoring
3-check confirmation, audit trail, full incident history. SLA-grade evidence for the conversations that follow.
Maintenance Windows
Schedule planned maintenance — probes know to skip the window. No false alerts when your team has the floor scheduled.
Field Reports
From teams like yours.
Sample — Replace before launch
We caught a regional CDN issue at 3am that our old monitor missed for 6 hours. PingForce saw three probes flip critical from Asia while everything else stayed green. Saved us a refund cycle.
[CMS: author_name]
[CMS: author_role] · [CMS: author_company]
Sample — Replace before launch
Got a quote from a big enterprise monitoring vendor — $40k a year, six-month rollout, and a sales motion that took weeks. Signed up for Captain in 90 seconds. Same insights, less bureaucracy.
[CMS: author_name]
[CMS: author_role] · [CMS: author_company]
Ready to see what your service looks like from everywhere?
Sign up in 60 seconds. Free forever on Specialist. No credit card. Cancel anytime.