Can I enter a domain instead of an IP?

Yes, the domain is resolved to an IP and traced as usual.

Why are some hops shown as “*”?

Some routers do not answer such requests — this is normal.

Why does a trace take longer than usual?

It depends on the route length: the more hops and the slower they answer, the longer the check.

How is a trace different from ping?

Ping checks only the final server, a trace checks every hop on the way to it.

Why does the last hop not respond?

The server may block such requests with a firewall while the website on it works fine.

Where is the trace run from?

From a PSB server — so you see the route from the internet to the target, not from your computer.

How long does the check take?

Usually 10 to 60 seconds depending on the route length.

IP Tracer Online

Trace an IP: see the path to a server step by step — which nodes the request passes, with latency and loss on each. It shows where speed is lost.

Check result

What the IP tracer shows

A short note on every field of the result. Details are in the sections below.

Route hops

Which networks the request passes

RTT latency

The response time of every hop

Loss

Where packets do not get through

Hop country

Which countries the route crosses

Domain or IP

Either works

Export

Download the result as .csv

Trace IP: how to run a trace online

1
Enter an IP address or domain.
2
Click “Trace”.
3
See the route hops: address, host, country, loss and latency on each.
4
Download the result as .csv if needed.

How tracing works

Every packet has a TTL counter — how many hops it can pass. Each router decreases it by one, and when it reaches zero, the router drops the packet and tells the sender.

The trace sends packets with TTL 1, 2, 3 and so on. First the first router replies, then the second — building the chain of hops to the server with the latency of each.

IP tracer: how to read the result

Column	Meaning
#	The hop number on the path from our server to the target
IP / Host	The router address and its name, if any
Location	Where the hop is — shows which countries the route crosses
Network	The ASN and provider that own the hop
RTT	Round-trip time to the hop, in milliseconds
Loss	The share of packets the hop did not answer

Typical patterns

What you see	What it means
“*” on one hop, everything fine after it	The router does not answer such requests — no problem
Latency jumps at one hop and stays high to the end	A slow segment — this is where speed is lost
Loss on an intermediate hop, but not after it	The router rate-limits replies — it usually does not affect traffic
Loss from a certain hop to the end	A problem on that network segment
The route stops, only “*” after it	The server is unreachable or blocks such requests

Tracing from your computer

You can also run a trace locally — then you see the route from your own connection:

Terminal

Windows:        tracert psbproxy.io
macOS, Linux:   traceroute psbproxy.io

The online trace shows the route from our server. Comparing the two routes helps find where the problem is — at your ISP or further away.

Trace and ping

Ping shows latency and loss only to the final server. A trace shows the same for every hop on the way. If ping shows a problem, the trace helps find the segment.