Pagination

All Object List responses in the RIPE Atlas API are paginated. This prevents any single response from becoming excessively large and ensures consistent performance.

Page-Based Pagination

Pagination is controlled with two query parameters:

Parameter	Default	Maximum	Description
page	1	—	The page number to retrieve
page_size	50	500	The number of objects per page

For example, to fetch the first 3 measurements:

GET /api/v2/measurements/?page_size=3

Try it out

Navigating Results

Every paginated response includes navigation metadata:

{
  "count": 12345,
  "next": "https://atlas.ripe.net/api/v2/measurements/?page=2&page_size=50",
  "previous": null,
  "results": [ ... ]
}

Field	Description
count	The total number of objects matching your query (across all pages)
next	A full URL to the next page of results, or null if you are on the last page
previous	A full URL to the previous page of results, or null if you are on the first page
results	The array of objects for the current page

To traverse the full result set, follow the next link from each response until it returns null.

Tips

• Larger pages do not speed up the API. The server does the same amount of work regardless of page size. Smaller pages simply add more network round trips.
• Use count to estimate total pages. Total pages = ceil(count / page_size).
• Do not hardcode page URLs. Always follow the next and previous links provided in the response, as the URL structure may change.