Checking…
Ping test
Check replies and round-trip time to a public target from a named remote Globalping probe.
Checking…
Check replies and round-trip time to a public target from a named remote Globalping probe.
Checking…
Checking…
This starts a remote Globalping measurement. Your target and results are public and may remain available for up to six months. Use a target you are authorized to test.
One remote probe, five packets. TCP uses port 443. No automatic retries; shared service limits apply.
No remote measurement has started.
A ping test sends a small set of probes toward a target and records the replies that return. Use the form above to enter a public IP address or hostname, choose an IP version and region, then start the measurement. MyIP.dog runs this ping test through one Globalping probe. The displayed latency describes that remote probe's connection to the target, rather than the connection from your laptop, phone, or home router.
The distinction matters when you investigate a slow application. A ping test from another network can help check whether the destination answers there. It cannot reproduce your Wi-Fi interference, local congestion, browser extensions, or corporate gateway. Read the actual probe location beside the result before comparing numbers. Choosing a continent requests a probe in that region; it does not promise a particular city, internet provider, or repeatable starting network.
Enter an address without a port, or a hostname without a URL scheme or path. Private, loopback, multicast, documentation, and other unsupported special-use addresses are rejected. This ping test is intended for public destinations you are authorized to check. The example button fills 1.1.1.1 and selects IPv4, but does not submit a measurement. You can inspect all settings before any remote diagnostic begins.
For a hostname, our server asks Google Public DNS for A or AAAA records according to your selection. It follows the returned alias chain, validates the relevant addresses, and selects one public address. That literal address becomes the ping test target, so later probe-side DNS selection cannot silently change it. The result retains both the entered name and tested address. A different resolver or later lookup may legitimately select another destination.
If your ping test reports no usable address, check the selected family and spelling. A domain can publish IPv4 records without publishing IPv6 records. For a literal IPv6 address, select IPv6; the form does not convert it into IPv4. The DNS lookup helps inspect published records separately. Neither a successful lookup nor an accepted address guarantees that a remote probe will receive replies.
The default ping test uses ICMP. The TCP option targets port 443, with no arbitrary port selection. Each run requests five packets from one probe. ICMP echo handling and TCP connection handling can differ because a firewall or service applies different policies. Compare like with like: changing protocol, target, region, and time together makes a before-and-after result difficult to interpret.
A TCP ping test is not a browser page load. It does not verify a certificate, fetch your application's HTML, sign into an account, or exercise a checkout flow. A quick TCP response can coexist with a broken website. Conversely, a destination may ignore ICMP while serving normal HTTPS traffic. Treat the selected protocol as part of the question you asked, not as an interchangeable label attached to a universal health score.
The report identifies the actual probe city, country, network, and autonomous system number supplied by Globalping. It also shows the tested address, requested region, protocol, latest timestamp, and a link to the public source response. Keep these fields with a ping test when sharing it. A latency number copied without its origin and destination is usually insufficient to reproduce a network observation.
Minimum, average, and maximum RTT are measured in milliseconds for received replies. Round-trip time includes the outbound and returning journey, plus any handling involved in generating the response. It does not give a separate one-way delay. This ping test preserves a legitimate zero value if the provider reports one; absent timing information is shown as unavailable rather than silently replaced with zero.
The minimum is the fastest observed reply in this short sample. The average summarizes the received replies, and the maximum is the slowest observed reply. A ping test with widely separated minimum and maximum values suggests variation within that run, but five packets are not enough to characterize a full day's behavior. We do not turn that small sample into a precise jitter rating, service-level guarantee, or prediction of gaming performance.
The ping test displays packets sent, replies received, and the percentage of missing replies reported for the sample. For a hypothetical five-packet run with four replies, one missing response represents 20%. That percentage describes a very small denominator. It is not proof that one fifth of all future application traffic will be lost. Reply filtering, rate limiting, and destination policy can affect the observation.
If no replies arrive, RTT fields have no valid sample to summarize. The ping test shows “No reply” instead of a misleading zero-millisecond result. Preserve the protocol and actual probe location when investigating. Try the application's normal connection path and consult relevant service monitoring. A single unanswered diagnostic is not sufficient to declare that an entire website or network is offline.
Creating a ping test and receiving its final data are separate steps. The interface shows collection progress and retains partial observations as they arrive. A probe can become unavailable, report a failure, or return an unfamiliar status. Those outcomes stay visible. “Collection finished” describes the result-collection process; read the probe outcome beneath it before drawing a conclusion about the target.
The ping test waits for updates for up to 50 seconds after creation. Stopping ends local collection, and clearing removes the displayed result from this page. Neither action cancels or deletes a measurement already submitted to Globalping. If a source link is available, you can inspect it later. An interrupted creation request may have reached the provider even when the browser never received the measurement identifier.
This ping test does not measure download throughput, upload throughput, DNS leak behavior, or whether a VPN hides your traffic. It does not identify the person using an address. It also cannot promise the same route from every country or provider. The IPv6 test checks browser reachability to separate endpoints, while IP comparison compares addresses observed by different destinations. Each tool answers a different question.
Anycast services can answer the same public address from different network locations. A ping test to a well-known resolver may reach a nearby deployment from the selected probe. That does not place every server using the service in that city. Geographical labels attached to the probe describe the measurement origin reported by the provider; they do not establish the physical location of the tested address.
Start by writing down the symptom and expected behavior. For example, a service might work from one office but fail from another. Keep the ping test target, address family, and protocol fixed while collecting a small number of observations from relevant regions. Save the actual probe details, since selecting the same continent again does not ensure the same probe. Avoid treating rapidly repeated measurements as independent evidence of a permanent condition.
For a problem on your own connection, run an appropriate local diagnostic as well. On Windows, the built-in ping command supports a chosen target and bounded packet count. Compare its scope with this remote ping test, then review the router, ISP path, or destination logs as appropriate. Agreement between observations can narrow an investigation, but disagreement often provides useful clues about where their paths differ.
Before starting a ping test, review the disclosure above the form. Targets and results are public at Globalping and may remain available for up to six months. The report can include target and network information. Our server handles the submitted target, and hostname resolution also sends the name to Google Public DNS. Use an IP literal when you intend to test a specific public address without this hostname-resolution step.
MyIP.dog applies limits to ping test creation and polling, and the upstream service has its own availability and usage limits. A rate-limit or busy response is an operational condition, not evidence about your target. Wait before retrying. This tool deliberately avoids automatic creation retries: repeating an uncertain request could start another public measurement when the first one already exists.
There is no universal threshold independent of distance, origin network, destination, protocol, and application needs. A short reply time from a nearby remote probe does not promise the same experience from your device. Use a ping test to compare controlled observations and understand a specific problem. Application timing and actual user experience remain necessary for judging whether a service meets its users' needs.
A speed test transfers data to estimate throughput under its own conditions. This ping test sends a small number of diagnostic probes and summarizes their replies. The tests may also use entirely different origins and destinations. A connection can have substantial bandwidth alongside noticeable delay or intermittent problems. Keep the measurements' units and paths visible rather than trying to convert one number into the other.
Use online traceroute to inspect reported hops from a remote probe. It can add route observations, including gaps where routers do not reply. A ping test alone has no hop-by-hop evidence. Even a traceroute cannot directly reveal every physical link or identify the cause of a missing response, so combine the report with knowledge of the affected application and network.
Use Copy report, review the contents, and include your symptom and expected behavior. The export includes the ping test settings, actual probe, available statistics, collection state, source link, and scope notes. Say explicitly that it was run from a remote probe. If collection stopped early, retain that fact. A carefully scoped report is more useful than an isolated number described as the latency of the whole internet.
This ping test uses the Globalping API; its integration guidance describes tools built on the platform. ICMP echo behavior is specified for IPv4 in RFC 792 and IPv6 in RFC 4443. Hostname selection uses the documented Google Public DNS JSON interface. Read our methodology for the site's broader distinction between observed evidence and inferred conclusions.