All tools

Global Ping & TCP Port Checker

See how your server responds from 12 rarecloud.io locations.

Network powered by rarecloud.io

An address runs ICMP ping. Add :22, :443 or another port to test TCP connectivity.

Europe
USA
Asia
0 locations selected

Results by location

Ready

Live ping or TCP measurements from rarecloud.io locations. Latency in milliseconds.
LocationStatusSentLoss %LastAvgBestWorstStDevHistoryRoute
Europe
🇬🇧 LondonUnited Kingdom · rarecloud.ioOffline———————
🇩🇪 FrankfurtGermany · rarecloud.ioOffline———————
🇳🇱 The HagueNetherlands · rarecloud.ioOffline———————
🇷🇴 TimișoaraRomania · rarecloud.ioOffline———————
🇷🇴 ConstanțaRomania · rarecloud.ioOffline———————
🇷🇴 BucharestRomania · rarecloud.ioOffline———————
USA
🇺🇸 Silicon ValleyUSA · rarecloud.ioOffline———————
🇺🇸 DallasUSA · rarecloud.ioOffline———————
🇺🇸 Phoenix, ArizonaUSA · rarecloud.ioOffline———————
🇺🇸 New York / New JerseyUSA · rarecloud.ioOffline———————
Asia
🇯🇵 TokyoJapan · rarecloud.ioOffline———————
🇭🇰 Hong KongHong Kong · rarecloud.ioOffline———————

Latency in ms. TCP latency measures connection setup; failed connections are not an ICMP packet-loss measurement.

One target. Twelve perspectives.

Each selected location tests the same resolved IP. Routes and filtering can differ between networks. Tests use IPv4.

Read the TCP result

Successful: connection established. Refused: actively rejected. Timeout: no connection within 3 seconds. An open port does not verify TLS or application health.

Test server connectivity from multiple locations

Use global ping to investigate a server that responds in one region but fails in another. Each rarecloud.io node measures the same destination from its own network, so you can compare routing, latency and reachability across Europe, the USA and Asia.

Enter example.com for ICMP ping or example.com:443 for a TCP port check. Hostnames are resolved to one IPv4 address before the run. If a domain uses a CDN, this tests the chosen address and does not measure regional DNS selection.

How to use global ping and TCP port checks

  1. Enter a public IPv4 address or hostname. Add :443, :22 or another port for a TCP test.
  2. Select the locations you want to test from and click Start test.
  3. Compare live status, latency and loss or failed connections. Use Stop test to end the run early.
  4. Open MTR for a location to inspect its route, or export the results as JSON.

Understand latency, loss and port accessibility

Last, Avg, Best and Worst show latency in milliseconds. StDev describes how much successful measurements vary. ICMP measures echo round trips; TCP measures connection setup time.

Loss % is the proportion of ICMP attempts without a successful reply. In TCP mode, Failed % reports unsuccessful connection attempts. A refused connection is a response, so it should not be interpreted as an ICMP packet-loss measurement.

For a complete diagnosis, check DNS records, inspect the TLS certificate and verify the HTTP response. Use IP WHOIS to identify the network owner.

Frequently Asked Questions

What does a global ping test measure?

It sends ICMP echo requests from multiple locations to the same IPv4 address. The results show reachability, round-trip latency and packet loss from each location, helping you identify regional connectivity differences.

Can I test a domain name instead of an IP address?

Yes. Enter a hostname such as example.com. The tool resolves an IPv4 address once and uses that same address for all locations. The resolved address appears above the results. It does not compare DNS responses between regions.

How do I check whether port 22 or 443 is open?

Enter a hostname or IPv4 address followed by a colon and the port, for example example.com:443. Each selected location attempts a TCP connection to that port. You can test one port per run, between 1 and 65535.

What do Successful, Refused and Timeout mean?

Successful means a TCP connection was established. Refused means the connection was actively rejected, often because no service is listening or a firewall rejects it. Timeout means no connection was established within three seconds; filtering, loss and an unavailable target are possible causes.

Why does ping fail while a TCP port works?

A firewall or host can block ICMP echo requests while allowing TCP connections. Test the service port to distinguish ICMP filtering from a service connectivity problem. Failed TCP connections are reported separately from ICMP packet loss.

Does a successful port 443 test mean the website is working?

It confirms TCP connectivity only. It does not validate the TLS certificate, HTTP response or application health. Use the SSL Checker and Website Status tools for those checks.

What does packet loss at an intermediate MTR hop mean?

Routers may limit or ignore diagnostic replies while forwarding traffic normally. Loss at an intermediate hop alone does not prove forwarding loss. Compare it with later hops and the destination before drawing conclusions.

Which locations and IP versions are supported?

The tool currently supports IPv4 from London, Frankfurt, The Hague, Timișoara, Constanța, Bucharest, Silicon Valley, Dallas, Phoenix, New York / New Jersey, Tokyo and Hong Kong. Only available locations can be selected.

How long does a test run?

A standard run makes ten attempts per location, five seconds apart. Results arrive as each location responds. You can stop early, export the current results and run another test. MTR is a separate bounded route test.