Thanks to all who have responded and offered help.
I opened a support case and the following fix was suggested to me:
The escalation engineer found that there were some issues with the databases involved in the tracking and reporting of requests and violations.
Unfortunately, there is no easy way to repair the existing DB entries to get historic reports fixed, but we could try to fix it for future requests by restarting the "asmlogd" service using the command below:
pgrep asmlogd | xargs kill -9
(this command will kill the process and it will be restarted automatically)
This should not cause interruptions to your production traffic, but please still consider doing it during a maintenance window.
I implemented this fix and after observing the system for a significant period of time, I am now satisfied that this has solved the problem.