A new web-based traceroute visualization tool has launched, promising to help network administrators and security researchers visualize network paths with geographic mapping. The tool supports standard traceroute, flyingroutes, and MTR output formats, automatically detecting users' IP addresses as starting points and displaying interactive maps showing packet routes across the internet.
However, early user testing has revealed several significant compatibility and functionality problems that are limiting the tool's effectiveness.
Key Features:
- Automatic IP address detection for starting point
- Geographic location mapping via ipinfo.io API
- Internet Exchange Point (IXP) detection with PeeringDB API
- Interactive map visualization
- Protocol-specific timing analysis
- Packet loss highlighting for MTR data
Browser Security Features Block Core Functionality
The most critical issue affecting users is compatibility with modern browser security features. Firefox's Enhanced Tracking Protection is blocking calls to the ipinfo.io API, which the tool relies on for geographic location data and ISP information. This means users cannot see location details or ISP data without disabling their browser's security protections - a concerning requirement for a network analysis tool.
Additionally, security scanning services initially flagged the site as phishing, though this classification was later updated to computer and internet info after review.
IPv6 Support and Geolocation Accuracy Concerns
Users are reporting fundamental functionality gaps, particularly with IPv6 support. When the tool auto-detects an IPv4 address but the actual traceroute runs over IPv6, results fail to display properly. This creates a significant blind spot given the increasing adoption of IPv6 networks.
The accuracy of IP-based geolocation has also drawn skepticism from users. While the underlying concept of triangulating router locations through multiple reference points and latency measurements is technically sound, real-world results appear inconsistent. Some users report seeing large gaps in their traceroute paths, with the tool showing their IP address followed by 13 skipped hops and then 10 unknown entries.
Reported Issues:
- Firefox Enhanced Tracking Protection blocks ipinfo.io API calls
- IPv6 traceroutes not supported when IPv4 auto-detected
- Initial security flagging as "phishing" site
- Inconsistent geolocation accuracy
- Missing hops in traceroute visualization
- Limited mobile interface functionality
Mixed Reception Despite Technical Promise
Despite these issues, the tool has received positive feedback for its core concept and visualization approach. The interactive mapping feature and support for multiple traceroute formats represent valuable additions to the network analysis toolkit.
I love more tooling and attention given to latency. Throughput gets the attention but latency is what drives a high quality experience
The tool's ability to identify Internet Exchange Points (IXPs) and display protocol-specific timing information from flyingroutes output demonstrates sophisticated network analysis capabilities when functioning properly.
Supported Input Formats:
- Standard traceroute output
- Flyingroutes with protocol breakdown (ICMP, UDP, TCP timing)
- MTR output with packet loss and timing statistics
Mobile Experience Needs Improvement
Mobile users have suggested adding sample data to showcase the tool's capabilities, indicating that the current interface may not effectively demonstrate its features on smaller screens. This represents a missed opportunity to engage users who want to quickly understand the tool's value proposition.
The combination of browser compatibility issues, IPv6 support gaps, and geolocation accuracy problems suggests the tool needs significant refinement before it can serve as a reliable resource for network professionals. While the underlying concept shows promise, addressing these fundamental technical barriers will be essential for broader adoption.
Reference: Traceroute Visualizer
