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/ripe-atlas@ripe.net/
[atlas] Bug on credit expenditure?
- Previous message (by thread): [atlas] Bug on credit expenditure?
- Next message (by thread): [atlas] Liquid Web (Phoenix, US) has joined RIPE Atlas Anchors.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Fri Dec 19 11:11:26 CET 2014
The cost estimation should be ok now. /vty On 12/16/14, 9:45 AM, Viktor Naumov wrote: > Hi Sebastian, > > You're right indeed. I'm tracing the cost estimation routines at this > moment. The fix will be out there shortly. > I will keep you updated. > > Thank you! > > /vty > > On 12/14/14, 10:28 PM, Sebastian Castro wrote: >> Hi: >> >> I've created 12 one-off traceroute measurements today, each measurement >> requesting 38 probes. According to the results page, the number of >> credits per measurement is 60, at 38 probes, we got 2280 credits. >> >> Any further attempt to create new measurements returned error 104: >> "Executing this measurement request would violate your maximum daily >> spending limit of 2200000.0 credits" Unless my math is horribly wrong, >> or the message is incorrect, I'm well under the 2.2 million credits >> daily limit. >> >> Is there a bug somewhere that's miscounting the usage of credits? I have >> enough credits in my account to pamper myself with measurements :) >> >> Cheers, > >
- Previous message (by thread): [atlas] Bug on credit expenditure?
- Next message (by thread): [atlas] Liquid Web (Phoenix, US) has joined RIPE Atlas Anchors.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]