Measurements toward prefixes controlled by the PEERING testbed

RIPE Atlas runs frequent measurements toward prefixes controlled by the PEERING testbed (specified under the RS-PEERING-TESTBED route set in the IRR). The measurements have a description of "PEERING Testbed route monitoring".

We have 48 teams of 400 Probes that run traceroute to target{team}.atlas.peering.ee.columbia.edu every 20 minutes. This high frequency is useful in tracking route convergence after PEERING experiments change BGP announcements. The traceroutes use only 1 packet per hop to reduce load (the default is 3).

Impact considerations. The configuration uses approximately 14M credits/day and generates 1.4M measurement results/day. We include each individual Probe in at most 4 teams, which would limit the measurements' probing rate from each Probe to (4 teams * 72 traceroutes/day * 20 packets/traceroute = 4 packets/minute). A Probe's gateway would receive 12 TTL-zero packets/hour. All measurements are towards PEERING-controlled prefixes, and should not raise complaints from our upstreams.