Skip to content
LookupOwl

Global ping test

Ping one host from many countries at the same time and compare the answers on a map.

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

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 example.com

Checked live lookup2047 ms

JSON

Answers everywhere

example.com answers from all 5 places

Median 1.8 ms, from 1 ms in Sao Paulo to 17.8 ms in Helsinki. No packets lost.

IPv40% lossMany places answered from the same CDN
Where we pinged from
Map of 5 places: 5 fast.

Fastest: Sao Paulo, 1 ms. Slowest: Helsinki, 17.8 ms. Pins are numbered as in the list; the shape is the band (circle fast or good, triangle slow, cross no reply).

Median across places
1.8ms
Slowest
17.8ms

Helsinki

Loss
0%

Worst place

Answered
5 of 5

Every place

Places5
  • 1. Helsinki, FIHetzner Online, AS24940 · data centre17.8 msFast
    17.9 ms · 17.8 ms · 17.8 ms · 17.8 ms
    Address answered
    104.20.23.154
    Min / avg / max
    17.8 / 17.8 / 17.9 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    Hetzner Online, AS24940 · data centre
    PING example.com (104.20.23.154) 56(84) bytes of data.
64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=55 time=17.9 ms
64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=55 time=17.8 ms
64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=55 time=17.8 ms
64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=55 time=17.8 ms

--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1503ms
rtt min/avg/max/mdev = 17.776/17.820/17.920/0.058 ms
  • 2. Buffalo, USHostPapa, AS36352 · data centre13 msFast
    13 ms · 13 ms · 13.1 ms · 13.1 ms
    Address answered
    104.20.23.154
    Min / avg / max
    13 / 13 / 13.1 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    HostPapa, AS36352 · data centre
    PING example.com (104.20.23.154) 56(84) bytes of data.
64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=49 time=13.0 ms
64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=49 time=13.0 ms
64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=49 time=13.1 ms
64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=49 time=13.1 ms

--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1503ms
rtt min/avg/max/mdev = 13.008/13.044/13.087/0.031 ms
  • 4. Sydney, AUOracle, AS31898 · data centre1.8 msFast
    1.9 ms · 1.9 ms · 1.8 ms · 1.8 ms
    Address answered
    104.20.23.154
    Min / avg / max
    1.8 / 1.8 / 1.9 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    Oracle, AS31898 · data centre
    PING example.com (104.20.23.154) 56(84) bytes of data.
64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=55 time=1.85 ms
64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=55 time=1.86 ms
64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=55 time=1.81 ms
64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=55 time=1.82 ms

--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1504ms
rtt min/avg/max/mdev = 1.808/1.834/1.862/0.020 ms
  • 3. Singapore, SGLeaseWeb, AS59253 · data centre1.6 msFast
    1.7 ms · 1.6 ms · 1.7 ms · 1.6 ms
    Address answered
    104.20.23.154
    Min / avg / max
    1.6 / 1.6 / 1.7 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    LeaseWeb, AS59253 · data centre
    PING example.com (104.20.23.154) 56(84) bytes of data.
64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=57 time=1.71 ms
64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=57 time=1.55 ms
64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=57 time=1.69 ms
64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=57 time=1.56 ms

--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1504ms
rtt min/avg/max/mdev = 1.550/1.628/1.714/0.072 ms
  • 5. Sao Paulo, BROracle, AS31898 · data centre1 msFast
    1 ms · 1.1 ms · 0.9 ms · 1 ms
    Address answered
    172.66.147.243
    Min / avg / max
    0.9 / 1 / 1.1 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    Oracle, AS31898 · data centre
    PING example.com (172.66.147.243) 56(84) bytes of data.
64 bytes from example.com (172.66.147.243): icmp_seq=1 ttl=60 time=0.975 ms
64 bytes from example.com (172.66.147.243): icmp_seq=2 ttl=60 time=1.06 ms
64 bytes from example.com (172.66.147.243): icmp_seq=3 ttl=60 time=0.930 ms
64 bytes from example.com (172.66.147.243): icmp_seq=4 ttl=60 time=0.973 ms

--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1502ms
rtt min/avg/max/mdev = 0.930/0.983/1.055/0.045 ms
Addresses4

Different places were given different addresses for example.com. That is normal for a CDN.

AddressGiven to
172.66.147.243Sao Paulo
104.20.23.154Helsinki, Buffalo, Singapore and Sydney
2606:4700:10::6814:179aNone of the places used it
2606:4700:10::ac42:93f3None of the places used it
Run againTrace the path

Probes by Globalping, a free network of volunteer machines.

Structured result (JSON) · 6.0 KB
{
  "target": "example.com",
  "mode": "global",
  "protocol": "icmp",
  "family": "auto",
  "packets": 4,
  "dns": {
    "status": "ok",
    "a": [
      "172.66.147.243",
      "104.20.23.154"
    ],
    "aaaa": [
      "2606:4700:10::6814:179a",
      "2606:4700:10::ac42:93f3"
    ]
  },
  "places": [
    {
      "status": "finished",
      "probe": {
        "country": "FI",
        "city": "Helsinki",
        "asn": 24940,
        "network": "Hetzner Online",
        "latitude": 60.17,
        "longitude": 24.94,
        "kind": "datacenter"
      },
      "resolvedAddress": "104.20.23.154",
      "family": 4,
      "rtts": [
        17.9,
        17.8,
        17.8,
        17.8
      ],
      "min": 17.78,
      "avg": 17.82,
      "max": 17.92,
      "jitter": 0.03,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING example.com (104.20.23.154) 56(84) bytes of data.\n64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=55 time=17.9 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=55 time=17.8 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=55 time=17.8 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=55 time=17.8 ms\n\n--- example.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 17.776/17.820/17.920/0.058 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "US",
        "city": "Buffalo",
        "asn": 36352,
        "network": "HostPapa",
        "latitude": 42.89,
        "longitude": -78.88,
        "kind": "datacenter"
      },
      "resolvedAddress": "104.20.23.154",
      "family": 4,
      "rtts": [
        13,
        13,
        13.1,
        13.1
      ],
      "min": 13.01,
      "avg": 13.04,
      "max": 13.09,
      "jitter": 0.03,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING example.com (104.20.23.154) 56(84) bytes of data.\n64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=49 time=13.0 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=49 time=13.0 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=49 time=13.1 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=49 time=13.1 ms\n\n--- example.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 13.008/13.044/13.087/0.031 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "SG",
        "city": "Singapore",
        "asn": 59253,
        "network": "LeaseWeb",
        "latitude": 1.29,
        "longitude": 103.85,
        "kind": "datacenter"
      },
      "resolvedAddress": "104.20.23.154",
      "family": 4,
      "rtts": [
        1.71,
        1.55,
        1.69,
        1.56
      ],
      "min": 1.55,
      "avg": 1.63,
      "max": 1.71,
      "jitter": 0.14,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING example.com (104.20.23.154) 56(84) bytes of data.\n64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=57 time=1.71 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=57 time=1.55 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=57 time=1.69 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=57 time=1.56 ms\n\n--- example.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 1.550/1.628/1.714/0.072 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "AU",
        "city": "Sydney",
        "asn": 31898,
        "network": "Oracle",
        "latitude": -33.77,
        "longitude": 150.9,
        "kind": "datacenter"
      },
      "resolvedAddress": "104.20.23.154",
      "family": 4,
      "rtts": [
        1.85,
        1.86,
        1.81,
        1.82
      ],
      "min": 1.81,
      "avg": 1.83,
      "max": 1.86,
      "jitter": 0.02,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING example.com (104.20.23.154) 56(84) bytes of data.\n64 bytes from example.com (104.20.23.154): icmp_seq=1 ttl=55 time=1.85 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=2 ttl=55 time=1.86 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=3 ttl=55 time=1.81 ms\n64 bytes from example.com (104.20.23.154): icmp_seq=4 ttl=55 time=1.82 ms\n\n--- example.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 1.808/1.834/1.862/0.020 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "BR",
        "city": "Sao Paulo",
        "asn": 31898,
        "network": "Oracle",
        "latitude": -23.55,
        "longitude": -46.64,
        "kind": "datacenter"
      },
      "resolvedAddress": "172.66.147.243",
      "family": 4,
      "rtts": [
        0.98,
        1.06,
        0.93,
        0.97
      ],
      "min": 0.93,
      "avg": 0.98,
      "max": 1.06,
      "jitter": 0.08,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING example.com (172.66.147.243) 56(84) bytes of data.\n64 bytes from example.com (172.66.147.243): icmp_seq=1 ttl=60 time=0.975 ms\n64 bytes from example.com (172.66.147.243): icmp_seq=2 ttl=60 time=1.06 ms\n64 bytes from example.com (172.66.147.243): icmp_seq=3 ttl=60 time=0.930 ms\n64 bytes from example.com (172.66.147.243): icmp_seq=4 ttl=60 time=0.973 ms\n\n--- example.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1502ms\nrtt min/avg/max/mdev = 0.930/0.983/1.055/0.045 ms"
    }
  ],
  "summary": {
    "asked": 5,
    "ran": 5,
    "answered": 5,
    "median": 1.83,
    "p90": null,
    "fastest": {
      "city": "Sao Paulo",
      "avg": 0.98
    },
    "slowest": {
      "city": "Helsinki",
      "avg": 17.82
    },
    "uneven": null,
    "worstLoss": 0,
    "anycast": true,
    "verdict": "up"
  },
  "tcpFallback": null,
  "v4vsV6": null,
  "notes": [],
  "incomplete": false,
  "expired": false,
  "measurementId": "2qWEXMRiPszetlfvL00021Vgd"
}

Next step

Why ping from many places

A host can answer in 20 ms from one country and in 300 ms from another, or not at all from a network that routes badly to it. A single ping cannot show that. A global ping test sends the same packets from a spread of locations, so you see where a problem is, and whether it is the host, the path or one provider.

It is the quickest way to answer questions such as: is my site slow for customers in Australia, did the move to a new region help, is a game server reachable from Europe, or is a CDN really answering close to everyone.

Choosing the places

  • A preset area. Worldwide mix is one probe per continent. Europe, North America, Asia and Pacific, and South America and Africa spread the places inside that area.
  • Your own place. Type a country such as Germany, a city such as Tokyo, a network such as AS7922 or Comcast, or a cloud region such as aws-us-east-1. It replaces the preset.
  • How many. From 1 to 10 in the browser. REST, MCP and the page without JavaScript run up to 5.
  • Home and office networks only. Most probes sit in data centres. This switch keeps only home and office connections, but there are fewer of those, so fewer places may answer.

What comes back

A map with one numbered pin per place, its shape showing the latency band; a row for each place, slowest first, with a bar from the fastest to the slowest packet; four numbers across places (median, slowest, loss and how many answered); and a tab of the addresses each place reached. Places that could not run are listed with the reason and left out of the verdict.

The result has a link that holds only the probe network's measurement id, not what you typed. Results are kept for a limited time by the probe network, so an old link can show "this saved result has expired" and offer to run it again with the same settings. For the route behind a slow place, the traceroute shows each network on the way.

What is sent, and the limits

The checks run through Globalping, a free network of volunteer machines. Before the first run from your browser the page asks you, because Globalping then receives the target and your IP address. Nothing else leaves your browser, and we do not keep what you tested. To be kind to the people who run the target, we pace how often one address gets pinged.

Questions people ask

How many places can I choose?

Up to ten in the browser, from a preset area or a country, city, network or cloud region you type in. Our server runs up to five when you use the API, MCP or the page without JavaScript.

What is sent to the probe network?

The target you typed and, when your own browser starts the check, your IP address. The page asks before the first run. Nothing else leaves your browser, and the check is not tied to an account because there is none.

Why do some places say they did not run?

Volunteer probes can go offline or time out before they start. They are shown with the reason and are not counted against the target.

Can I test from a specific city or network?

Yes. Type a city such as Tokyo, a country, a network such as AS7922 or a cloud region such as aws-us-east-1 in the place box. There may be no probe for a very small city, in which case we say so.

How is this different from a normal ping?

A normal ping runs from one machine, usually yours. This one runs from several machines in different places at once, which is what shows a regional problem.

Why is it limited for one target?

Pinging someone else's server costs them a little each time. We pace how often one address is checked, so an address that was just tested a lot may ask you to wait a minute.

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=5"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp

Description for AI agents · OpenAPI · llms.txt