Measurements

The Measurements group is the catalogue: RIPE's measurements with filters to narrow them down, a detail view for a single one, and the curated well-known set the rest of the platform leans on. All three are public.

Measurement list

/measurements · public

A paginated view of RIPE's measurement catalogue, read live. The dataset is on the order of 150 million rows, so the global list is a sanity check rather than something to browse — arrive with a filter in mind.

Filter by search, type, target and status, with a configurable page size. Those filters are applied by RIPE, not locally, so they work against the whole catalogue rather than the current page.

If a filter you expect isn't offered, that's deliberate: the form exposes only the filters RIPE actually honours. An unsupported filter would be silently ignored upstream and quietly give you wrong results.

Measurement detail

/measurements/detail · public

Look up one measurement by ID. Three tabs:

Details groups the record into cards:

• General — owner, type, target, current status
• Configuration — how the measurement is set up
• Schedule — interval, start and stop times
• Tags — including system-well-known-target when applicable

There is also an Open results JSON link, for when you want the raw data rather than the rendering.

Latest shows the most recent per-probe results. For ongoing measurements this is fetched live from RIPE; for measurements in a terminal status Atlas serves its own cached copy. That is why a stopped measurement loads faster than a running one — see Status, and why it decides everything.

DNS results are additionally decoded from the raw wire format into something readable, with the original preserved.

Map places the participating probes geographically — the fastest way to see whether a measurement's vantage points are where you assumed.

Well-known measurements

/measurements/well-known · public

The subset RIPE tags system-well-known-target: all-probes runs against well-known destinations. Same table as the measurement list, pre-filtered.

Two things distinguish this page:

• It is read entirely from Atlas's own store, with no fallback to RIPE. An hourly job discovers the set and re-caches the latest results, so the page is fast and never depends on the upstream being responsive.
• It is the set worth starting from. If you want a measurement to reason about — a baseline, a comparison, a known-good target — these are the ones everyone can read and that have been running long enough to be useful.

The trade-off is freshness: up to an hour old by design. For anything where that matters, use the detail view, which reads live.

Finding what a probe participates in

Coming at it from the other direction — "which measurements does this probe run?" — is answered on the Measurements tab of probe lookup, not here.

---

Background reading: Measurements · Data delay and freshness