About the Traceroute Visualizer
Traceroute maps the responding hops between the buffer.lol diagnostics server and a public destination. It helps illustrate the route seen from the server side and where latency changes or non-responsive hops appear along that path.
How to use this tool
Enter a public hostname or IP address and run the trace. The request is validated before it reaches the restricted diagnostics worker. Read the hops in order from the worker toward the destination, and repeat the trace if you are investigating a transient route. A hostname trace may resolve to a different address over time because of DNS load balancing, anycast, or content delivery networks.
How to read the result
Each numbered row represents a hop that returned a traceroute response. Addresses or resolved names can identify networks along the path, while timing values approximate the response delay for that probe. Asterisks or missing hops do not automatically indicate failure: routers often filter or deprioritize traceroute traffic while continuing to forward ordinary traffic. A persistent jump that continues through later hops is more meaningful than one slow intermediate response.
Limits and privacy
The trace begins at buffer.lol's server, not at your browser, home router, or office network. It therefore cannot diagnose the first mile of your own connection. Routes can be asymmetric, and the return path may differ from the displayed outbound path. Firewall rules, MPLS, tunnels, load balancing, and ICMP filtering can hide or rearrange details. Use only destinations you are authorized to inspect; submitted targets are processed by the diagnostics service.
Common questions
- Why do some traceroute hops show no response?
- Many routers filter or rate-limit traceroute replies. A missing intermediate response does not mean the router stopped forwarding normal traffic.
- Does this show the route from my device?
- No. It shows the route from the buffer.lol diagnostics server to the destination.