Yes, we are aware of it. This is happening because the issue is in the main ("old") scanning source we have for Bet365 in Prematch. That is why we're switching to an alternative scanning source whenever new issues with this specific bookie appear, while our team keeps working on settling the problem with the main source of scanning. Unfortunately, this task is still being worked on by our developers.
Thank you kindly for your continued patience!