Educated guess: this is a limit for a total over all users? Op wo 10 jul 2024 om 07:09 schreef Malte Tashiro via ripe-atlas <ripe-atlas@ripe.net>:
Hi,
there seems to be something wrong (?) with the measurement creation process, or maybe some rules have changed?
I'm trying to schedule a toy measurement to google.com, however, as soon as I set the timing to periodic, I get the error message:
"We do not allow more than 25 concurrent measurements to the same target: google.com"
I am not running any measurements at the moment. This behavior is independent of the measurement type (ping, traceroute, SSL) and the number of probes (error appears with one probe requested). It seems to solely be a problem of the timing.
So far this message only appears for google.com and 8.8.8.8, other targets work. If I schedule the measurement in the future, I can actually submit it, but get a "Scheduling denied" measurement, for example: https://atlas.ripe.net/measurements/75418006/details
I don't know if this is related, but it seems like somebody is hammering Atlas with a large number of geolocation measurements (500 probes per measurement) and DNS lookups (1 probe) at the moment. In the last hour 5582 measurements were scheduled, which is 1.5 measurements per second!
Best, Malte -- ripe-atlas mailing list -- ripe-atlas@ripe.net To unsubscribe send an email to ripe-atlas-leave@ripe.net