RIPE Atlas measurements failing

Hi everyone,

Since the past couple of weeks I have been trying to run a traceroute measurement with 50-100 random probes but almost all of them (~95%) of the probes do not report back. It was working fine July and early August. The same time happens with NTP measurements.

For the NTP measurements, I havent able to run a successful measurements till now. I even tried using only anchors for both NTP and traceroute.

Below is the measurement I was trying: Traceroute to 2 probes using 50 random probes each. Can anyone tell me if I’m missing anything?

{
“definitions”: [
{
“type”: “traceroute”,
“af”: 4,
“resolve_on_probe”: true,
“description”: “Traceroute measurement to 178.84.1.88”,
“response_timeout”: 4000,
“protocol”: “UDP”,
“packets”: 3,
“size”: 48,
“first_hop”: 1,
“max_hops”: 32,
“paris”: 16,
“destination_option_size”: 0,
“hop_by_hop_option_size”: 0,
“dont_fragment”: false,
“skip_dns_check”: false,
“target”: “178.84.1.88”
},
{
“type”: “traceroute”,
“af”: 4,
“resolve_on_probe”: true,
“description”: “Traceroute measurement to 145.94.58.54”,
“response_timeout”: 4000,
“protocol”: “UDP”,
“packets”: 3,
“size”: 48,
“first_hop”: 1,
“max_hops”: 32,
“paris”: 16,
“destination_option_size”: 0,
“hop_by_hop_option_size”: 0,
“dont_fragment”: false,
“skip_dns_check”: false,
“target”: “145.94.58.54”
}
],
“probes”: [
{
“type”: “area”,
“value”: “WW”,
“requested”: 50
}
],
“is_oneoff”: true,
“bill_to”: “****”
}

Hi,

Can you send me some measurement ID’s? That makes it easier to check. You can email them to me at jterbeest@ripe.net if you don’t want to share them publicy.

Thank you,

Cheers,
Johan
RIPE Atlas Team

Below is the list of all my failed measurements. The first 2 are the traceroute ones I said were not working. I have also mentioned the other ones that failed for more info.

My measurements:

  1. 78570000 (TRACEROUTE)
  2. 78569999 (TRACEROUTE)
  3. 78568403 (TRACEROUTE)
  4. 78568402 (TRACEROUTE)
  5. 78077401 (PING)
  6. 77199089 (NTP)
  7. 77160872 (NTP)
  8. 77160701 (NTP)