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.
Results for ws.support.github.com
Answers everywhere
ws.support.github.com answers from all 5 places
Median 114.5 ms, from 32.1 ms in Buffalo to 224.6 ms in Singapore. No packets lost.
IPv40% loss
Where we pinged from
Map of 5 places: 2 good, 1 fast, 2 slow.
Fastest: Buffalo, 32.1 ms. Slowest: Singapore, 224.6 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
114.5ms
Slowest
224.6ms
Singapore
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
3. Singapore, SGLeaseWeb, AS59253 · data centre224.6 msSlow
225 ms · 225 ms · 225 ms · 225 ms- Address answered
140.82.114.22- Min / avg / max
224.6 / 224.6 / 224.7 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- LeaseWeb, AS59253 · data centre
PING ws.support.github.com (140.82.114.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=1 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=2 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=3 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=4 ttl=48 time=225 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1501ms rtt min/avg/max/mdev = 224.598/224.626/224.663/0.025 ms
4. Sydney, AUOracle, AS31898 · data centre199.9 msSlow
200 ms · 200 ms · 200 ms · 200 ms- Address answered
140.82.112.21- Min / avg / max
199.7 / 199.9 / 200 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- Oracle, AS31898 · data centre
PING ws.support.github.com (140.82.112.21) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=48 time=200 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 199.713/199.869/199.985/0.098 ms
5. Sao Paulo, BROracle, AS31898 · data centre114.5 msGood
115 ms · 114 ms · 115 ms · 115 ms- Address answered
140.82.112.22- Min / avg / max
114.4 / 114.5 / 114.6 ms- Jitter
0.7 ms- Loss
- 0% (4 of 4 replies)
- Network
- Oracle, AS31898 · data centre
PING ws.support.github.com (140.82.112.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=1 ttl=50 time=115 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=2 ttl=50 time=114 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=3 ttl=50 time=115 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=4 ttl=50 time=115 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 114.394/114.521/114.583/0.076 ms
1. Falkenstein, DEHetzner Online, AS24940 · data centre89.3 msGood
89.3 ms · 89.4 ms · 89.1 ms · 89.3 ms- Address answered
140.82.112.21- Min / avg / max
89.1 / 89.3 / 89.4 ms- Jitter
0.2 ms- Loss
- 0% (4 of 4 replies)
- Network
- Hetzner Online, AS24940 · data centre
PING ws.support.github.com (140.82.112.21) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=44 time=89.3 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=44 time=89.4 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=44 time=89.1 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=44 time=89.3 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 89.092/89.271/89.360/0.106 ms
2. Buffalo, USHostPapa, AS36352 · data centre32.1 msFast
31.3 ms · 32.8 ms · 31.3 ms · 32.8 ms- Address answered
140.82.113.22- Min / avg / max
31.3 / 32.1 / 32.8 ms- Jitter
1.5 ms- Loss
- 0% (4 of 4 replies)
- Network
- HostPapa, AS36352 · data centre
PING ws.support.github.com (140.82.113.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=1 ttl=44 time=31.3 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=2 ttl=44 time=32.8 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=3 ttl=44 time=31.3 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=4 ttl=44 time=32.8 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1504ms rtt min/avg/max/mdev = 31.311/32.062/32.813/0.742 ms
2. Buffalo, USHostPapa, AS36352 · data centre32.1 msFast
31.3 ms · 32.8 ms · 31.3 ms · 32.8 ms- Address answered
140.82.113.22- Min / avg / max
31.3 / 32.1 / 32.8 ms- Jitter
1.5 ms- Loss
- 0% (4 of 4 replies)
- Network
- HostPapa, AS36352 · data centre
PING ws.support.github.com (140.82.113.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=1 ttl=44 time=31.3 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=2 ttl=44 time=32.8 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=3 ttl=44 time=31.3 ms 64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=4 ttl=44 time=32.8 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1504ms rtt min/avg/max/mdev = 31.311/32.062/32.813/0.742 ms
1. Falkenstein, DEHetzner Online, AS24940 · data centre89.3 msGood
89.3 ms · 89.4 ms · 89.1 ms · 89.3 ms- Address answered
140.82.112.21- Min / avg / max
89.1 / 89.3 / 89.4 ms- Jitter
0.2 ms- Loss
- 0% (4 of 4 replies)
- Network
- Hetzner Online, AS24940 · data centre
PING ws.support.github.com (140.82.112.21) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=44 time=89.3 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=44 time=89.4 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=44 time=89.1 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=44 time=89.3 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 89.092/89.271/89.360/0.106 ms
5. Sao Paulo, BROracle, AS31898 · data centre114.5 msGood
115 ms · 114 ms · 115 ms · 115 ms- Address answered
140.82.112.22- Min / avg / max
114.4 / 114.5 / 114.6 ms- Jitter
0.7 ms- Loss
- 0% (4 of 4 replies)
- Network
- Oracle, AS31898 · data centre
PING ws.support.github.com (140.82.112.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=1 ttl=50 time=115 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=2 ttl=50 time=114 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=3 ttl=50 time=115 ms 64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=4 ttl=50 time=115 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 114.394/114.521/114.583/0.076 ms
3. Singapore, SGLeaseWeb, AS59253 · data centre224.6 msSlow
225 ms · 225 ms · 225 ms · 225 ms- Address answered
140.82.114.22- Min / avg / max
224.6 / 224.6 / 224.7 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- LeaseWeb, AS59253 · data centre
PING ws.support.github.com (140.82.114.22) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=1 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=2 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=3 ttl=48 time=225 ms 64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=4 ttl=48 time=225 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1501ms rtt min/avg/max/mdev = 224.598/224.626/224.663/0.025 ms
4. Sydney, AUOracle, AS31898 · data centre199.9 msSlow
200 ms · 200 ms · 200 ms · 200 ms- Address answered
140.82.112.21- Min / avg / max
199.7 / 199.9 / 200 ms- Jitter
0 ms- Loss
- 0% (4 of 4 replies)
- Network
- Oracle, AS31898 · data centre
PING ws.support.github.com (140.82.112.21) 56(84) bytes of data. 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=48 time=200 ms 64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=48 time=200 ms --- ws.support.github.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 199.713/199.869/199.985/0.098 ms
Addresses6
Different places were given different addresses for ws.support.github.com. That is normal for a CDN.
| Address | Given to |
|---|---|
| 140.82.112.22 | Sao Paulo |
| 140.82.114.22 | Singapore |
| 140.82.113.21 | None of the places used it |
| 140.82.113.22 | Buffalo |
| 140.82.114.21 | None of the places used it |
| 140.82.112.21 | Falkenstein and Sydney |
Probes by Globalping, a free network of volunteer machines.
Structured result (JSON) · 6.5 KB
{
"target": "ws.support.github.com",
"mode": "global",
"protocol": "icmp",
"family": "auto",
"packets": 4,
"dns": {
"status": "ok",
"a": [
"140.82.112.22",
"140.82.114.22",
"140.82.113.21",
"140.82.113.22",
"140.82.114.21",
"140.82.112.21"
],
"aaaa": []
},
"places": [
{
"status": "finished",
"probe": {
"country": "DE",
"city": "Falkenstein",
"asn": 24940,
"network": "Hetzner Online",
"latitude": 50.48,
"longitude": 12.37,
"kind": "datacenter"
},
"resolvedAddress": "140.82.112.21",
"family": 4,
"rtts": [
89.3,
89.4,
89.1,
89.3
],
"min": 89.09,
"avg": 89.27,
"max": 89.36,
"jitter": 0.2,
"loss": 0,
"sent": 4,
"received": 4,
"band": "good",
"raw": "PING ws.support.github.com (140.82.112.21) 56(84) bytes of data.\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=44 time=89.3 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=44 time=89.4 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=44 time=89.1 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=44 time=89.3 ms\n\n--- ws.support.github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 89.092/89.271/89.360/0.106 ms"
},
{
"status": "finished",
"probe": {
"country": "US",
"city": "Buffalo",
"asn": 36352,
"network": "HostPapa",
"latitude": 42.89,
"longitude": -78.88,
"kind": "datacenter"
},
"resolvedAddress": "140.82.113.22",
"family": 4,
"rtts": [
31.3,
32.8,
31.3,
32.8
],
"min": 31.31,
"avg": 32.06,
"max": 32.81,
"jitter": 1.5,
"loss": 0,
"sent": 4,
"received": 4,
"band": "fast",
"raw": "PING ws.support.github.com (140.82.113.22) 56(84) bytes of data.\n64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=1 ttl=44 time=31.3 ms\n64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=2 ttl=44 time=32.8 ms\n64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=3 ttl=44 time=31.3 ms\n64 bytes from ws.support.github.com (140.82.113.22): icmp_seq=4 ttl=44 time=32.8 ms\n\n--- ws.support.github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1504ms\nrtt min/avg/max/mdev = 31.311/32.062/32.813/0.742 ms"
},
{
"status": "finished",
"probe": {
"country": "SG",
"city": "Singapore",
"asn": 59253,
"network": "LeaseWeb",
"latitude": 1.29,
"longitude": 103.85,
"kind": "datacenter"
},
"resolvedAddress": "140.82.114.22",
"family": 4,
"rtts": [
225,
225,
225,
225
],
"min": 224.6,
"avg": 224.63,
"max": 224.66,
"jitter": 0,
"loss": 0,
"sent": 4,
"received": 4,
"band": "slow",
"raw": "PING ws.support.github.com (140.82.114.22) 56(84) bytes of data.\n64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=1 ttl=48 time=225 ms\n64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=2 ttl=48 time=225 ms\n64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=3 ttl=48 time=225 ms\n64 bytes from ws.support.github.com (140.82.114.22): icmp_seq=4 ttl=48 time=225 ms\n\n--- ws.support.github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1501ms\nrtt min/avg/max/mdev = 224.598/224.626/224.663/0.025 ms"
},
{
"status": "finished",
"probe": {
"country": "AU",
"city": "Sydney",
"asn": 31898,
"network": "Oracle",
"latitude": -33.77,
"longitude": 150.9,
"kind": "datacenter"
},
"resolvedAddress": "140.82.112.21",
"family": 4,
"rtts": [
200,
200,
200,
200
],
"min": 199.71,
"avg": 199.87,
"max": 199.99,
"jitter": 0,
"loss": 0,
"sent": 4,
"received": 4,
"band": "slow",
"raw": "PING ws.support.github.com (140.82.112.21) 56(84) bytes of data.\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=1 ttl=48 time=200 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=2 ttl=48 time=200 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=3 ttl=48 time=200 ms\n64 bytes from ws.support.github.com (140.82.112.21): icmp_seq=4 ttl=48 time=200 ms\n\n--- ws.support.github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 199.713/199.869/199.985/0.098 ms"
},
{
"status": "finished",
"probe": {
"country": "BR",
"city": "Sao Paulo",
"asn": 31898,
"network": "Oracle",
"latitude": -23.55,
"longitude": -46.64,
"kind": "datacenter"
},
"resolvedAddress": "140.82.112.22",
"family": 4,
"rtts": [
115,
114,
115,
115
],
"min": 114.39,
"avg": 114.52,
"max": 114.58,
"jitter": 0.67,
"loss": 0,
"sent": 4,
"received": 4,
"band": "good",
"raw": "PING ws.support.github.com (140.82.112.22) 56(84) bytes of data.\n64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=1 ttl=50 time=115 ms\n64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=2 ttl=50 time=114 ms\n64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=3 ttl=50 time=115 ms\n64 bytes from ws.support.github.com (140.82.112.22): icmp_seq=4 ttl=50 time=115 ms\n\n--- ws.support.github.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 1503ms\nrtt min/avg/max/mdev = 114.394/114.521/114.583/0.076 ms"
}
],
"summary": {
"asked": 5,
"ran": 5,
"answered": 5,
"median": 114.52,
"p90": null,
"fastest": {
"city": "Buffalo",
"avg": 32.06
},
"slowest": {
"city": "Singapore",
"avg": 224.63
},
"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": "2YJ8O58yGT9VmtHFe00021Vhi"
}Next step
- Traceroute and MTRPing says it answers. Where does the path slow down?Check ws.support.github.com in Traceroute and MTR
- Port checkerIs a service port open, not just ping?Check ws.support.github.com in Port checker
- Is it down?Is the website itself up, layer by layer?Check ws.support.github.com in Is it down?
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
- Enter a host or an addressA domain name such as
example.comor a public IP address such as1.1.1.1. A web address works too: only the host name is used. - 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
AS7922or a cloud region such asaws-us-east-1. - 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 see | What it usually means |
|---|---|
| One place far slower than the rest | The 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 place | Often harmless. One reply in four missing once is not a problem by itself. |
| Steady loss at several places | Congestion or a busy server. Try again in a few minutes and compare. |
| No reply anywhere | The 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 "https://lookupowl.com/api/v1/tools/ping?q=example.com&places=1&protocol=tcp"claude mcp add --transport http lookupowl https://lookupowl.com/mcp