When a customer says “it’s broken,” see exactly where it breaks.
Trace a request through all seven layers from 40+ probes worldwide. Stop guessing on tickets — reproduce the issue, prove the cause, and reply with evidence.
The tickets that ruin your afternoon — solved before your coffee gets cold.
“Works for me” isn’t an answer your customer wants to hear. PingForce turns the vague, the intermittent, and the it-only-happens-sometimes tickets into a screenshot you can paste straight into the reply.
São Paulo — reproduced the hang200 OKpeering congestion, not your appTest from where your customers actually are — all 40+ of them.
Your customers aren’t all sitting in your office. When one of them has a problem, run a single test that fans out across 40+ probes on 7 cloud providers — North America, Europe, Asia-Pacific, South America, and Africa — and see exactly which corners of the world are healthy and which are hurting.
Build a fleet that watches from inside the places the public probes can’t reach.
The 40+ global probes cover the open internet. But your trickiest tickets live behind a firewall, at a branch office, or on a customer’s private network. Deploy your own probes anywhere — any cloud, any datacenter, on-prem, a closet in Cleveland — and test from the exact spot where the problem actually happens.
Private probes
Community probes
The public 40+
Don’t just fix it — show your work.
A diagnosis nobody can see is just a hunch. Turn every test into proof you can paste into a reply, and give customers a status page they can check themselves — so the next outage generates fewer tickets, not more.
From the people answering the tickets.
Questions support teams ask us.
A customer reports an issue I can't reproduce. What do I do?
Run a Ping test targeting your site and choose probes in the customer's region. You'll see exactly what they see — latency, packet loss, and the full traceroute path — even when it works fine from your office. If 39 probes are healthy and one region is failing, you've found your answer in under a minute.
How do I prove a problem is the customer's ISP and not our service?
Traceroute shows the request hop by hop. When the path stalls or drops before it reaches your server, that's upstream — the customer's network or a carrier in between. Share the result link so the customer can see the breakdown point themselves.
Can I catch problems that only happen intermittently?
Yes. The Monitor Feature runs continuous checks and timestamps every failure, so an intermittent issue leaves a paper trail even when it's not happening at the moment you look. We require 3 consecutive failed checks before opening an incident, so you get real signal, not noise.
Can I test from inside our own network?
Yes — deploy a private probe on your own infrastructure (cloud, datacenter, on-prem, or a branch office). It's visible only to you and lets you test from inside firewalls or specific egress points the public probes can't reach.
Can customers see status without opening a ticket?
Publish a status page — public or password-protected — showing real-time service state and incident history. Captain tier includes 2 status pages, with more on higher tiers. Most teams see "is it down?" tickets drop once customers can self-serve.
How does my team get alerted?
Alerts fire when an incident opens and again when it closes, across email, SMS, Slack, Microsoft Teams, and webhooks (for PagerDuty, Opsgenie, and the like). Share monitors with teammates at read-only or read/write permission — child accounts are included on Captain and up.
Can I export results for a postmortem?
Every Ping test exports as a shareable link, JSON, or CSV. Drop the link in a ticket, feed the JSON into your own tooling, or pull the CSV into a postmortem doc. Monitor incident history is retained for one year for SLA evidence.
Stop guessing on tickets.
Start closing them with proof.
Free forever tier. Setup in 5 minutes. No credit card.