Ping over IPv6
Resolve the IPv6 address of a host, ping it from several places and put the result next to IPv4.
Results for googleapis.com
Answers everywhere
googleapis.com answers from all 5 places
Median 1.4 ms, from 0.6 ms in Sydney to 9.6 ms in Houston. No packets lost.
Fastest: Sydney, 0.6 ms. Slowest: Houston, 9.6 ms. Pins are numbered as in the list; the shape is the band (circle fast or good, triangle slow, cross no reply).
Houston
Worst place
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.
- HelsinkiIPv41.3 msAbout the sameIPv61.1 ms
- HoustonIPv410.3 msAbout the sameIPv69.6 ms
- TokyoIPv43.4 msAbout the sameIPv62.1 ms
- SydneyIPv41 msAbout the sameIPv60.6 ms
- Sao PauloIPv41.5 msAbout the sameIPv61.4 ms
Places5
2. Houston, USSnaju Development, AS399646 · data centre9.6 msFast
9.6 ms · 9.6 ms · 9.7 ms · 9.6 ms- Address answered
2607:f8b0:4023:1004::69- Min / avg / max
9.6 / 9.6 / 9.7 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- Snaju Development, AS399646 · data centre
PING googleapis.com (2607:f8b0:4023:1004::69) 56 data bytes 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=1 ttl=112 time=9.55 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=2 ttl=112 time=9.62 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=3 ttl=112 time=9.72 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=4 ttl=112 time=9.61 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1504ms rtt min/avg/max/mdev = 9.553/9.625/9.721/0.060 ms
3. Tokyo, JPxTom, AS3258 · data centre2.1 msFast
2 ms · 2.1 ms · 2.1 ms · 2.1 ms- Address answered
2404:6800:400b:c006::67- Min / avg / max
2 / 2.1 / 2.1 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- xTom, AS3258 · data centre
PING googleapis.com (2404:6800:400b:c006::67) 56 data bytes 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=1 ttl=117 time=2.02 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=2 ttl=117 time=2.08 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=3 ttl=117 time=2.07 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=4 ttl=117 time=2.14 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 2.024/2.077/2.139/0.041 ms
5. Sao Paulo, BRThe Constant Company, AS20473 · data centre1.4 msFast
1.3 ms · 1.4 ms · 1.6 ms · 1.3 ms- Address answered
2800:3f0:4001:80c::2004- Min / avg / max
1.3 / 1.4 / 1.6 ms- Jitter
0.2 ms- Loss
- 0% (4 of 4 replies)
- Network
- The Constant Company, AS20473 · data centre
PING googleapis.com (2800:3f0:4001:80c::2004) 56 data bytes 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=1 ttl=118 time=1.31 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=2 ttl=118 time=1.38 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=3 ttl=118 time=1.55 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=4 ttl=118 time=1.34 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 1.313/1.393/1.547/0.091 ms
1. Helsinki, FIHetzner Online, AS24940 · data centre1.1 msFast
1 ms · 1.1 ms · 1 ms · 1.1 ms- Address answered
2a00:1450:4026:806::2004- Min / avg / max
1 / 1.1 / 1.1 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- Hetzner Online, AS24940 · data centre
PING googleapis.com (2a00:1450:4026:806::2004) 56 data bytes 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=1 ttl=116 time=1.04 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=2 ttl=116 time=1.08 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=3 ttl=116 time=1.04 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=4 ttl=116 time=1.08 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1502ms rtt min/avg/max/mdev = 1.036/1.059/1.081/0.019 ms
4. Sydney, AUVERGETEL, AS142064 · data centre0.6 msFast
0.6 ms · 0.6 ms · 0.6 ms · 0.7 ms- Address answered
2404:6800:4006:802::2004- Min / avg / max
0.6 / 0.6 / 0.7 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- VERGETEL, AS142064 · data centre
PING googleapis.com (2404:6800:4006:802::2004) 56 data bytes 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=1 ttl=116 time=0.601 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=2 ttl=116 time=0.562 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=3 ttl=116 time=0.546 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=4 ttl=116 time=0.653 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1508ms rtt min/avg/max/mdev = 0.546/0.590/0.653/0.041 ms
1. Helsinki, FIHetzner Online, AS24940 · data centre1.1 msFast
1 ms · 1.1 ms · 1 ms · 1.1 ms- Address answered
2a00:1450:4026:806::2004- Min / avg / max
1 / 1.1 / 1.1 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- Hetzner Online, AS24940 · data centre
PING googleapis.com (2a00:1450:4026:806::2004) 56 data bytes 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=1 ttl=116 time=1.04 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=2 ttl=116 time=1.08 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=3 ttl=116 time=1.04 ms 64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=4 ttl=116 time=1.08 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1502ms rtt min/avg/max/mdev = 1.036/1.059/1.081/0.019 ms
2. Houston, USSnaju Development, AS399646 · data centre9.6 msFast
9.6 ms · 9.6 ms · 9.7 ms · 9.6 ms- Address answered
2607:f8b0:4023:1004::69- Min / avg / max
9.6 / 9.6 / 9.7 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- Snaju Development, AS399646 · data centre
PING googleapis.com (2607:f8b0:4023:1004::69) 56 data bytes 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=1 ttl=112 time=9.55 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=2 ttl=112 time=9.62 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=3 ttl=112 time=9.72 ms 64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=4 ttl=112 time=9.61 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1504ms rtt min/avg/max/mdev = 9.553/9.625/9.721/0.060 ms
5. Sao Paulo, BRThe Constant Company, AS20473 · data centre1.4 msFast
1.3 ms · 1.4 ms · 1.6 ms · 1.3 ms- Address answered
2800:3f0:4001:80c::2004- Min / avg / max
1.3 / 1.4 / 1.6 ms- Jitter
0.2 ms- Loss
- 0% (4 of 4 replies)
- Network
- The Constant Company, AS20473 · data centre
PING googleapis.com (2800:3f0:4001:80c::2004) 56 data bytes 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=1 ttl=118 time=1.31 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=2 ttl=118 time=1.38 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=3 ttl=118 time=1.55 ms 64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=4 ttl=118 time=1.34 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 1.313/1.393/1.547/0.091 ms
4. Sydney, AUVERGETEL, AS142064 · data centre0.6 msFast
0.6 ms · 0.6 ms · 0.6 ms · 0.7 ms- Address answered
2404:6800:4006:802::2004- Min / avg / max
0.6 / 0.6 / 0.7 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- VERGETEL, AS142064 · data centre
PING googleapis.com (2404:6800:4006:802::2004) 56 data bytes 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=1 ttl=116 time=0.601 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=2 ttl=116 time=0.562 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=3 ttl=116 time=0.546 ms 64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=4 ttl=116 time=0.653 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1508ms rtt min/avg/max/mdev = 0.546/0.590/0.653/0.041 ms
3. Tokyo, JPxTom, AS3258 · data centre2.1 msFast
2 ms · 2.1 ms · 2.1 ms · 2.1 ms- Address answered
2404:6800:400b:c006::67- Min / avg / max
2 / 2.1 / 2.1 ms- Jitter
0.1 ms- Loss
- 0% (4 of 4 replies)
- Network
- xTom, AS3258 · data centre
PING googleapis.com (2404:6800:400b:c006::67) 56 data bytes 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=1 ttl=117 time=2.02 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=2 ttl=117 time=2.08 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=3 ttl=117 time=2.07 ms 64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=4 ttl=117 time=2.14 ms --- googleapis.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 2.024/2.077/2.139/0.041 ms
Addresses7
Different places were given different addresses for googleapis.com. That is normal for a CDN.
| Address | Given to |
|---|---|
| 142.251.39.196 | None of the places used it |
| 2a00:1450:4007:809::2004 | None of the places used it |
| 2a00:1450:4026:806::2004 | Helsinki |
| 2607:f8b0:4023:1004::69 | Houston |
| 2404:6800:400b:c006::67 | Tokyo |
| 2404:6800:4006:802::2004 | Sydney |
| 2800:3f0:4001:80c::2004 | Sao Paulo |
Probes by Globalping, a free network of volunteer machines.
Structured result (JSON) · 7.2 KB
{
"target": "googleapis.com",
"mode": "global",
"protocol": "icmp",
"family": "6",
"packets": 4,
"dns": {
"status": "ok",
"a": [
"142.251.39.196"
],
"aaaa": [
"2a00:1450:4007:809::2004"
]
},
"places": [
{
"status": "finished",
"probe": {
"country": "FI",
"city": "Helsinki",
"asn": 24940,
"network": "Hetzner Online",
"latitude": 60.17,
"longitude": 24.94,
"kind": "datacenter"
},
"resolvedAddress": "2a00:1450:4026:806::2004",
"family": 6,
"rtts": [
1.04,
1.08,
1.04,
1.08
],
"min": 1.04,
"avg": 1.06,
"max": 1.08,
"jitter": 0.04,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING googleapis.com (2a00:1450:4026:806::2004) 56 data bytes\n64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=1 ttl=116 time=1.04 ms\n64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=2 ttl=116 time=1.08 ms\n64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=3 ttl=116 time=1.04 ms\n64 bytes from googleapis.com (2a00:1450:4026:806::2004): icmp_seq=4 ttl=116 time=1.08 ms\n\n--- googleapis.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1502ms\nrtt min/avg/max/mdev = 1.036/1.059/1.081/0.019 ms"
},
{
"status": "finished",
"probe": {
"country": "US",
"city": "Houston",
"asn": 399646,
"network": "Snaju Development",
"latitude": 29.76,
"longitude": -95.36,
"kind": "datacenter"
},
"resolvedAddress": "2607:f8b0:4023:1004::69",
"family": 6,
"rtts": [
9.55,
9.62,
9.72,
9.61
],
"min": 9.55,
"avg": 9.63,
"max": 9.72,
"jitter": 0.09,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING googleapis.com (2607:f8b0:4023:1004::69) 56 data bytes\n64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=1 ttl=112 time=9.55 ms\n64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=2 ttl=112 time=9.62 ms\n64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=3 ttl=112 time=9.72 ms\n64 bytes from googleapis.com (2607:f8b0:4023:1004::69): icmp_seq=4 ttl=112 time=9.61 ms\n\n--- googleapis.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 9.553/9.625/9.721/0.060 ms"
},
{
"status": "finished",
"probe": {
"country": "JP",
"city": "Tokyo",
"asn": 3258,
"network": "xTom",
"latitude": 35.69,
"longitude": 139.69,
"kind": "datacenter"
},
"resolvedAddress": "2404:6800:400b:c006::67",
"family": 6,
"rtts": [
2.02,
2.08,
2.07,
2.14
],
"min": 2.02,
"avg": 2.08,
"max": 2.14,
"jitter": 0.05,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING googleapis.com (2404:6800:400b:c006::67) 56 data bytes\n64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=1 ttl=117 time=2.02 ms\n64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=2 ttl=117 time=2.08 ms\n64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=3 ttl=117 time=2.07 ms\n64 bytes from googleapis.com (2404:6800:400b:c006::67): icmp_seq=4 ttl=117 time=2.14 ms\n\n--- googleapis.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 2.024/2.077/2.139/0.041 ms"
},
{
"status": "finished",
"probe": {
"country": "AU",
"city": "Sydney",
"asn": 142064,
"network": "VERGETEL",
"latitude": -33.87,
"longitude": 151.21,
"kind": "datacenter"
},
"resolvedAddress": "2404:6800:4006:802::2004",
"family": 6,
"rtts": [
0.6,
0.56,
0.55,
0.65
],
"min": 0.55,
"avg": 0.59,
"max": 0.65,
"jitter": 0.05,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING googleapis.com (2404:6800:4006:802::2004) 56 data bytes\n64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=1 ttl=116 time=0.601 ms\n64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=2 ttl=116 time=0.562 ms\n64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=3 ttl=116 time=0.546 ms\n64 bytes from googleapis.com (2404:6800:4006:802::2004): icmp_seq=4 ttl=116 time=0.653 ms\n\n--- googleapis.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1508ms\nrtt min/avg/max/mdev = 0.546/0.590/0.653/0.041 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:80c::2004",
"family": 6,
"rtts": [
1.31,
1.38,
1.55,
1.34
],
"min": 1.31,
"avg": 1.39,
"max": 1.55,
"jitter": 0.15,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING googleapis.com (2800:3f0:4001:80c::2004) 56 data bytes\n64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=1 ttl=118 time=1.31 ms\n64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=2 ttl=118 time=1.38 ms\n64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=3 ttl=118 time=1.55 ms\n64 bytes from googleapis.com (2800:3f0:4001:80c::2004): icmp_seq=4 ttl=118 time=1.34 ms\n\n--- googleapis.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 1.313/1.393/1.547/0.091 ms"
}
],
"summary": {
"asked": 5,
"ran": 5,
"answered": 5,
"median": 1.39,
"p90": null,
"fastest": {
"city": "Sydney",
"avg": 0.59
},
"slowest": {
"city": "Houston",
"avg": 9.63
},
"uneven": null,
"worstLoss": 0,
"anycast": false,
"verdict": "up"
},
"tcpFallback": null,
"v4vsV6": [
{
"city": "Helsinki",
"v6": {
"avg": 1.06,
"loss": 0
},
"v4": {
"avg": 1.26,
"loss": 0
}
},
{
"city": "Houston",
"v6": {
"avg": 9.63,
"loss": 0
},
"v4": {
"avg": 10.26,
"loss": 0
}
},
{
"city": "Tokyo",
"v6": {
"avg": 2.08,
"loss": 0
},
"v4": {
"avg": 3.35,
"loss": 0
}
},
{
"city": "Sydney",
"v6": {
"avg": 0.59,
"loss": 0
},
"v4": {
"avg": 0.99,
"loss": 0
}
},
{
"city": "Sao Paulo",
"v6": {
"avg": 1.39,
"loss": 0
},
"v4": {
"avg": 1.45,
"loss": 0
}
}
],
"notes": [
"Our server runs at most 5 places. Turn on JavaScript to choose up to 6."
],
"incomplete": false,
"expired": false,
"measurementId": "2rMWtFHuDwRFVbjey00021WWh"
}More in Network
Next step
- Traceroute and MTRPing says it answers. Where does the path slow down?Check googleapis.com in Traceroute and MTR
- Port checkerIs a service port open, not just ping?Check googleapis.com in Port checker
- Is it down?Is the website itself up, layer by layer?Check googleapis.com in Is it down?
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 "https://lookupowl.com/api/v1/tools/ping?q=cloudflare.com&places=1&protocol=tcp"claude mcp add --transport http lookupowl https://lookupowl.com/mcp