Inaccuracies in the source data for reporting API v1

We have resolved the issue with the data fed through the reporting API v1. The issue was due to a failure with our incremental data ingestion strategy. This is now fixed. Users should only notice minor fluctuations in their data as the issues only affected about 1% of the data in a completely random manner. This escaped our monitoring thresholds. We have entirely reworked the ingestion method and we will be monitoring it closely in the next few days and we have applied an extremely strict monitoring threshold going forward.

We found the error for the inaccuracies and are working on a fix.

We have noticed inaccuracies in the pre-processed data that feeds the reporting API v1 endpoints. We are investigating