There was a view counting glitch on January 27 which some of you have noticed. The reason was that during upgrade work on the counting mechanism, that is meant to improve its performance, some misconfiguration in one of the elements caused every article that received views to get stuck on 1.
It has since been fixed.
Since the views play a major role in your payments calculations, and the payments cycle for the 27th already finished and used those incorrect views, it yielded incorrect payments for all of you.
To rectify this issue, you are going to receive an additional cycle of payments for the 27th, based on your views from a day before. That means you are receiving the correct payment for the 27th, plus any amount you received in the erroneous cycle. In other words — it’s our mistake, so we’re paying up.
Please note, however, that the skewed views count for the 27th will remain as is.
We hope to refrain from such errors in the future, and as always, we make it up to you when we fault.