IP Route Survey (IPRS)

IPRS is an initiative to continuously monitor IP-level routing across the internet. This is done through the regular collection of traceroute-style measurements from multiple vantage points towards a significant portion of the internet’s routable address blocks. The survey is conducted by the Dioptra research group at Sorbonne University’s LIP6 computer science laboratory.

As of December 2023, IPRS conducts four daily IPv4 snapshots featuring multipath route traces from ten vantage points towards all routable IPv4 /24 prefixes. So as to economize on M-Lab data storage, a subset of these measurements is being selected to be offered through M-Lab.

Please cite this data set as follows: M-Lab’s Sorbonne IPRS Data Set, <date range used>. https://measurementlab.net/tests/iprs

Any IPRS IPv4 snapshots that are not yet available through M-Lab can be obtained upon request from the Dioptra group.

In addition, IPRS conducts one daily IPv6 snapshot with single-path route traces towards a substantial number of routable prefixes. These, too, can be obtained upon request from the Dioptra group.

Data

We provide two series of data sets for the IPRS data.

The first, iprs_index1, consists of metadata. As mentioned, IPRS data consists of a series of snapshots of IP-level routing in the internet. Each snapshot is associated with a unique identifier, or UUID. The metadata data set includes, for each snapshot:

• its UUID
• its date and time
• whether it is present on M-Lab (if not, it can be obtained upon request from the Dioptra group)
• whether it contains IPv4 data, IPv6 data, or both
• additional metadata concerning the software versions that were used to obtain the snapshot, and their configuration

The second, iprs_data1, consists of the route trace data itself. The iprs1 schema is purposely compatible with the scamper1 schema that is used for M-Lab’s extensive existing Traceroute data set, so as to ease users’ ability to conduct queries across both data sets.

The differences between iprs1 and scamper1 are:

• An iprs1 route trace is not towards a single destination address, but towards a destination prefix (currently /24 prefix)
• iprs1’s id field allows IPRS data to be selected by snapshot, as indicated in the iprs_index1 table.
• For the following data types that call for an integer value, iprs1 uses the INTEGER data type whereas scamper1 uses FLOAT:
  • raw.CycleStart.ID
  • raw.CycleStart.start_time
  • raw.Tracelb.userid
  • raw.Tracelb.probe_size
  • raw.Tracelb.firsthop
  • raw.Tracelb.attempts
  • raw.Tracelb.confidence
  • raw.Tracelb.tos
  • raw.Tracelb.gaplimit
  • raw.Tracelb.wait_timeout
  • raw.Tracelb.wait_probe
  • raw.Tracelb.probec
  • raw.Tracelb.probec_max
  • raw.Tracelb.nodec
  • raw.Tracelb.linkc
  • raw.CycleStop.ID
  • raw.CycleStop.stop_time
• The following fields do not apply to IPRS data and are therefore left as NULL:
  • parser.Version
  • parser.Time
  • parser.ArchiveURL
  • parser.Filename
  • parser.Priority
  • parser.GitCommit
  • raw.Metadata.TracerouteCallerVersion
  • raw.Metadata.CachedResult
  • raw.Metadata.CachedUUID
  • raw.CycleStart.ID
  • raw.Tracelb.version
  • raw.Tracelb.userid
  • raw.Tracelb.start.Usec
  • raw.Tracelb.probe_size
  • raw.Tracelb.tos
  • raw.Tracelb.gaplimit
  • raw.Tracelb.wait_timeout
  • raw.Tracelb.wait_probe
  • raw.Tracelb.probec
  • raw.Tracelb.probec_max
  • raw.Tracelb.nodes.name
  • raw.Tracelb.nodes.q_ttl
  • raw.Tracelb.nodes.links.Links.Probes.Tx.Sec
  • raw.Tracelb.nodes.links.Links.Probes.Tx.Usec
  • raw.Tracelb.nodes.links.Links.Probes.Replies.Rx.Sec
  • raw.Tracelb.nodes.links.Links.Probes.Replies.Rx.Usec
  • raw.Tracelb.nodes.links.Links.Probes.Replies.icmp_q_tos
  • raw.CycleStop.ID
• Links do not include unresponsive hosts
• In the case of amplification (one probe receiving more than one reply), only one reply is retained, while raw.Tracelb.nodes.links.Links.Probes.Replyc indicates the total number of replies the probe received from this address.

If you wish to obtain IPRS data in other formats, or in greater detail, or additional data not published here, such as data obtained from IPv6 measurements, please contact the Dioptra team at Sorbonne University.

If you are interested in accessing IPRS data in BigQuery, please contact the M-Lab team!

Get more information at https://iprs.dioptra.io/

iprs_index1 Schema

iprs_data1 Schema

Example queries

The following query provides an overview of metadata for snapshots that have been published:

SELECT *
FROM `mlab-collaboration.sorbonne.iprs_index1`
WHERE is_published = true;

The following query fetches records from the iprs_data1 table, but only for snapshots that meet specific criteria in the iprs_index1 table.

Filtering Criteria:

• Timeframe: Includes snapshots taken in March 2025.
• Duration: Includes only snapshots lasting less than 2 hours.

SELECT *
FROM `mlab-collaboration.sorbonne.iprs_data1`
WHERE id IN (
SELECT id
FROM `mlab-collaboration.sorbonne.iprs_index1`
WHERE start_time BETWEEN “2025-03-01” AND “2025-03-30”
AND duration < 7200
);