This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] probe allocations
- Previous message (by thread): [atlas] probe allocations
- Next message (by thread): [atlas] probe allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gilles Massen
gilles.massen at restena.lu
Fri Nov 8 18:54:41 CET 2013
Hi Andreas, Thanks for clarifying. If its only a but (that gets fixed eventually) that's fine. And I'm not desperate about the credits yet ... Best, Gilles On 8/11/13, 16:40 , Andreas Strikos wrote: > Hi Gilles, > > normally every measurement is allocated equal or less (if we don't have > enough) probes than the user has requested. > In your case though, due a bug, your measurement got scheduled more than > once, so you got more than you requested. > If you are low on credits we could give you back the overcharge amount. > > Sorry for the inconvenience. > > Regards, > Andreas > > On 11/8/13, 3:46 PM, Gilles Massen wrote: >> Hi, >> >> I was wondering how the number of allocated probes is determined for a >> given UDM. Specifically, I set up a recurring UDM with 50 world-wide >> probes (DNS), but 110 probes were allocated to the test. While I'm >> certainly flattered that RIPE Atlas deemed the measurement so >> worthwhile, the credit consumption was somewhat higher than expected... >> so what is the logic, and am I able to get (at most) what I requested? >> >> best, >> Gilles >>
- Previous message (by thread): [atlas] probe allocations
- Next message (by thread): [atlas] probe allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]