The network path to a host — hop-by-hop — so a routing change is visible, not just a slowdown.
Every Traceroute monitor runs on the same spine as the rest of PulseTrace — probed from each region you pick, scored on every check, and streamed into one timeline where incidents open on their own, anomalies surface without a threshold to guess, and reports are generated for you. Point it at a target, choose an interval, and it's watched.
What each check verifies
The panel on the right is the real create-monitor screen — it fills itself in with a Traceroute example, exactly what you'd type.
For diagnosing where a path breaks or slows, not just whether it does: a regional latency creep, a transit provider change, a firewall that started dropping. Run it alongside an HTTP or ping monitor for the same host so an incident already includes the hop-by-hop picture.
Path to api.example.com from asia changed — 14 hops (was 9), +180 ms at hop 6 (transit provider change).