Latest Measurement Results

Location

The latest measurement results endpoint can be found here:

GET /api/v2/measurements/2000000/latest/?probe_ids=10006

Much like the other similar API URLs, this one works by inserting a single measurement ID to return JSON data.

Output Format

The output format is only slightly different from what you'd expect from the standard measurement result API call. Rather than simply dumping every result as a list, it returns a series of key/value pairs in the format:

    {
      probe_id: [<result>],
      probe_id: [<result>],
      ...
    }

This allows you to easily fetch the latest result from probe 123, for example, by using:

my_data["123"][0];

Versioning

In case you're wondering why the format is probe_id: [<result>] and not simply probe_id: <result>, this is due to the fact that you can request up to 10 previous result values for every probe by specifying versions=n, where n is a number between 1-10:

https://atlas.ripe.net/api/v2/measurement-latest/<measurement-id>/?versions=1

{
  probe_id: [<result>],
  probe_id: [<result>],
  ...
}

https://atlas.ripe.net/api/v2/measurement-latest/<measurement-id>/?versions=2

{
  probe_id: [<result>, <result>],
  probe_id: [<result>, <result>],
  ...
}

The versions will always be returned in reverse chronological order, so requesting my_data["123"][0] will always be the most recent result, and my_data["123"][1], the second-most recent.

Filtering

You can also do basic filtration by probe id simply by using probe_ids=probe_id,probe_id as query parameters.

Note, however, that if you specify a probe ID that is not part of the measurement, you'll simply get back an empty set.

Caching

Presently, the API is cached at 5 minutes, i.e. the information returned from this URL might be 5 minutes behind the actual state.