Hi,

(I understand there were many more messages about this recently, somewhat skipping ahead...)

I executed these just now against the same target(s), and results look good:
https://atlas.ripe.net/measurements/118369580
https://atlas.ripe.net/measurements/118370167

If I understand correctly things changed on the server side as well, but I'm not 100% sure we can conclude the issue was there to begin with? If so, we can work together and do some controlled experiments - observing closer what the probes get and whether they pass those results along. There is a chance we could improve handling of bad responses, or perhaps there's a bug that eats up good but unexpected responses.

Cheers,
Robert

On 10-07-2025 18:01, Marco Davids (SIDN) via ripe-atlas wrote:
> Dear list,
>
> If anyone knows, or is able to figure out, why most (but not all) Atlas
> probes don’t report results for NTP measurements to ntp0.testdns.nl, I’d
> appreciate your insights.
>
> Examples:
>
> https://atlas.ripe.net/measurements/116922622/
>
> https://atlas.ripe.net/measurements/116946257/
>
> https://atlas.ripe.net/measurements/116830921/
>
> Ping works:
>
> https://atlas.ripe.net/measurements/116921717/
>
> Thanks in advance.
>
>
> -----
> To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
> As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
> More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/