One of my measurements (that usually uses about 1000 credits per day) all of a sudden posted a credit usage of 2,293,788.00 credits for a single measurement. 2013-10-10 18:13 UTC UDM 764596 samples of msm #1013277 -2,293,788.00 -1,279,520.00 I don't know where or why the 764596 samples came from, usually only 90 samples are performed. Was there a proble in the measurement or credit system recently? Thanks.
On Thu, Oct 10, 2013 at 02:54:26PM -0400, Mike. <the.lists@mgm51.com> wrote a message of 20 lines which said:
I don't know where or why the 764596 samples came from, usually only 90 samples are performed.
Was there a proble in the measurement or credit system recently?
Someone reported exactly the same problem on Twitter: https://twitter.com/bastien_durel/status/388407290262736897
On 2013.10.10. 23:10, Stephane Bortzmeyer wrote:
On Thu, Oct 10, 2013 at 02:54:26PM -0400, Mike. <the.lists@mgm51.com> wrote a message of 20 lines which said:
I don't know where or why the 764596 samples came from, usually only 90 samples are performed.
Was there a proble in the measurement or credit system recently?
Someone reported exactly the same problem on Twitter:
I can confirm that the billing cycle yesterday afternoon went out of whack: we see that in some cases it overcharged (and in some other cases it undercharged) for measurement results. We've suspended billing for the time being and are investigating the cause for the issue. Of course we'll compensate the affected users for the overcharge. We'll get back with more details later. Thank you for your patience, Robert
On 2013.10.11. 10:05, Robert Kisteleki wrote:
On 2013.10.10. 23:10, Stephane Bortzmeyer wrote:
On Thu, Oct 10, 2013 at 02:54:26PM -0400, Mike. <the.lists@mgm51.com> wrote a message of 20 lines which said:
I don't know where or why the 764596 samples came from, usually only 90 samples are performed.
Was there a proble in the measurement or credit system recently?
Someone reported exactly the same problem on Twitter:
I can confirm that the billing cycle yesterday afternoon went out of whack: we see that in some cases it overcharged (and in some other cases it undercharged) for measurement results. We've suspended billing for the time being and are investigating the cause for the issue.
Of course we'll compensate the affected users for the overcharge.
We'll get back with more details later.
Update: so far we haven't identified the root cause of the problem. However, in order to prevent the issue form reoccuring, we deployed an emergency update of the billing code that includes sanity checks about the charges and refuses to bill unreasonable amounts. (This piece of code was scheduled for deployment after the RIPE76 meeting.) We also identified overcharged measurements and provided compensation for these.
(... and now also sending the missing part of this mail ...)
Update: so far we haven't identified the root cause of the problem. However, in order to prevent the issue form reoccuring, we deployed an emergency update of the billing code that includes sanity checks about the charges and refuses to bill unreasonable amounts. (This piece of code was scheduled for deployment after the RIPE76 meeting.)
We also identified overcharged measurements and provided compensation for these. We believe this covers virtually all of the affected measurements.
We plan to give you another update tomorrow, once we're through 2-3 more billing cycles. Regards, Robert Kisteleki for the RIPE Atlas team
On 10/11/2013 at 2:59 PM Robert Kisteleki wrote: |(... and now also sending the missing part of this mail ...) | |> Update: so far we haven't identified the root cause of the problem. |However, |> in order to prevent the issue form reoccuring, we deployed an emergency |> update of the billing code that includes sanity checks about the charges |and |> refuses to bill unreasonable amounts. (This piece of code was scheduled |for |> deployment after the RIPE76 meeting.) |> |> We also identified overcharged measurements and provided compensation for |> these. |We believe this covers virtually all of the affected measurements. | |We plan to give you another update tomorrow, once we're through 2-3 more |billing cycles. | |Regards, |Robert Kisteleki |for the RIPE Atlas team ============= Thanks for the follow-up.
Dear All, Today's update, as promised: we believe that the situation has been successfully resolved. If you see any reamining issues, please write to us at atlas@ripe.net and we'll look into the details. Regards, Robert
participants (3)
-
Mike. -
Robert Kisteleki -
Stephane Bortzmeyer