Skip to content
LookupOwl

Ping over IPv6

Resolve the IPv6 address of a host, ping it from several places and put the result next to IPv4.

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.

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.

Results for google.com

Checked live lookup4156 ms

JSON

Answers everywhere

google.com answers from all 5 places

Median 1.5 ms, from 0.7 ms in Sydney to 3.5 ms in Helsinki. No packets lost.

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

Fastest: Sydney, 0.7 ms. Slowest: Helsinki, 3.5 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.5ms
Slowest
3.5ms

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.
IPv4 and IPv65

IPv6 is flagged as much slower when it takes more than 2 times as long, or 50 ms more. That often means an IPv6 tunnel on the way.

  • Helsinki
    IPv43.9 ms
    About the same
    IPv63.5 ms
  • Montreal
    IPv42 ms
    About the same
    IPv62.1 ms
  • Singapore
    IPv41.3 ms
    About the same
    IPv61.5 ms
  • Sydney
    IPv40.6 ms
    About the same
    IPv60.7 ms
  • Sao Paulo
    IPv41.2 ms
    About the same
    IPv61.4 ms
Places5
  • 1. Helsinki, FIHetzner Online, AS24940 · data centre3.5 msFast
    3.9 ms · 3.6 ms · 3 ms · 3.5 ms
    Address answered
    2a00:1450:4010:c03::64
    Min / avg / max
    3 / 3.5 / 3.9 ms
    Jitter
    0.5 ms
    Loss
    0% (4 of 4 replies)
    Network
    Hetzner Online, AS24940 · data centre
    PING google.com (2a00:1450:4010:c03::64) 56 data bytes
    64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=1 ttl=104 time=3.90 ms
    64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=2 ttl=106 time=3.56 ms
    64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=3 ttl=104 time=3.03 ms
    64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=4 ttl=106 time=3.54 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 1503ms
    rtt min/avg/max/mdev = 3.027/3.506/3.902/0.312 ms
  • 2. Montreal, CAOVH, AS16276 · data centre2.1 msFast
    2.1 ms · 2 ms · 2 ms · 2.1 ms
    Address answered
    2607:f8b0:4020:c07::8a
    Min / avg / max
    2 / 2.1 / 2.1 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    OVH, AS16276 · data centre
    PING google.com (2607:f8b0:4020:c07::8a) 56 data bytes
    64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=1 ttl=102 time=2.06 ms
    64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=2 ttl=102 time=2.04 ms
    64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=3 ttl=102 time=2.03 ms
    64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=4 ttl=102 time=2.12 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 1509ms
    rtt min/avg/max/mdev = 2.029/2.062/2.121/0.036 ms
  • 3. Singapore, SGLeaseWeb, AS59253 · data centre1.5 msFast
    1.6 ms · 1.5 ms · 1.5 ms · 1.5 ms
    Address answered
    2404:6800:4003:c04::66
    Min / avg / max
    1.5 / 1.5 / 1.6 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    LeaseWeb, AS59253 · data centre
    PING google.com (2404:6800:4003:c04::66) 56 data bytes
    64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=1 ttl=112 time=1.64 ms
    64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=2 ttl=112 time=1.45 ms
    64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=3 ttl=112 time=1.48 ms
    64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=4 ttl=112 time=1.48 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 1504ms
    rtt min/avg/max/mdev = 1.450/1.510/1.636/0.073 ms
  • 5. Sao Paulo, BRThe Constant Company, AS20473 · data centre1.4 msFast
    1.5 ms · 1.4 ms · 1.4 ms · 1.3 ms
    Address answered
    2800:3f0:4001:808::200e
    Min / avg / max
    1.3 / 1.4 / 1.5 ms
    Jitter
    0.1 ms
    Loss
    0% (4 of 4 replies)
    Network
    The Constant Company, AS20473 · data centre
    PING google.com (2800:3f0:4001:808::200e) 56 data bytes
    64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=1 ttl=119 time=1.47 ms
    64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=2 ttl=119 time=1.39 ms
    64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=3 ttl=119 time=1.40 ms
    64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=4 ttl=119 time=1.33 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 1503ms
    rtt min/avg/max/mdev = 1.330/1.398/1.469/0.049 ms
  • 4. Sydney, AUVERGETEL, AS142064 · data centre0.7 msFast
    0.7 ms · 0.7 ms · 0.7 ms · 0.8 ms
    Address answered
    2404:6800:4006:807::200e
    Min / avg / max
    0.7 / 0.7 / 0.8 ms
    Jitter
    0 ms
    Loss
    0% (4 of 4 replies)
    Network
    VERGETEL, AS142064 · data centre
    PING google.com (2404:6800:4006:807::200e) 56 data bytes
    64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=1 ttl=117 time=0.689 ms
    64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=2 ttl=117 time=0.679 ms
    64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=3 ttl=117 time=0.667 ms
    64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=4 ttl=117 time=0.762 ms
    
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 1507ms
    rtt min/avg/max/mdev = 0.667/0.699/0.762/0.037 ms
Addresses7

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

AddressGiven to
172.217.20.46None of the places used it
2a00:1450:4007:81b::200eNone of the places used it
2a00:1450:4010:c03::64Helsinki
2607:f8b0:4020:c07::8aMontreal
2404:6800:4003:c04::66Singapore
2404:6800:4006:807::200eSydney
2800:3f0:4001:808::200eSao Paulo

Probes by Globalping, a free network of volunteer machines.

Structured result (JSON) · 7.1 KB
{
  "target": "google.com",
  "mode": "global",
  "protocol": "icmp",
  "family": "6",
  "packets": 4,
  "dns": {
    "status": "ok",
    "a": [
      "172.217.20.46"
    ],
    "aaaa": [
      "2a00:1450:4007:81b::200e"
    ]
  },
  "places": [
    {
      "status": "finished",
      "probe": {
        "country": "FI",
        "city": "Helsinki",
        "asn": 24940,
        "network": "Hetzner Online",
        "latitude": 60.17,
        "longitude": 24.94,
        "kind": "datacenter"
      },
      "resolvedAddress": "2a00:1450:4010:c03::64",
      "family": 6,
      "rtts": [
        3.9,
        3.56,
        3.03,
        3.54
      ],
      "min": 3.03,
      "avg": 3.51,
      "max": 3.9,
      "jitter": 0.46,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING google.com (2a00:1450:4010:c03::64) 56 data bytes\n64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=1 ttl=104 time=3.90 ms\n64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=2 ttl=106 time=3.56 ms\n64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=3 ttl=104 time=3.03 ms\n64 bytes from google.com (2a00:1450:4010:c03::64): icmp_seq=4 ttl=106 time=3.54 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 3.027/3.506/3.902/0.312 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "CA",
        "city": "Montreal",
        "asn": 16276,
        "network": "OVH",
        "latitude": 45.51,
        "longitude": -73.59,
        "kind": "datacenter"
      },
      "resolvedAddress": "2607:f8b0:4020:c07::8a",
      "family": 6,
      "rtts": [
        2.06,
        2.04,
        2.03,
        2.12
      ],
      "min": 2.03,
      "avg": 2.06,
      "max": 2.12,
      "jitter": 0.04,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING google.com (2607:f8b0:4020:c07::8a) 56 data bytes\n64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=1 ttl=102 time=2.06 ms\n64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=2 ttl=102 time=2.04 ms\n64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=3 ttl=102 time=2.03 ms\n64 bytes from google.com (2607:f8b0:4020:c07::8a): icmp_seq=4 ttl=102 time=2.12 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1509ms\nrtt min/avg/max/mdev = 2.029/2.062/2.121/0.036 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "SG",
        "city": "Singapore",
        "asn": 59253,
        "network": "LeaseWeb",
        "latitude": 1.29,
        "longitude": 103.85,
        "kind": "datacenter"
      },
      "resolvedAddress": "2404:6800:4003:c04::66",
      "family": 6,
      "rtts": [
        1.64,
        1.45,
        1.48,
        1.48
      ],
      "min": 1.45,
      "avg": 1.51,
      "max": 1.64,
      "jitter": 0.07,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING google.com (2404:6800:4003:c04::66) 56 data bytes\n64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=1 ttl=112 time=1.64 ms\n64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=2 ttl=112 time=1.45 ms\n64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=3 ttl=112 time=1.48 ms\n64 bytes from google.com (2404:6800:4003:c04::66): icmp_seq=4 ttl=112 time=1.48 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 1.450/1.510/1.636/0.073 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "AU",
        "city": "Sydney",
        "asn": 142064,
        "network": "VERGETEL",
        "latitude": -33.87,
        "longitude": 151.21,
        "kind": "datacenter"
      },
      "resolvedAddress": "2404:6800:4006:807::200e",
      "family": 6,
      "rtts": [
        0.69,
        0.68,
        0.67,
        0.76
      ],
      "min": 0.67,
      "avg": 0.7,
      "max": 0.76,
      "jitter": 0.04,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING google.com (2404:6800:4006:807::200e) 56 data bytes\n64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=1 ttl=117 time=0.689 ms\n64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=2 ttl=117 time=0.679 ms\n64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=3 ttl=117 time=0.667 ms\n64 bytes from google.com (2404:6800:4006:807::200e): icmp_seq=4 ttl=117 time=0.762 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1507ms\nrtt min/avg/max/mdev = 0.667/0.699/0.762/0.037 ms"
    },
    {
      "status": "finished",
      "probe": {
        "country": "BR",
        "city": "Sao Paulo",
        "asn": 20473,
        "network": "The Constant Company",
        "latitude": -23.53,
        "longitude": -46.79,
        "kind": "datacenter"
      },
      "resolvedAddress": "2800:3f0:4001:808::200e",
      "family": 6,
      "rtts": [
        1.47,
        1.39,
        1.4,
        1.33
      ],
      "min": 1.33,
      "avg": 1.4,
      "max": 1.47,
      "jitter": 0.05,
      "loss": 0,
      "sent": 4,
      "received": 4,
      "band": "fast",
      "raw": "PING google.com (2800:3f0:4001:808::200e) 56 data bytes\n64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=1 ttl=119 time=1.47 ms\n64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=2 ttl=119 time=1.39 ms\n64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=3 ttl=119 time=1.40 ms\n64 bytes from google.com (2800:3f0:4001:808::200e): icmp_seq=4 ttl=119 time=1.33 ms\n\n--- google.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 1.330/1.398/1.469/0.049 ms"
    }
  ],
  "summary": {
    "asked": 5,
    "ran": 5,
    "answered": 5,
    "median": 1.51,
    "p90": null,
    "fastest": {
      "city": "Sydney",
      "avg": 0.7
    },
    "slowest": {
      "city": "Helsinki",
      "avg": 3.51
    },
    "uneven": null,
    "worstLoss": 0,
    "anycast": false,
    "verdict": "up"
  },
  "tcpFallback": null,
  "v4vsV6": [
    {
      "city": "Helsinki",
      "v6": {
        "avg": 3.51,
        "loss": 0
      },
      "v4": {
        "avg": 3.92,
        "loss": 0
      }
    },
    {
      "city": "Montreal",
      "v6": {
        "avg": 2.06,
        "loss": 0
      },
      "v4": {
        "avg": 2,
        "loss": 0
      }
    },
    {
      "city": "Singapore",
      "v6": {
        "avg": 1.51,
        "loss": 0
      },
      "v4": {
        "avg": 1.32,
        "loss": 0
      }
    },
    {
      "city": "Sydney",
      "v6": {
        "avg": 0.7,
        "loss": 0
      },
      "v4": {
        "avg": 0.63,
        "loss": 0
      }
    },
    {
      "city": "Sao Paulo",
      "v6": {
        "avg": 1.4,
        "loss": 0
      },
      "v4": {
        "avg": 1.21,
        "loss": 0
      }
    }
  ],
  "notes": [
    "Our server runs at most 5 places. Turn on JavaScript to choose up to 6."
  ],
  "incomplete": false,
  "expired": false,
  "measurementId": "2Rl2milO15p6fd34U00021W4s"
}

Next step

What an IPv6 ping shows

IPv6 is the newer internet address format, and many hosts answer on both families through different paths. A host can be fast over IPv4 and slow or silent over IPv6 without anyone noticing, because browsers quietly fall back to the family that works. Pinging both from the same places makes the difference visible.

Enter a host name and we look up its AAAA record, then ping the IPv6 address from each place. The same places are then pinged over IPv4, and each row shows the two side by side with the address each family reached.

Reading the IPv4 and IPv6 comparison

  • About the same. The two families are within a factor of two and 50 ms of each other. Nothing to fix.
  • IPv6 is much slower here. IPv6 takes more than twice as long, or 50 ms more, than IPv4 from that place. This often means an IPv6 tunnel or a poor route on the way.
  • No IPv6 route. The place got no reply over IPv6, while IPv4 worked. The probe may have no IPv6 connectivity, or the path may be broken.

A probe without IPv6 connectivity of its own says nothing about the host, so look at several places before drawing a conclusion. If most places agree, the host is the cause. If only one place disagrees, that probe or its network is.

When a host has no IPv6 address

A name with no AAAA record has nothing to ping over IPv6. We say so plainly and offer the IPv4 ping instead, along with a DNS lookup so you can see which records the name does have. Adding IPv6 means adding an AAAA record at the DNS provider and making sure the server listens on the new address.

How the probes are chosen

Many places runs through Globalping, a free network of volunteer probe machines. Pick an area or type a country, a city, a network or a cloud region, and tell us how many places you want. The probes are volunteer machines, many in data centres, so the times show how the internet sees the host from those places and not from your house.

Questions people ask

What if a host has no IPv6 address?

Then there is nothing to ping over IPv6. We say so, show the IPv4 address it does have, and offer the IPv4 ping instead.

Why is IPv6 slower than IPv4 for some hosts?

The two families can take different paths. A tunnel, a smaller provider network or a route that crosses an ocean can add a lot of delay to IPv6 while IPv4 stays direct.

Does a slow IPv6 path hurt visitors?

Browsers try both families and use the one that connects first, so visitors rarely notice. It still matters for services that prefer IPv6, and it can hide a broken IPv6 setup.

Can I ping a raw IPv6 address?

Yes, from our server. The probe network accepts IPv6 only for host names, so a bare address is timed from our own server as a TCP connection, and the result is labelled that way.

Why does one place show no IPv6 route?

Not every volunteer probe has IPv6 connectivity. If only one place fails and the others answer, the probe is the likely cause, not the host.

Which addresses did each place reach?

The Addresses tab lists every address the name resolved to and which places reached each one. CDNs often hand different places different addresses.

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=cloudflare.com&places=1&protocol=tcp"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp