IP & Network

Network connectivity test

Enter one public hostname or IP. Confirm authorization, then run a single remote measurement.

Network connectivity test

Public hostname or IP

Only Run sends the target, mode and region to Globalping. Measurements may be public by ID and retained by that service; the probe is not your device.

Remote probe report

Enter a public host to begin.

Check options

Enter a public host to begin.

When your terminal can reach a site but someone in another region cannot, a network connectivity test from a remote probe gives a second vantage point. It does not measure the path from your own laptop.

Why use a network connectivity test from elsewhere

A named remote observer makes the result interpretable.

See where the answer came from

The network connectivity test puts the actual probe city, country and network beside the target and timestamp. Two probes may see different RTTs or timeouts; neither result is your local connection.

Two remote probe points take different paths to one public host, with different response indicators.

Separate ICMP from a TCP port

An unanswered ICMP ping can coexist with a TCP response on port 443. The network connectivity test keeps those methods distinct instead of declaring the whole site down.

One public host has no ICMP response but receives a successful TCP connection on a single port.

Read the observation before the verdict

01

Pick the path you mean to inspect

ICMP sends three packets. For a TCP port check, select one port; 443 is the default. Traceroute follows hops from a remote probe. The online ping test never starts on typing alone.

02

Choose a region, then verify the actual probe

Worldwide means one available probe, not measurements from every continent. North America, Europe and Asia filter the selection; the report shows the city and country that really ran it.

03

Interpret a timeout in context

A lost ICMP reply is not proof that a website failed. Compare the TCP result or online traceroute, and read per-hop asterisks as missing replies rather than an automatic broken route.

Three ways to inspect one public target

ICMP replies and packet loss

Three packets yield received count, loss percentage and min/average/max RTT where replies exist. A packet loss test from one remote probe is a sample, not a continuous availability monitor.

One TCP port, one observation

TCP port check attempts a connection to the chosen port. A reply supports reachability from that probe; it does not test HTTPS, credentials, or the application behind the socket.

Hop by hop route

Traceroute lists returned hops and response times. Missing intermediate replies stay visible, so an operator can compare later responding hops without treating one silent router as a dead end.

What this remote measurement cannot prove

Public targets only
This network connectivity test blocks obvious private, loopback and reserved IPs locally. Globalping checks final DNS resolution too; a browser alone cannot verify every CNAME destination.
No port ranges or repeated scans
One target and one TCP port are accepted per explicit run. There is no CIDR batch, continuous Ping, automatic retry or multi-probe sweep.
Probe time is not browser time
RTT is between the remote probe and the target. The page may stop waiting after 60 seconds, which does not mean the network packet itself timed out.
A reply has limited meaning
ICMP can be filtered while a website works. A TCP connection does not prove that its application is healthy; traceroute asterisks do not prove later hops are blocked.

Network connectivity test questions

Why does ping time out while the website still opens?

ICMP replies may be filtered while TCP 443 remains reachable. Try the single-port mode from the same remote region; that still checks a remote probe, not your browser’s path.

What does an asterisk in traceroute mean?

That hop did not return a reply within the probe’s wait. If later hops respond, traffic passed beyond it. An asterisk alone cannot identify a broken router.

Can ping test a port number?

Ordinary ICMP ping has no port number. Select TCP port check to attempt one TCP connection; it reports that method separately rather than calling it ICMP.

How are ICMP ping and TCP ping different?

ICMP asks for an echo reply. TCP mode tries a three-way handshake on your chosen port. Either can succeed while the other fails because firewalls and services handle them differently.

Does failed ping mean the website or internet is down?

No. One remote ICMP observation may reflect filtering, route policy or transient loss. Compare a TCP port and your own browser, then repeat only when you intentionally want another sample.

Need another observation explained?

Run another network connectivity test

A network connectivity test is most useful when you record the mode, actual probe and time alongside the RTT or timeout. Run again deliberately if you need a second sample.