Resolved -
This incident has been resolved.
Sep 11, 17:47 EDT
Update -
We are still awaiting the completion of a few final data validation steps, but the dataset is nearly complete. Thank you for your continued patience—we’ll keep you updated with the latest on the reporting latency issue as progress continues.
Sep 11, 08:06 EDT
Update -
The backfill is nearly complete, and our team remains engaged as we work toward full resolution. Thank you for your patience!
Sep 9, 10:37 EDT
Monitoring -
Data has begun to backfill, and our team will continue monitoring closely as we work toward fully resolving this issue.
Sep 7, 21:18 EDT
Update -
Our team is continuing to backfill data from the time of the incident. We’ll keep sharing updates as we progress toward a full resolution, and once everything is fully restored, we’ll provide additional details.
Sep 7, 10:03 EDT
Update -
The pacing issue we uncovered has been resolved. We are now monitoring and working towards resolution on the reporting latency issue within the CMS.
Our team will continue to keep a close eye on the situation, and once it is fully resolved, we’ll share additional details on the overall impact.
Sep 6, 18:59 EDT
Update -
Our team has been actively working to resolve an issue related to reporting latency, which has been impacting the timely loading of data into the CMS.
Recent Findings:
In our efforts to resolve the reporting issue, our team identified an unforeseen complication with the pacing in inventory. As a result, there was a temporary mismatch in the pacing behavior.
Fix Implementation:
A quick fix has been successfully implemented, as we work towards a full solution.
Next Steps:
We are continuing to monitor the situation. Once the reporting latency issue is fully resolved, we will provide more insight into the overall impact.
Thank you for your patience as we work to resolve these issues.
Sep 6, 14:29 EDT
Identified -
We are aware that portions of reporting within the CMS may not be fully visible for some users. Please note that all underlying data and delivery remain accurate — this is only a display issue within the interface.
Our team is monitoring closely and will update here as soon as visibility is fully restored.
Sep 6, 08:12 EDT
