Ping Test from a Remote Probe
Run a small ICMP ping test from a Globalping probe to a public domain you have permission to test. The tool sends five packets and shows returned round-trip statistics and the actual probe location. It does not send ICMP packets from your browser or measure the first Wi-Fi hop from your computer.
Run a small ICMP ping test from a Globalping probe to a public domain you have permission to test. The tool sends five packets and shows returned round-trip statistics and the actual probe location. It does not send ICMP packets from your browser or measure the first Wi-Fi hop from your computer.
Five packets from one requested region; the actual responding probe is named in the result.
Best solution
Run a small ICMP ping test from a Globalping probe to a public domain you have permission to test.
Five packets from one requested region; the actual responding probe is named in the result.
No measurement yet. This checks from Globalping probes, not from your computer. No continuous monitoring.
Opens the Kepo download page; this calculation or file is not transferred.
Key solutions at a glance The main decisions from this guide, condensed into one table.
How to Use This Check
Enter a public domain you own or are authorized to test. Use a hostname only, without https, a path or a port. A ping test targets the host reached by name resolution; it does not request a particular article or authenticate to an application.
Choose a probe region and read the consent statement before starting. The request asks Globalping for one probe in that region. Availability is not guaranteed, and the result names the city and network that actually performed the test. This is the relevant starting point when comparing two measurements.
Run the check once and wait for the probe result. Read received packets, sent packets and average round-trip time together. An average based on fewer replies needs the missing replies beside it. An unavailable average is not zero latency, and a request that has not finished is not a final sample.
Compare the result with the same target, protocol and probe context at another time only when a repeat is needed. Do not repeatedly press the button to manufacture a favorable value. A low-latency result from a nearby remote probe can coexist with a slow connection on your laptop because the network paths differ.
What the Result Actually Means
ICMP echo requests ask a target to return a response, allowing the probe to measure the round trip. The ping test shown here is distinct from timing a web API request. The latter includes HTTP behavior and browser processing, while this result comes from the remote probe’s ICMP tool. Some networks filter or deprioritize ICMP even when web services work. A failed echo sample therefore cannot establish that a website, DNS service or game application is unavailable. Use an application-level check when that is the service you need to verify.
| Field or observation | Meaning |
|---|---|
| Protocol | ICMP echo |
| Origin | Named Globalping probe |
| Sample | Five requested packets |
| Interpretation | One path and observation time |
Limits and Common Misreadings
This online ping test cannot isolate problems on your home Wi-Fi. For that, compare local gateway and external targets using tools on a device you control. The remote sample is useful for a different question: how the destination looks from the selected external location.
Five packets are a short diagnostic sample, not a reliability percentage for a month. One missing reply has a large effect on such a small sample. Keep the packet count visible and avoid extrapolating to a service-level commitment.
Globalping measurement records are public. Do not put secret hostnames or internal infrastructure names into a public test, and do not use this tool to probe targets without permission.
An Example of Careful Interpretation: Separate the Observation from Its Cause
Imagine two authorized observations of the same hostname, one from Germany and one from Singapore. Different round-trip times can be expected because the origins, routes and possibly resolved edges differ. You cannot subtract the two numbers and call the difference your home network’s delay. To compare changes over time, keep the requested region and target stable, then inspect the actual returned probe each time. Even the same requested region can select a different network. The context beside the value is what makes the result interpretable rather than just a visually impressive number.
Keep a Useful Troubleshooting Record
Keep the question, input, observation time and source together. A bare address, percentage or status code is difficult to interpret later because it omits the connection and measurement context. When comparing two observations, note what changed between them: the target, network, VPN state, selected adapter, record type or remote origin. Change one relevant condition at a time when possible. That makes the comparison easier to explain without inventing a cause from one number.
Save only information you actually need. Network records can reveal infrastructure names and connection details, even when they do not contain a password. Remove unrelated identifiers before sharing a screenshot with another person. Never put private credentials in a domain field or publish an internal hostname as part of a public test. A copied result is a snapshot, not a promise that the same conditions still apply when someone reads it later.
Kepo is a Mac desktop-widget product for repeated checks and small workflows. A labeled troubleshooting note or a supported monitoring widget can keep the relevant context accessible while you work. The download link opens the product workflow; this article does not automatically install a configured diagnostic widget, transfer your network inputs or start a scheduled check. Confirm the actual widget’s capabilities before relying on it for ongoing observations.
Choose the next task by the question you need answered.
Frequently Asked Questions
Does ping test from a remote probe describe my entire network?
No. The steps and component above define the scope of this observation. A local adapter value, an external address and a remote probe result describe different viewpoints. Preserve that context and do not generalize a single observation to every application or connection.
What should I do when a result is unavailable?
Keep it marked unavailable. An unfinished or failed observation is not a successful zero result and does not establish the cause of a problem. Check the input and try again later only when another observation is useful. Respect provider limits rather than repeatedly retrying.
Does this page save a monitoring history or install a desktop widget?
No. The page provides the specific manual workflow described above. It does not schedule future tests or create a configured desktop widget. Save the relevant result yourself and use an explicitly supported monitoring feature if you need recurring checks.
Sources and Method
Primary references for the protocol, provider or operating-system steps.
A useful network answer states what was checked, where the observation came from and what remains unknown. Keep those distinctions when you save or share the result.
Stay informed with Kepo on your desktop
Embed interactive widgets, monitor dynamic sites, track APIs, and run ambient AI agents right on your macOS desktop.
Related Articles
View all posts →Is It Down? Check a Website Response
Check whether a public domain returns an HTTPS response from a remote Globalping probe. This is a single root-path HEAD request with the actual response code and probe location. It helps answer “is it down from that location now?” but does not establish a worldwide outage or test every part of a website.
Packet Loss Test: A Remote ICMP Sample
Run a 16-packet ICMP sample from a named remote probe and inspect the sent, received and lost packet counts. This packet loss test describes the selected remote path during that short sample. It is not a browser-to-game-server test or a continuous measurement of your Wi-Fi connection.
TCP Port Checker
Check one TCP port on an authorized public domain from a remote Globalping probe. The port checker reports whether TCP responses were observed and retains packet statistics. A missing response is not proof that a port is closed, and this tool does not scan a range of ports or inspect your private local network.
SSL Checker: Inspect a TLS Certificate
Inspect TLS information returned by an HTTPS request from a remote probe, including the certificate subject, issuer, validity dates and probe trust result when available. This SSL checker checks the public domain’s root endpoint. It is not an exhaustive certificate-chain, cipher-suite or browser-compatibility audit.