ForceVPS Network Tools

Online Traceroute for Websites and Servers

Use ForceVPS Online Traceroute to analyze the network path to websites, servers, and internet resources. The tool displays every intermediate hop, helps identify routing issues, detect high-latency segments, and troubleshoot connectivity problems over IPv4 and IPv6.

6 quick targets
4 launch POPs
64 max hops supported
Resource Traceroute Live Route ForceVPS agent
Launch POP
IPv4 / IPv6
Hop path
Traceroute request

Run a Real-Time Traceroute Test

Analyze the route to any website or server using ForceVPS Online Traceroute. Select a network location, configure the test parameters, and receive detailed hop-by-hop results in real time.

Quick resources
Traceroute target
Launch node
Protocol
Traceroute options
Primary settings
Output options
The agent response or transport error will appear in the console on the right.
CLI

Result console

Target forcevps.com
Node Kyiv, Ukraine
Protocol IPv4
$ lg traceroute --node kyiv --family ipv4 --max-hops 16 --wait 2 --compact forcevps.com traceroute to forcevps.com, 16 hops max 1 edge-gw.kyiv.forcevps 0.42 ms 0.39 ms 0.41 ms 2 core-link.kyiv.forcevps 2.14 ms 2.09 ms 2.08 ms 3 forcevps.com 18.42 ms 18.31 ms 18.27 ms

FAQ

Traceroute is a network diagnostic tool that shows the path packets take from the selected test location to a specified domain or IP address. It helps identify intermediate network hops, measure latency, and locate sections of the route where connectivity problems may occur.
Enter a domain name or IP address, select a test location, and configure the available test parameters. After the online Traceroute starts, it will display the sequence of network hops and the response time at each stage of the route.
A hop is a router or another network device that packets pass through on their way to the destination server. Each row in the Traceroute results represents a separate stage of the route and usually includes the hop's IP address and response time.
Asterisks or a Request timed out message mean that a network hop did not answer the test request within the allowed time. This does not always indicate a problem: the router may block or limit ICMP responses while continuing to forward transit traffic normally.
Look for the hop after which latency increases sharply, timeouts begin, or the destination stops responding. If the increased latency continues across all subsequent hops, the issue may be located in that section of the route. A single slow hop followed by normal results usually does not indicate a fault.
The route depends on the test location, internet provider, BGP routing, peering agreements, and current network conditions. Traffic to the same server can therefore pass through different network hops and have different latency when tested from different countries or networks.
ICMP, UDP, and TCP packets may be handled differently by network equipment and firewalls. Certain protocols or ports may be blocked, rate-limited, or routed differently, so changing the protocol can help diagnose server availability and network connectivity problems more accurately.

Powered by WHMCompleteSolution