Create a ping or traceroute measurement using the RIPE Atlas API
domain: ripe.net · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an API key at atlas.ripe.net/keys tied to your RIPE NCC Access account, with fine-grained permissions no broader than your own account's.
Send it as the Authorization: Key <key> header on all measurement-creation calls; missing/invalid/expired/disabled keys return 403.
POST to https://atlas.ripe.net/api/v2/measurements/ with a body containing at least one definitions[] entry (target, type such as ping or traceroute, af for IPv4/IPv6, description) and at least one probes[] entry (selection by type such as area, country, asn, or probes, plus a value and requested count).
Combine multiple probes[] entries as needed, remembering probe sets are additive across entries, not an intersection/filter.
Read the returned measurement IDs from the measurements array in the response, in the same order as your definitions.
Known gotchas
Probe selections across multiple probes[] entries are additive — asking for 10 worldwide plus 5 in NL gives you all 15, not a filtered subset.
Global fields like start_time/stop_time only apply to definitions that don't set them explicitly — per-definition overrides are silent and easy to misconfigure in a batch.
Measurements consume account credits tied to RIPE Atlas's probe-hosting/credit system — check your credit balance before scripting large or recurring measurement creation.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?