Khipu Visualisation
Khipu is an interactive visualisation tool for exploring network measurement data from RIPE Atlas. It provides a hierarchical tree view of network paths, supporting traceroute, DNS, and ping measurements with multiple visualisation modes.
Khipu fullscreen ASN view example
Overview
Khipu transforms complex network measurement data into intuitive visual representations, allowing you to:
- Visualize network paths as interactive tree structures
- Explore data at different abstraction levels (IP, ASN, Country)
- Filter and analyze measurements based on various criteria
- Identify patterns, anomalies, and network characteristics
Supported Measurement Types
Traceroute
Displays the path packets take from source probes to destination targets, showing each hop along the route.
DNS
Visualizes DNS query paths and responses, showing the route to DNS resolvers and query results.
Ping
Shows ping measurement results in a simplified view, focusing on connectivity and response times.
View Modes
Khipu offers three distinct view modes for traceroute measurements, each providing different insights into your network data:
IP View
The most detailed view, showing individual IP addresses for each hop in the network path.
- Displays exact IP addresses at each hop
- Shows probe IDs or IP addresses for source nodes
- Reveals the complete routing path
- Best for detailed path analysis and troubleshooting
ASN View
Groups IP addresses by their Autonomous System Numbers, providing an organisational view of the network path.
- Consolidates IPs into their respective ASNs
- Shows AS names and numbers
- Identifies transit providers and network boundaries
- Useful for understanding routing policies and peering relationships
Country View
The highest level abstraction, grouping nodes by geographic location.
- Groups hops by country
- Uses country names or two-letter codes
- Visualizes geographic routing patterns
- Helpful for understanding regional connectivity and latency patterns
WARNING
NOTE: Khipu uses a combination of IPLocate, PeeringDB, and RIPE Registry sources to determine location, but no ip location system is perfect and there will often be errors, especially with CDNs and similar addresses.
User Interface
Toolbar Controls
Khipu toolbar in IP view
The Khipu toolbar provides comprehensive control over the visualisation:
Measurement Type Badge
Displays the current measurement type (TRACEROUTE, DNS, or PING) with colour coding:
- Teal for traceroute
- Light Blue for DNS
- Light Green for ping
View Mode Toggle (Traceroute only)
Switch between IP, ASN, and Country views using the button toggle.
Display
On wide screens the display options are shown inline under Display. On narrower screens they are collected in an Options menu.
- Success: tri-part button for showing All (default), Successful only, or Failed only
- Target: Display target node information (disabled for multi-target measurements)
- Probes (IP view): Toggle between showing probe IDs or IP addresses
- IP Labels (IP view): Toggle on to show IP labels on all nodes
- Group Unknown (ASN view): Group unknown intermediate ASN nodes together
- ASN Labels (ASN view): Show or hide ASN labels on all nodes
- Short Names (Country view): Use two-letter country codes instead of full names
Distance Mode (IP view only)
Choose how vertical distance is calculated:
- HOPS: Equal spacing based on hop count
- RTT: Spacing based on round-trip time for more accurate latency representation
Shared Hops (Traceroute IP and ASN views)
Choose how hops that several probes pass through are drawn. The two options are icon buttons; hover over them to see their names:
- Paths (default): each probe gets its own branch. A hop shared by several probes is drawn once per branch, so the picture is tidier, but the same address can appear more than once.
- Topology: every hop is drawn once and the probes that share it converge on it. This shows the real network structure. It is denser where routes interleave, and it keeps nodes in place during a time lapse.
Layout (Traceroute only)
Choose between radial or horizontal presentation of data. Unless the URL specifies a layout, a traceroute measurement with up to 250 paths opens in the horizontal layout. Larger ones open in the radial layout, which is easier to read at that size, and a message tells you so. Ping and DNS measurements are always shown radially.
Count
- Count: Displays the number of visible paths (changes as filters are applied)
View Controls
- Zoom In/Out: Adjust the visualisation scale
- Fullscreen: Enter or exit fullscreen mode for immersive viewing (Escape also leaves it)
- Time lapse (clock icon): open the time lapse controls. The button only appears for recurring traceroute measurements with 100 probes or fewer.
Until you zoom or pan, Khipu fits the whole visualisation to the canvas, and refits it whenever the filters change or the window is resized. Once you have zoomed or panned, it keeps your zoom level and position when you change the path, RTT or country filter, or resize the window. Changes that redraw the picture differently fit it to the canvas again: the view mode, the layout, the Success button, Group Unknown, and turning Short Names on.
Export
The export menu offers:
- Export Image:
- SVG (vector): sharp at any size, so you can zoom in on the file for detail
- PNG (picture): 3840 × 2160 pixels, for pasting into documents and chats
- Export Data: JSON (Filtered) or CSV (Filtered) for the current view with all filters applied, and JSON (All Data) or CSV (All Data) for all loaded measurements
While an export is being prepared, the export button shows a progress spinner.
Filtering Options
RTT Range Filter
Use the dual-handle slider to filter measurements by round-trip time:
- Drag handles to set minimum and maximum RTT values
- Shows "ALL" when maximum is reached
- Automatically disabled when showing only failed traces
INFO
NOTE: The RTT filter only applies to successful paths; failed traces are not affected by RTT range settings.
Path Filter
Search for specific elements in network paths:
- For traceroute: Filter by IP, ASN, IXP, or Probe ID
- For DNS: Filter by IP, ASN, RCODE, NSID, or answer data
- Separate terms with commas or Enter; each term becomes a chip
- Text terms match partially: for example, part of an IP address matches every address that contains it
- A term made only of digits (for example
3333) matches a probe ID or an ASN, never part of an IP address. Use theASprefix (for exampleAS3333) to search ASNs only. - Include/exclude filter button (shown once a term is entered):
- Include (tick icon, default): shows paths that match all terms
- Exclude (ban icon): hides paths that match any term
- Clear all terms with the clear button next to the include/exclude button
- Updates visualisation in real-time after debounce
- IXP names are searchable (e.g., "AMS-IX", "DE-CIX"), or one can type simply "ixp" to filter out all non-ixp routes.
- For traceroute, the keyword
errorkeeps paths with any error: a hop or packet the probe could not send, or an ICMP error a router answered with. Timeouts are not errors; use the Success button for those.error:<text>keeps paths with an error whose wording contains the text, in any case, for exampleerror:unreachable,error:never leftorerror:could not send. With Exclude,errorhides every path with an error. - For ping measurements with RTT verification, the keywords
validandinvalid(whether the RTT is plausible) andanomaly(all flagged results) are also available.impossible,suspiciousandunlikelyselect a single anomaly band.
Country Filter
Use the country filter menu to include or exclude specific countries:
- Click "All Countries" button to reveal country selection menu
- Filter by country name or by continent that selects all countries in that continent
- Search for any country
- Select All/None
- Invert selection
Interactive Features
Node Interaction
- Hover: View detailed information about any node in a popup
- Shows IP address, ASN, country, and RTT values
- Automatically detects and displays IXP membership with exchange name
- Anycast detection shown for identified anycast addresses
- Sources and targets that are RIPE Atlas anchors are labelled Anchor with an anchor icon and link to their probe page
- Multiple origin ASes: a warning triangle next to an ASN means the hop's prefix is announced by more than one origin AS. Hover over it to see all of them and which one Khipu shows. This is often sibling ASNs of one organisation, a customer and its provider, anycast or DDoS scrubbing, but it can also be a misconfiguration or a hijack.
- Routing loops: when a traceroute keeps returning to the same routers (at least two full laps), the looping node gets a red ! badge. Its popup names the routers in the cycle, the hops it spans, how many probes loop there, and whether the trace eventually continued past the loop.
- Click: Select nodes for persistent information display
- Drag: Pan the visualisation to explore different areas
- Scroll: Zoom in and out of the visualisation
Errors on a Path
A traceroute hop with no reply is a timeout, drawn as *. Sometimes the probe could not send a packet at all, and the result says why (for example "sendto failed: Network is unreachable"). Khipu shows these, and ICMP errors from routers, as errors rather than as timeouts:
- A hop the probe could not send for is labelled
×instead of*. Its popup says Could not send: with the probe's reason. - A trace that never left the probe: the probe's popup says Never left the probe: with the reason. If the probe reported no source address, as often happens when a probe without working IPv6 runs an IPv6 measurement, its node is named Probe followed by its ID, so it is still drawn.
- A trace that stopped partway: the probe's popup says Could not send (hop N): with the reason.
- Some packets of a hop not sent: when a hop answered but the probe could not send another of its packets, the probe's popup says Could not send some packets (hop N):, and so does the popup of that hop when it is the trace's last hop.
- In the probe's traceroute table, a hop the probe could not send for reads send error: with the reason, and a hop with some packets not sent shows × not sent next to its RTT (hover over it for the reason).
- ICMP errors: a reply carrying an ICMP error (for example "Network unreachable") shows ERR: and the error code next to the RTT in the traceroute table (hover over it for the meaning). The popup of a last hop lists them as ICMP Error N: followed by the meaning.
Use the error keyword in the path filter to find these paths.
Smart Popup Positioning
Popups for source nodes automatically position themselves to avoid obscuring important paths:
- Adjusts position based on node location and available space
- Maintains visibility of connected paths
Colour Legend
Khipu Traceroute Legend
Khipu DNS Legend
Access the colour legend through the info button (or if space allows it is auto expanded):
- Source nodes shown in blue
- Target nodes shown in green (Traceroute) or light blue (DNS and Ping)
- IXP nodes shown in pink (Traceroute only)
- Failed traces' last successful hops are shown in red, labelled Last Hop (Traceroute only)
- Intermediate nodes in gray/black (Traceroute only)
- Timeout hops (no reply) shown in yellow (Traceroute only)
- Unknown grouped ASN nodes shown in white with grey stroke (Traceroute, ASN view only)
- Anomalies are shown in orange (Traceroute RTT display mode only)
- RTT in ms with various color values (DNS and Ping only)
- Orange highlighting for selected/hovered paths and nodes
- Light grey lines show paths from the source nodes to the target (or last reached node in case of failure)
Navigation and Controls
Mouse Controls
- Hover: Display node information
- Click (node): Pin popup
- Click (whitespace): dismiss pinned popups
- Click + Drag (whitespace): Pan the view
- Click + Drag (pinned popup): Drag the pinned popup window
- Scroll Wheel: Zoom in/out
Time Lapse
For recurring traceroute measurements with 100 probes or fewer, the time lapse steps through earlier results so you can watch paths change over time. Click the clock icon in the View controls to open the time lapse panel. When the button is visible but greyed out, its tooltip explains why (for example, results are still loading). The button doesn't appear for ping or DNS measurements, one-off measurements, or measurements with more than 100 probes.

- Span: how far back to go, in frames. One frame is one measurement interval, and the span ends at the results currently shown. The span options are 24, 48 (default), 96 or 192 frames, shown as durations. They are limited to 7 days of data and to the time the measurement has been running.
- Playback: play/pause, previous and next frame, jump to the previous or next change, a frame slider, and the playback speed (0.5x, 1x or 2x).
- Changes: for each frame, the panel summarises how many probes changed path, with new and gone hops, plus probes with timeout-only changes, missing probes and probes that came back.
- Reading the picture: routes in the current frame are drawn normally, and routes from the previous frame are shown as faint "ghost" routes.
TIP
Switch Shared Hops to Topology before playing a time lapse. Each hop then keeps one fixed position and only the links change between frames, which makes path changes easier to follow.
Performance Features
Intelligent Caching
Khipu employs smart caching strategies to improve performance:
- Caches ASN lookups and country mappings RIPE NCC RIS
- Caches IXP information from PeeringDB
- Caches IP location information from IPLocate
- Stores processed measurement data
- Reduces API calls for repeated queries
Hardware leverage
- WebGL-based to use graphics hardware for best performance with large datasets
Progressive Loading
For large datasets:
- Initial render shows available data immediately
- Visual loading indicators during data processing
Single vs Multi-Target Visualisation
When Multiple Targets Appear
Khipu automatically detects and displays multiple targets when (all of the below):
- The measurement target is a domain name (not an IP address)
- DNS resolution was performed on each probe (not pre-resolved)
- The domain resolves to different IP addresses for different probes
This commonly occurs with:
- CDN endpoints (different IPs for geographic distribution)
- Load-balanced services (multiple backend servers)
Working with Multiple Targets
When multiple targets are detected:
- The "Target" display option is automatically disabled in the toolbar
- Each target node appears separately in the visualisation
- Hover over any target node to see its specific IP address
- Anycast addresses are automatically detected and labeled in the popup
- Path divergence to different targets is clearly visible in the tree structure
Single Target Measurements
For measurements with a single target:
- The target appears as a single node at the center of the tree
- The "Target" toggle in the toolbar controls its visibility (as well as clicking on the node itself)
- All paths converge to this single destination
DNS-Specific Features
When viewing DNS measurements, Khipu provides additional capabilities:
DNS Decoding
- Automatic decoding of DNS responses (abuf)
- Shows query types and response codes
- Displays resolver information
- Indicates DNSSEC validation status
Advanced Filtering
Once DNS decoding completes:
- Filter by specific query types (A, AAAA, etc.)
- Search for particular response codes
- Filter by resolver addresses
- Find specific domain responses
Tips for Effective Use
Analyzing Network Paths
- Start with IP view for detailed analysis
- Switch to ASN view to understand routing decisions
- Use Country view to identify geographic patterns
- Apply RTT filters to focus on performance issues
Identifying Issues
- Look for failed traces: the last hop that answered before a trace failed is shown in red
- Use the
errorpath filter to find probes that could not send, or that got ICMP errors - Check for routing loops (red ! badge) or unusual paths
- Compare RTT values across different paths
- Use filters to isolate problematic measurements
Optimizing Performance
- Use country filters to reduce visual complexity
- Hide successful traces when focusing on failures
- Adjust RTT range to focus on specific latency bands
- Toggle labels on/off based on analysis and needs
Sharing and Collaboration
URL-based Configuration
Khipu automatically saves all visualisation settings in the URL, making it easy to share your exact view with others:
- All view modes, filters, and display options are encoded in the URL
- Simply copy and share the URL from your browser's address bar
- Recipients will see exactly the same visualisation configuration
- No need to manually document or explain your settings
What Gets Shared
When you share a Khipu URL, the following settings are preserved:
- Selected measurement ID and type
- Current view mode (IP, ASN, or Country)
- All active filters (RTT range, path filter, country selections)
- Display options (successful traces, labels, distance mode)
- Layout (radial or horizontal)
- Shared Hops setting:
branchmode=truein the URL opens the Topology view (without it, Paths is used) - Fullscreen state
Common Use Cases
Troubleshooting Connectivity Issues
- Filter to show only failed traces
- Examine the last successful hop before failures
- Switch to ASN view to identify problematic networks
- Use path filter to find specific problem IPs or ASNs
Identifying Network Concentration Points
- Load your measurement data and switch to ASN or IP view
- Look for nodes with many converging paths (thick connection bundles)
- Hover over high-traffic nodes to see their details
- Use the path filter to isolate traces through specific concentration points
- Document critical bottlenecks for redundancy planning
Verifying Routing Policies and Prefix Acceptance
- Use the path filter to search for a specific interface or hop IP
- Filter traces that pass through your partner's network (ASN view)
- Check if your prefixes are being accepted and preferred
- Verify that expected routing paths are being used
- Compare actual paths with intended routing policies
- Document any discrepancies for configuration review
Focusing on Performance Issues
- Switch to IP view and enable RTT distance mode
- Use the RTT Range Filter to exclude well-performing traces (e.g., < 50ms)
- Focus on the remaining high-latency paths
- Identify common hops in poorly performing traces
- Switch to ASN view to see if specific networks are causing delays
- Create a prioritized list of performance bottlenecks to address
Investigating DNS Resolution
- Load DNS measurements
- Wait for automatic DNS decoding (if necessary, for large datasets)
- Use path filter to search for specific queries
- Analyze resolver distribution and response patterns
Geographic Routing Analysis
- Switch to Country view
- Enable short names for cleaner display
- Use country filter to focus on specific regions
- Identify unexpected geographic routing patterns
Other
- If the measurement is a periodic (vs one-off), you can use the time travel input at the top right of the page to view a different result (rather than the default latest result)
- To create a new ping or traceroute measurement and watch its results arrive live in Khipu, use the Multipath Visualisation use case. See Quick Measurements for details.