Hi, Indeed, this is a global maximum against each target. We have two major reasons for this: * some targets can stand "any amount" of measuring, but most can't / shouldn't have to * once there are $thismany measurements against a particular target, there's a good chance the new ones are redundant and results from existing ones can be reused. Granted, this is not *always* the case. Technically this is just a configuration variable, we can change it. We can also add IPs / prefixes on a "bring it on!" list (allowlist). We also have a feature request to put entire ASNs on this list. In the meantime, I'd encourage you to look at the currently running measurements, to see if you can use their data. Regards, Robert On Wed, Jul 10, 2024 at 12:45 PM Ernst J. Oud <ernstoud@gmail.com> wrote:
Same is true for 9.9.9.9 and others, too many measurements already running against that target. I reckon RIPE does not want to be accused of spamming/ddos so there is a maximum.
Regards,
Ernst J. Oud
On 10 Jul 2024, at 11:55, Malte Tashiro via ripe-atlas <ripe-atlas@ripe.net> wrote:
On 7/10/24 18:09, Mark Santcroos wrote:
Educated guess: this is a limit for a total over all users?
I am aware of the quotas described here [0], which describe the 25 measurement limit, but I understood them to be per user. If not, somebody could easily prevent others from performing measurements to a destination by scheduling 25 period measurements with one probe and an interval of a week or so.
Btw. I had also two other users confirm to me that they have the same problem.
[0] https://atlas.ripe.net/docs/getting-started/user-defined-measurements.html#q... <OpenPGP_0x7D82498BEF2E08F8.asc> -- ripe-atlas mailing list -- ripe-atlas@ripe.net To unsubscribe send an email to ripe-atlas-leave@ripe.net -- ripe-atlas mailing list -- ripe-atlas@ripe.net To unsubscribe send an email to ripe-atlas-leave@ripe.net