Ping and Latency Checker

This is a TCP ping (connection test) from the StackAtlas server — helpful when ICMP ping is blocked.

Host 443 Ready

HostDomain or IP

PortTCP

Packet loss

—

Received: —

Avg latency

—

Min/Max: —

Address used

—

Resolved: —

Raw response (JSON)

How to use it

Enter a host (domain or public IP).
Choose a port for the service you expect (common: 443 for HTTPS).
Click Ping to run multiple attempts.

What this measures

TCP connect latency (not ICMP echo).
A timeout can mean a firewall is filtering traffic, or the host is unreachable.
Results depend on where this server runs (not “from your computer”).

Common targets

Website / API:443

Try HTTPS first

Web (legacy):80

Often redirects to HTTPS

SSH server:22

Remote admin

Database:5432

Postgres example

How it works

Sends multiple TCP connection attempts from the StackAtlas server to your host and port, then reports loss and latency stats. Useful when ICMP ping is blocked.

Results reflect server-to-host path, not your local network.
Private/local addresses are blocked for safety.

Quick examples

HTTPS check

example.com :443 • 4 attempts

Loss 0% • Avg 82 ms

SSH blocked

ssh.server.test :22 • 3 attempts

Timeout/blocked • Loss 100%

Use quick ports to match the service you expect.

Mini FAQ

Is this ICMP ping?

No, it is a TCP connect test; some hosts allow TCP when ICMP is blocked.

Why am I seeing timeouts?

Firewalls, closed ports, or rate limits can drop the connection.

Should I change timeout/interval?

Longer timeouts help slow links; shorter intervals reveal jitter faster.