RIS Peer Count
This endpoint provides information on the number of peers as seen by RIS, the RIPE NCC's Routing Information Service. The endpoint supports history and each data point is aligned to the RIS RIB dump times (every 8 hours starting from midnight each day). Additionally the data shows the number of full-table peers with paramters to change the threshold (per address family).
/data/ris-peer-count/data.json
Parameters
| Key | Value | Info | Required |
|---|---|---|---|
| starttime/endtime | ISO8601 or Unix timestamp | Defines the start and end time for the query window | No - by default it will return the latest available data point (either 00:00, 08:00 or 16:00 UTC) |
| v4_full_prefix_threshold/ v6_full_prefix_threshold | digit | Defines the thresholds (IPv4 and IPv6) used to calculate the number of full-table peers. | NO - default are returned in the output. |
Data Output
| Key | Info | ||||||
|---|---|---|---|---|---|---|---|
| peer_count | Groups the address families. Each group item ("v4" or "v6") has the following structure:
| ||||||
| v4_full_prefix_threshold/ v6_full_prefix_threshold | Reflects the thresholds that are used for the calculations of the full-table peers. Both (IPv4 and IPv6) are the number of prefixes a peer needs to send before it is considered a full-table peer. | ||||||
| starttime / endtime | Reflects the start and end time for the query window of the result. |
Code Examples
bash
curl --location --request GET "https://stat.ripe.net/data/ris-peer-count/data.json"js
const requestOptions = {
method: 'GET',
};
fetch("https://stat.ripe.net/data/ris-peer-count/data.json", requestOptions)
.then(response => response.text())
.then(result => console.log(result))
.catch(error => console.log('error', error));