Hi,
Considering this is about Google, I have just added google.com to our allow
list. I also added 8.8.8.8 and will add the IPv6 version too.
Cheers,
Johan
On Thu, 11 Jul 2024 at 13:56, Robert Kisteleki wrote:
> Hi,
>
> I understand your point and recognise this is inconvenient at the
>
Hi,
I understand your point and recognise this is inconvenient at the
moment. I'd say in the short term we can increase the limit - 25 is
just a number like any other :-) - and perhaps administratively close
the failing measurements. While I can't make promises about when, but
in the longer term
Hi Robert,
thanks for the clarification, now I know it is not a bug.
With that said, I think this necessitates some form of house-keeping task
seeing how long Atlas has been active.
I looked at the 25 running measurements (attached), assuming [0] is the right
request:
- 23 ping
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
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
> wrote:
>
> On 7/10/24 18:09,
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
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
:
>
> 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
