Ping an IP Address
Ping any IP address or hostname from our external server. Reports ICMP round-trip times, packet loss, and min/avg/max latency per packet.
Provide a hostname or IP address to ping from our server.
Every network tool you'll ever need.
Purpose-built utilities for ports, IPs, DNS and email. Completely free, all powered by external probes.
Port Checker
Probe any TCP port on any host
DNS Lookup
Look up the IP addresses behind a domain
rDNS Check
Reverse DNS: map IPs back to hostnames (PTR)
Ping Tool
Check host reachability with ICMP
Speed Test
Gauge download, upload and latency
Proxy Check
Spot VPN or proxy usage
Link Checker
Confirm whether URLs are reachable
HTTP Headers Checker
Examine response headers
What Is My IP?
Reveal your current public IP
IP Subnet Calculator
Work out masks, ranges and CIDR math
IP Converter
Convert between IPv4 and IPv6 either way
ASN Lookup
Look up org, ISP and IP ranges by ASN
IP Blacklist Checker
See whether an IP is spam-listed
IPv6 Website Test
Test if a website supports IPv6 (AAAA + reachability)
SPF Record Checker
Verify your email sender policy
DMARC Validator
Read policy, alignment and reporting config
DKIM Checker
Validate DKIM signatures
Email Header Analyzer
Follow email origin and routing
Ping IP addresses and hostnames from a remote server
Pingie's ping tool sends ICMP echo requests from the pingie.net server to any IP address or hostname you provide. Each request travels from the server to the target and back, and the tool records the round-trip time (RTT) in milliseconds for every packet. Because the requests originate from a remote server rather than your own machine, the results reflect network conditions between that server and your target, not your local connection.
This matters when you want to confirm whether a host is reachable from an external vantage point, or when you need to separate your own network issues from a problem further upstream.
What the results tell you
Every ping response includes a sequence number, the responding host, the RTT in milliseconds, and the raw reply line returned by the system. If no response arrives within three seconds, the result is marked as a timeout. A timeout does not always mean the host is down. Many servers and firewalls block ICMP traffic by policy, so the host may be serving web requests normally while appearing unreachable to a ping test.
When you see consistent RTT values across several pings, the path between the server and the target is stable. Wildly varying times point to congestion or routing instability. A mix of responses and timeouts suggests intermittent packet loss.
How to run a ping test online
- Open the ping tool from the tool menu.
-
Type a hostname (for example,
example.com) or an IP address into the input field. - The tool sends sequential ICMP echo requests and displays each result in real time as replies arrive.
- Review the sequence numbers, RTT values, and any timeout or unreachable notices to draw your conclusions.
No account is required. Results appear as each packet completes, so you do not have to wait for the full sequence to finish before reading early data points.
When to use a server-side ping rather than a local one
Running a local ping from your terminal tells you about reachability from your own network. A server-side ping test online tells you whether a host is reachable from a different network entirely. The two together help you isolate where a problem lives.
Common situations where this tool is useful:
- Confirming a server is up after a deployment or reboot, from a neutral external location.
- Checking whether a firewall change has made a host unreachable to the outside world.
- Measuring baseline latency to a host from a known external network before investigating further.
- Verifying that a domain resolves and the underlying host responds, as a quick first step in diagnosing downtime reports.
- Comparing RTT across multiple targets to understand relative network distance or routing differences.
Ping domain names and IP addresses: How resolution works
When you enter a domain name, the tool resolves it to an IP address before sending any packets. The ICMP echo requests go to the resolved address, and the reply shows the host that responded. This means you can ping a domain or a bare IP with the same input field, and the tool handles the DNS step automatically.
If a domain has multiple IP addresses (load-balanced or anycast setups), the tool will reach whichever address the server's resolver returns. For deeper DNS investigation, the DNS lookup tool lets you inspect all records for a hostname.
Limitations to keep in mind
ICMP-based testing has real constraints. Understanding them helps you interpret results correctly rather than drawing wrong conclusions.
- Hosts that block ICMP will always time out, even when they are fully operational.
- Results reflect server-to-target latency only. Your own connection to the server is not measured.
- A single sequence of pings gives a snapshot, not a long-term picture. Sustained packet loss needs repeated testing over time.
- Some cloud and CDN providers route ICMP differently from HTTP traffic, so ping RTT may not match what a browser experiences.
If you need to check HTTP-level reachability rather than ICMP, the HTTP headers checker sends an actual HTTP request and shows the response headers and status code.
FAQ
A ping IP test sends an ICMP echo request packet to a target IP address or hostname and waits for an ICMP echo reply. The tool measures the round-trip time (RTT) in milliseconds: the duration from when the packet leaves the source server to when the reply returns. This tells you whether the host is reachable and how long the network path takes, but it does not test application-layer services like HTTP or SMTP.
The ping runs entirely from the pingie.net server. Your browser sends a request to the tool, and the server executes the ICMP echo requests toward your target. The RTT values you see reflect the network path between the Pingie server and the target host, not your local internet connection. This is intentional: it gives you an external, neutral view of whether a host is reachable from outside your own network.
Many servers and cloud providers configure their firewalls to drop ICMP packets as a matter of policy. This means the host ignores echo requests and never sends a reply, causing every ping to hit the three-second timeout. The host can still serve HTTP traffic normally because those connections use TCP on port 80 or 443, which the firewall permits. A timeout result does not confirm the host is down; it only confirms ICMP is blocked or the host is unreachable.
A ping test operates at the network layer using ICMP. It checks whether a host is reachable at the IP level and measures raw RTT. It does not open a TCP connection or speak any application protocol. An HTTP headers check opens a full TCP connection on port 80 or 443, sends an HTTP request, and reads the response headers and status code. Use ping to test basic reachability; use the HTTP checker to confirm a web service is responding correctly.
"Unreachable" means the network returned an ICMP destination-unreachable message, indicating that routing failed before the packet could reach the target. This differs from a timeout, where the packet is simply never answered. Unreachable typically points to a routing problem, a missing route on an intermediate hop, or a network that does not exist. A timeout more often points to a firewall dropping packets silently without sending any reply.
You can enter either a domain name or an IP address. When you provide a hostname, the server resolves it to an IP address through DNS before sending the ICMP packets. The resolved address appears in the results alongside the RTT values. If the domain does not resolve, the tool reports an error rather than a timeout. For a full view of a domain's DNS records, use the DNS lookup tool .
RTT benchmarks depend on geographic distance and the type of network path. Hosts on the same continent typically return RTTs under 50 milliseconds. Cross-continental paths often fall in the 100 to 200 millisecond range. Values above 300 milliseconds suggest congestion, a long routing path, or a satellite link. Consistency matters as much as the absolute number: stable RTTs across a sequence indicate a reliable path, while large swings between packets suggest instability or congestion.
The tool processes your request to execute the ping and return results. No personal data is required to use it, and you do not need to create an account. For details on how the site handles any incidental data, the privacy policy covers the full scope of data handling practices on pingie.net.
Your local terminal ping sends ICMP packets from your own machine through your own internet connection. The results reflect your network path to the target. This tool sends packets from the pingie.net server, giving you an external perspective that is independent of your ISP, your router, or your local network configuration. The two approaches answer different questions: local ping diagnoses your connection; a remote ping test checks whether the target is reachable from the wider internet.
Each ICMP echo request carries a sequence number that increments with every packet sent. The sequence number in the result confirms which request the reply corresponds to. If you see a gap in sequence numbers alongside timeouts, it means specific packets in that sequence received no reply within three seconds. This helps you identify whether packet loss is consistent or sporadic across the series.
No. Ping only tests ICMP reachability and does not interact with email infrastructure. To check whether an IP address appears on spam blocklists, use the IP blacklist checker . For email authentication issues, the DKIM checker and DMARC tools on Pingie inspect DNS records that govern how mail servers validate messages. Ping is a network-layer diagnostic, not an application-layer one.
You can enter an IPv6 address or a hostname that resolves to an IPv6 address. The underlying system ping command handles IPv6 natively on supported platforms. If you want to verify whether a website is accessible over IPv6 specifically, the IPv6 website test provides a dedicated check that confirms IPv6 connectivity at the application layer rather than just at the ICMP level.