"so not a bug" was the reply on git.
The reply, which does not help much solving:
I'm sorry, given the huge number of people running on EC2, this is definitaly not a Revive Adserver bug.
Possibily some misconfiguration on your side, but the issue tracker is not suitable for support questions.