Summary

  • Region Meshes runs a monthly RIPE Atlas traceroute mesh across the public probes in a country or defined region. Its displayed, annotated dataset selects up to 50 probes spread across different networks.
  • The unselected probe results remain in the underlying measurements. The grid, map and flow views reveal paths and exchange use; their lines count observed traceroutes, not traffic volume or every route in the region.

A country on screen has a guest list

Ask whether Internet paths inside a country stay inside it, and the answer can turn into a very persuasive picture. Green paths, blue paths, a neat flow diagram: the screen seems to settle an argument that network engineers could spend weeks picking apart. The clever part of Stephen Suess’s work is that RIPE NCC publishes enough of the machinery to let the reader pick it apart too.

In Suess’s account of Region Meshes, RIPE Atlas schedules a new round at the start of each month. Within a country, or an agreed multi-country region with enough probes, every public probe traceroutes toward every other public probe. Datasets have been generated monthly since February 2026 for selected regions. This is a measurement of paths between vantage points, with IPv4 and IPv6 chosen separately; it is not a meter on every customer’s traffic.

The RIPE Atlas documentation then reveals the editorial cut in the data. Up to 50 probes are selected for the enriched visualisation, favouring diversity across networks. A region with fewer public probes uses all of them. The remaining measurements stay available through RIPE Atlas, but their paths do not receive the same per-hop ASN, reverse DNS, exchange and location annotations. The full cast was measured; the close-ups went to 50. That is a sensible way to make a screen readable, and a crucial fact about what the screen shows.

Suess’s interface gives those selected paths three jobs. The grid puts probe pairs in cells that can open a full traceroute. The map draws arcs between vantage points and marks exchanges. The flow diagram groups source and destination ASNs around path categories; the width of a link is the number of measured paths, not gigabits. A thick band is a count of traceroutes in this selection. It cannot tell a network operator how much paid traffic took that road.

There is another choice behind the colours. The default view relies on known IXP and probe locations. Switch off “IXP data only” and the picture adds reverse DNS and IP-geolocation clues, which RIPE NCC says can put infrastructure in the wrong country. The more detailed map can therefore be less certain about a particular hop. The tool exposes both the switch and the underlying traceroute; a reader who sees a dramatic border crossing has a place to check before declaring one.

RIPE NCC identifies Suess as the specialist frontend developer responsible for RIPE Atlas visualisations. Its named photograph grounds this article’s editorial portrait. His contribution here is an interface that makes local routing visible while leaving its selection rule and raw measurements in reach. The best maps do not merely draw a line; they tell you who held the pencil and which points were on the page.