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

Checked live lookup2017 ms

JSON

Answers everywhere

github.com answers from all 5 places

Median 4.3 ms, from 2 ms in Sydney to 23.3 ms in Helsinki. No packets lost.

IPv40% loss
Where we pinged from
Map of 5 places: 5 fast.

Fastest: Sydney, 2 ms. Slowest: Helsinki, 23.3 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
4.3ms
Slowest
23.3ms

Helsinki

Loss
0%

Worst place

Answered
5 of 5

Every place

  • Our server runs at most 5 places. Turn on JavaScript to choose up to 6.
Places5
  • 1. Helsinki, FIHetzner Online, AS24940 · data centre23.3 msFast
    23.4 ms · 23.2 ms · 23.3 ms · 23.3 ms
    Address answered
    140.82.121.4
    Min / avg / max
    23.2 / 23.3 / 23.4 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    Hetzner Online, AS24940 · data centre
    PING github.com (140.82.121.4) 56(84) bytes of data.
64 bytes from github.com (140.82.121.4): icmp_seq=1 ttl=46 time=23.4 ms
64 bytes from github.com (140.82.121.4): icmp_seq=2 ttl=46 time=23.2 ms
64 bytes from github.com (140.82.121.4): icmp_seq=3 ttl=46 time=23.3 ms
64 bytes from github.com (140.82.121.4): icmp_seq=4 ttl=46 time=23.3 ms

--- github.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1503ms
rtt min/avg/max/mdev = 23.218/23.308/23.433/0.078 ms
  • 2. Los Angeles, USHostPapa, AS36352 · data centre8.2 msFast
    8.2 ms · 8.2 ms · 8.2 ms · 8.3 ms
    Address answered
    172.182.252.133
    Min / avg / max
    8.2 / 8.2 / 8.3 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    HostPapa, AS36352 · data centre
    PING github.com (172.182.252.133) 56(84) bytes of data.
64 bytes from github.com (172.182.252.133): icmp_seq=1 ttl=112 time=8.15 ms
64 bytes from github.com (172.182.252.133): icmp_seq=2 ttl=112 time=8.16 ms
64 bytes from github.com (172.182.252.133): icmp_seq=3 ttl=112 time=8.20 ms
64 bytes from github.com (172.182.252.133): icmp_seq=4 ttl=112 time=8.28 ms

--- github.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1504ms
rtt min/avg/max/mdev = 8.154/8.198/8.282/0.051 ms
  • 3. Tokyo, JPxTom, AS3258 · data centre4.3 msFast
    4.2 ms · 4.1 ms · 4.7 ms · 4.1 ms
    Address answered
    20.27.177.113
    Min / avg / max
    4.1 / 4.3 / 4.7 ms
    Jitter
    0.4 ms
    Loss
    0% (4 of 4 replies)
    Network
    xTom, AS3258 · data centre
    PING github.com (20.27.177.113) 56(84) bytes of data.
64 bytes from github.com (20.27.177.113): icmp_seq=1 ttl=115 time=4.19 ms
64 bytes from github.com (20.27.177.113): icmp_seq=2 ttl=115 time=4.14 ms
64 bytes from github.com (20.27.177.113): icmp_seq=3 ttl=115 time=4.67 ms
64 bytes from github.com (20.27.177.113): icmp_seq=4 ttl=115 time=4.13 ms

--- github.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1503ms
rtt min/avg/max/mdev = 4.125/4.280/4.666/0.224 ms
  • 5. Sao Paulo, BROracle, AS31898 · data centre3.2 msFast
    3.1 ms · 3 ms · 3.3 ms · 3.2 ms
    Address answered
    4.228.31.150
    Min / avg / max
    3 / 3.2 / 3.3 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    Oracle, AS31898 · data centre
    PING github.com (4.228.31.150) 56(84) bytes of data.
64 bytes from github.com (4.228.31.150): icmp_seq=1 ttl=115 time=3.08 ms
64 bytes from github.com (4.228.31.150): icmp_seq=2 ttl=115 time=3.04 ms
64 bytes from github.com (4.228.31.150): icmp_seq=3 ttl=115 time=3.28 ms
64 bytes from github.com (4.228.31.150): icmp_seq=4 ttl=115 time=3.22 ms

--- github.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1502ms
rtt min/avg/max/mdev = 3.040/3.156/3.284/0.099 ms
  • 4. Sydney, AUOracle, AS31898 · data centre2 msFast
    2 ms · 2 ms · 2 ms · 2 ms
    Address answered
    4.195.217.80
    Min / avg / max
    2 / 2 / 2 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    Oracle, AS31898 · data centre
    PING github.com (4.195.217.80) 56(84) bytes of data.
64 bytes from github.com (4.195.217.80): icmp_seq=1 ttl=114 time=1.98 ms
64 bytes from github.com (4.195.217.80): icmp_seq=2 ttl=114 time=2.00 ms
64 bytes from github.com (4.195.217.80): icmp_seq=3 ttl=114 time=2.00 ms
64 bytes from github.com (4.195.217.80): icmp_seq=4 ttl=114 time=2.01 ms

--- github.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 1502ms
rtt min/avg/max/mdev = 1.976/1.996/2.010/0.012 ms
Addresses5

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

AddressGiven to
140.82.121.4Helsinki
172.182.252.133Los Angeles
20.27.177.113Tokyo
4.195.217.80Sydney
4.228.31.150Sao Paulo
Run againTrace the path

Probes by Globalping, a free network of volunteer machines.

Structured result (JSON) · 6.0 KB
{
  "target": "github.com",
  "mode": "global",
  "protocol": "icmp",
  "family": "auto",
  "packets": 4,
  "dns": {
    "status": "ok",
    "a": [
      "140.82.121.4"
    ],
    "aaaa": []
  },
  "places": [
    {
      "status": "finished",
      "probe": {
        "country": "FI",
        "city": "Helsinki",
        "asn": 24940,
        "network": "Hetzner Online",
        "latitude": 60.17,
        "longitude": 24.94,
        "kind": "datacenter"
      },
      "resolvedAddress": "140.82.121.4",
      "family": 4,
      "rtts": [
        23.4,
        23.2,
        23.3,
        23.3
      ],
      "min": 23.22,
      "avg": 23.31,
      "max": 23.43,
      "jitter": 0.1,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING github.com (140.82.121.4) 56(84) bytes of data.\n64 bytes from github.com (140.82.121.4): icmp_seq=1 ttl=46 time=23.4 ms\n64 bytes from github.com (140.82.121.4): icmp_seq=2 ttl=46 time=23.2 ms\n64 bytes from github.com (140.82.121.4): icmp_seq=3 ttl=46 time=23.3 ms\n64 bytes from github.com (140.82.121.4): icmp_seq=4 ttl=46 time=23.3 ms\n\n--- github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 23.218/23.308/23.433/0.078 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "US",
        "city": "Los Angeles",
        "asn": 36352,
        "network": "HostPapa",
        "latitude": 34.05,
        "longitude": -118.24,
        "kind": "datacenter"
      },
      "resolvedAddress": "172.182.252.133",
      "family": 4,
      "rtts": [
        8.15,
        8.16,
        8.2,
        8.28
      ],
      "min": 8.15,
      "avg": 8.2,
      "max": 8.28,
      "jitter": 0.04,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING github.com (172.182.252.133) 56(84) bytes of data.\n64 bytes from github.com (172.182.252.133): icmp_seq=1 ttl=112 time=8.15 ms\n64 bytes from github.com (172.182.252.133): icmp_seq=2 ttl=112 time=8.16 ms\n64 bytes from github.com (172.182.252.133): icmp_seq=3 ttl=112 time=8.20 ms\n64 bytes from github.com (172.182.252.133): icmp_seq=4 ttl=112 time=8.28 ms\n\n--- github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 8.154/8.198/8.282/0.051 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "JP",
        "city": "Tokyo",
        "asn": 3258,
        "network": "xTom",
        "latitude": 35.69,
        "longitude": 139.69,
        "kind": "datacenter"
      },
      "resolvedAddress": "20.27.177.113",
      "family": 4,
      "rtts": [
        4.19,
        4.14,
        4.67,
        4.13
      ],
      "min": 4.13,
      "avg": 4.28,
      "max": 4.67,
      "jitter": 0.37,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING github.com (20.27.177.113) 56(84) bytes of data.\n64 bytes from github.com (20.27.177.113): icmp_seq=1 ttl=115 time=4.19 ms\n64 bytes from github.com (20.27.177.113): icmp_seq=2 ttl=115 time=4.14 ms\n64 bytes from github.com (20.27.177.113): icmp_seq=3 ttl=115 time=4.67 ms\n64 bytes from github.com (20.27.177.113): icmp_seq=4 ttl=115 time=4.13 ms\n\n--- github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 4.125/4.280/4.666/0.224 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "AU",
        "city": "Sydney",
        "asn": 31898,
        "network": "Oracle",
        "latitude": -33.77,
        "longitude": 150.9,
        "kind": "datacenter"
      },
      "resolvedAddress": "4.195.217.80",
      "family": 4,
      "rtts": [
        1.98,
        2,
        2,
        2.01
      ],
      "min": 1.98,
      "avg": 2,
      "max": 2.01,
      "jitter": 0.01,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING github.com (4.195.217.80) 56(84) bytes of data.\n64 bytes from github.com (4.195.217.80): icmp_seq=1 ttl=114 time=1.98 ms\n64 bytes from github.com (4.195.217.80): icmp_seq=2 ttl=114 time=2.00 ms\n64 bytes from github.com (4.195.217.80): icmp_seq=3 ttl=114 time=2.00 ms\n64 bytes from github.com (4.195.217.80): icmp_seq=4 ttl=114 time=2.01 ms\n\n--- github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1502ms\nrtt min/avg/max/mdev = 1.976/1.996/2.010/0.012 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "BR",
        "city": "Sao Paulo",
        "asn": 31898,
        "network": "Oracle",
        "latitude": -23.55,
        "longitude": -46.64,
        "kind": "datacenter"
      },
      "resolvedAddress": "4.228.31.150",
      "family": 4,
      "rtts": [
        3.08,
        3.04,
        3.28,
        3.22
      ],
      "min": 3.04,
      "avg": 3.16,
      "max": 3.28,
      "jitter": 0.11,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING github.com (4.228.31.150) 56(84) bytes of data.\n64 bytes from github.com (4.228.31.150): icmp_seq=1 ttl=115 time=3.08 ms\n64 bytes from github.com (4.228.31.150): icmp_seq=2 ttl=115 time=3.04 ms\n64 bytes from github.com (4.228.31.150): icmp_seq=3 ttl=115 time=3.28 ms\n64 bytes from github.com (4.228.31.150): icmp_seq=4 ttl=115 time=3.22 ms\n\n--- github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1502ms\nrtt min/avg/max/mdev = 3.040/3.156/3.284/0.099 ms"
    }
  ],
  "summary": {
    "asked": 5,
    "ran": 5,
    "answered": 5,
    "median": 4.28,
    "p90": null,
    "fastest": {
      "city": "Sydney",
      "avg": 2
    },
    "slowest": {
      "city": "Helsinki",
      "avg": 23.31
    },
    "uneven": null,
    "worstLoss": 0,
    "anycast": false,
    "verdict": "up"
  },
  "tcpFallback": null,
  "v4vsV6": null,
  "notes": [
    "Our server runs at most 5 places. Turn on JavaScript to choose up to 6."
  ],
  "incomplete": false,
  "expired": false,
  "measurementId": "2AMgJsAJSNAKrhVRE00021Vgn"
}

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