See the path packets take from each region to your server
Enter a target to test from multiple regions
Traceroute
Traceroute path
| Hop | IP address | PTR | Location / ISP | AS | Packet loss | Last (ms) | Best (ms) | Worst (ms) |
|---|---|---|---|---|---|---|---|---|
| 疑似 | ||||||||
| 正在探测第 跳,链路尚未追踪完成,请等待「接收中」消失 | ||||||||
Test overview
Route overview
Packet loss distribution
Latency distribution (responding nodes)
Reading a traceroute
Traceroute lists the hops toward a destination. Compare the latency and loss at each hop with the final destination to see where a problem persists.
Traceroute records every hop between a test node and the destination, with the IP, location, network operator, latency and loss for each hop. When ping shows high latency but not where it comes from, traceroute is the tool that pinpoints the segment.
Look for the hop where latency jumps and stays high for every following hop; that is where the problem starts. A single slow hop followed by normal hops only means that router deprioritizes probe replies. For traffic between China and other countries, the cross-border hops show whether a route uses a premium path such as CN2 GIA or a congested international exit.
Frequently asked questions
Does loss at one hop indicate an outage?
Intermediate routers may rate-limit probe responses. If subsequent hops and the destination respond normally, that isolated loss is usually a response policy.
A hop shows a timeout or asterisk. Is the network down?
Usually not. Many routers do not answer TTL-exceeded probes, so they appear as asterisks. If later hops and the destination respond, the path works. Only when every hop from one point to the destination times out is the path actually broken.
Why does latency not increase hop by hop?
Each hop measures the full round trip from the source to that router, and routers give probe replies different priority. A slow hop followed by a faster one is normal rate limiting and does not affect forwarding.
What is the difference between traceroute and MTR?
Traceroute probes each hop a few times and gives a snapshot. MTR keeps probing and reports loss and latency statistics per hop, which makes intermittent problems easier to find.