Skip to content
LookupOwl

Ping from many places

Enter a host name or an IP address to see whether it answers, how fast, and whether that changes between countries.

A domain name or a public IP address. Web addresses work too.

Our server times one TCP connection. Many places asks Globalping, a free probe network, to run a real ping. We tell you first what it receives.

Which part of the world to ask. Used when you run it from many places.

More options

A country, city, network or cloud region. It replaces the choice above.

How many places to test from, 1 to 10. From REST, MCP and the web form without JavaScript at most 5 run.

There are fewer of these, so fewer places may answer.

Packets to send from each place, 1 to 10.

TCP works when a firewall blocks ICMP. It measures connection time, not ping.

Only used with TCP.

Automatic uses whatever the name points to.

A Globalping measurement id from a permalink: show that saved result instead of running a new one. Set by the page, not by hand.

The Globalping id of the IPv4 run to put next to the IPv6 saved result in `id`. Set by the page, not by hand.

Try:

Results for www.example.org

Checked from cache0 ms

JSON

Answers

www.example.org answers from our server

14.6 ms from our server, with no loss. That is one place. To see other countries, run it from many places.

IPv4TCP 443, from our server0% loss
Average
14.6ms
Range
14.3 to 15ms

Jitter 0.4 ms

Loss
0%

4 of 4 replies

Address
172.66.157.237

LookupOwl

  • From our server we time a TCP connection to port 443, not an ICMP ping, because a web server cannot send ping packets. It measures connection time. Choose many places for a real ping.
Places1
  • 1. Our serverLookupOwl · data centre14.6 msFast
    14.4 ms · 14.3 ms · 15 ms · 14.6 ms
    Address answered
    172.66.157.237
    Min / avg / max
    14.3 / 14.6 / 15 ms
    Jitter
    0.4 ms
    Loss
    0% (4 of 4 replies)
    Network
    LookupOwl · data centre
    172.66.157.237:443 connected in 14.42 ms
172.66.157.237:443 connected in 14.33 ms
172.66.157.237:443 connected in 15 ms
172.66.157.237:443 connected in 14.63 ms
Addresses4
AddressGiven to
172.66.157.237Our server
104.20.26.136None of the places used it
2606:4700:10::6814:1a88None of the places used it
2606:4700:10::ac42:9dedNone of the places used it
Run from many placesRun againTrace the path
Structured result (JSON) · 1.6 KB
{
  "target": "www.example.org",
  "mode": "server",
  "protocol": "tcp",
  "port": 443,
  "family": "auto",
  "packets": 4,
  "dns": {
    "status": "ok",
    "a": [
      "172.66.157.237",
      "104.20.26.136"
    ],
    "aaaa": [
      "2606:4700:10::6814:1a88",
      "2606:4700:10::ac42:9ded"
    ]
  },
  "places": [
    {
      "status": "finished",
      "probe": {
        "country": "",
        "city": "Our server",
        "asn": 0,
        "network": "LookupOwl",
        "latitude": 0,
        "longitude": 0,
        "kind": "datacenter"
      },
      "resolvedAddress": "172.66.157.237",
      "family": 4,
      "rtts": [
        14.42,
        14.33,
        15,
        14.63
      ],
      "min": 14.33,
      "avg": 14.6,
      "max": 15,
      "jitter": 0.38,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "172.66.157.237:443 connected in 14.42 ms\n172.66.157.237:443 connected in 14.33 ms\n172.66.157.237:443 connected in 15 ms\n172.66.157.237:443 connected in 14.63 ms"
    }
  ],
  "summary": {
    "asked": 1,
    "ran": 1,
    "answered": 1,
    "median": 14.6,
    "p90": null,
    "fastest": {
      "city": "Our server",
      "avg": 14.6
    },
    "slowest": {
      "city": "Our server",
      "avg": 14.6
    },
    "uneven": null,
    "worstLoss": 0,
    "anycast": true,
    "verdict": "up"
  },
  "tcpFallback": null,
  "v4vsV6": null,
  "notes": [
    "From our server we time a TCP connection to port 443, not an ICMP ping, because a web server cannot send ping packets. It measures connection time. Choose many places for a real ping."
  ],
  "incomplete": false,
  "expired": false
}

Next step

What this ping test does

A ping sends a few small packets to a host and times how long each reply takes. It answers three questions in order: does the host answer at all, how fast and how steady is it, and is that the same everywhere. This page sends the packets from places you choose and puts the answers side by side, with a map, a bar for each place and the numbers underneath.

It tests a server you name, from other places. It is not a test of your own connection. Want to test your own connection? Try the speed and latency test.

  • Reply time. The round trip of each packet in milliseconds, with the fastest, the average and the slowest.
  • Jitter. How much the time changes from one packet to the next. A steady line is good for calls and games.
  • Loss. The share of packets that never came back.
  • Where it answered from. The city, the network and whether the probe sits in a data centre or on a home connection.

How to run a ping test

  1. Enter a host or an addressA domain name such as example.com or a public IP address such as 1.1.1.1. A web address works too: only the host name is used.
  2. Choose where to run it"From our server" is one place, and nothing is sent to anyone else. "From many places" asks a network of volunteer probes to ping from a spread of countries. You can pick an area, or type a country, a city, a network such as AS7922 or a cloud region such as aws-us-east-1.
  3. Read the answerThe headline says whether the host answers everywhere. Open a row to see every packet, the address that place reached and the probe it came from.

How to read the times

We group reply times into four bands, always with a word and a shape as well as a colour: fast is under 50 ms, good is 50 to 150, slow is 150 to 300 and very slow is over 300. These are rules of thumb. Distance sets the floor: light in fibre takes about 1 ms per 100 km each way, so a server in Frankfurt cannot answer a probe in Sydney in 10 ms, whatever its hardware.

What you seeWhat it usually means
One place far slower than the restThe nearest server is a long way from that place, or the path there is poor. Only that row is flagged.
A few lost packets at one placeOften harmless. One reply in four missing once is not a problem by itself.
Steady loss at several placesCongestion or a busy server. Try again in a few minutes and compare.
No reply anywhereThe host may be off, may point at the wrong address, or may ignore ping on purpose.

From our server, or from many places

A web server cannot send real ping packets, because that needs privileges ours does not have. So from our own server we time a TCP connection to a web port instead, and the result says so. It measures connection time, which is close to a ping but not the same thing. For a true ping from several countries, choose many places.

Many places runs through Globalping, a free network of volunteer probe machines. The first time, the page asks before anything is sent. Your browser then asks Globalping to run the check, and Globalping receives the target and your IP address. Without JavaScript, our server asks Globalping for up to 5 places on your behalf instead, and it receives the target and our server's address.

CDNs, blocked pings and what to try next

Some hosts drop ping on purpose and still serve websites. When nothing answers to ping we try a TCP connection to port 443 from the same places. If that works, the verdict is "up, but does not answer ping". If it does not, the page lists what to check next, and the traceroute shows where the path stops, while the port checker tests a single port.

Questions people ask

Is this the same as testing my own internet speed?

No. This tool pings a server you name, from places around the world. To test your own connection, use a speed and latency test.

Why do the places answer so fast?

Many sites sit behind a CDN, which answers from a server close to every probe. Low times everywhere then describe the CDN, not the website's own server. The page adds a note when it sees this.

What does "From our server" measure?

A TCP connection to port 443, or another web port you pick, timed from our server. A web server cannot send ICMP ping packets, so we do not pretend to. The result is labelled TCP.

Why did one place fail to run?

The probes are volunteer machines, and one can go offline or time out before it starts. We list it as "didn't run" with the reason and leave it out of the verdict, because it says nothing about the host.

What is a good ping time?

Under 50 ms is fast and under 150 ms is good for most things. The distance to the server sets the lowest possible time, so compare places that are far apart with that in mind.

Why does a host answer in a browser but not to ping?

Many firewalls drop ICMP on purpose. When ping gets no answer anywhere, we try TCP port 443 from the same places and tell you if the host is up but ignores ping.

Can I use this from a script or an AI assistant?

Yes. The same check is in the REST API and the MCP server as the ping tool. Those run up to 5 places through our server and return every time, the loss and a verdict.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is ping. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/ping?q=example.com&places=1&protocol=tcp"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp

Description for AI agents · OpenAPI · llms.txt