Major incident

iSpot: Processing Delay 9/11-9/13

Affected: Unified Measurement, OTT Conversions, OTT Impresssions, Linear Conversions

Current status of iSpot: Operational — live iSpot status

Timeline

1. Sep 14, 2026, 21:26 UTC
   identified
   We identified a processing delay affecting pixel-based measurement data for event dates September 11-13. Not data was lost - the events were captured, and reprocessing is in progress to restore the affected impression and conversion data. Current Status: OTT Impressions & Conversions: Delayed for Sept 11-13; reprocessing in progress Linear Conversions: Delayed for Sept 11-13; reprocessing in progress Linear Impressions: No impact OTT & Linear Lift: No Impact We expect these dates to be fully repopulated in the dashboard and API within the next 48 hours and will confirm status as we progress.
2. Sep 15, 2026, 12:41 UTC
   identified
   Update: Processing Delay 9/11–9/13 (OTT Impressions & Conversions, Linear Conversions) Status update on the delayed measurement data for September 11–13. No data was lost. - OTT Impressions & Conversions: Reprocessing nearly complete; final load begins this afternoon/evening - Linear Conversions: Reprocessing nearly complete; final load begins this afternoon/evening - Linear Impressions / OTT & Linear Lift: No impact We expect these dates to be fully restored in the dashboard and API by tomorrow morning, and will confirm once
3. Sep 16, 2026, 20:56 UTC
   identified
   Status update on the delayed measurement data for September 11–13. No data was lost. - OTT Impressions & Conversions: Reprocessing nearly complete; final load is taking longer than anticipated. Estimated sometime tomorrow (9/17), with the goal of completion by morning. - Linear Conversions: Reprocessing nearly complete; final load is taking longer than anticipated. Estimated sometime tomorrow (9/17), with the goal of completion by morning. - Linear Impressions / OTT & Linear Lift: No impact We expect these dates to be fully restored in the dashboard and API sometime tomorrow, with the goal of morning, and will confirm once complete.
4. Sep 17, 2026, 17:01 UTC
   identified
   Update: Processing Delay 9/11–9/13 (OTT Impressions & Conversions, Linear Conversions) Overall Status: Resolved (Minor Reporting Detail Pending) Data Backlog Resolved All delayed measurement data for September 11–13 has been reprocessed and loaded. Zero data was lost. OTT Impressions & Conversions: Reprocessing complete; data loaded. Linear Conversions: Reprocessing complete; data loaded. Linear Impressions / OTT & Linear Lift: Unaffected. Current Focus: Metadata Repopulation Core numbers are fully verified, but metadata fields for September 11 (and limited records for September 12) are partially incomplete. What is accurate: Top-line impression and conversion totals are 100% complete and accurate. What is impacted: Granular reports filtered by campaign, creative, publisher, or placement ID may show missing details for 9/11–9/12. Next Steps: We are working on a fix to repopulate the missing metadata and will provide a correction timeline shortly.
5. Sep 18, 2026, 19:48 UTC
   resolved
   Resolved: iSpot Data Processing Delay The recent data processing delays have been fully resolved. Both the data backlog and the associated metadata repopulation are complete, and reporting is now current across dashboards and API. No data was lost at any point — the issue caused a temporary processing delay, not data loss. Impacted and now resolved: Event dates: September 11–13 Metrics: OTT Impressions, OTT Conversions, and Linear Conversions Impacted metadata is now resolved and functional as well All of the above are fully repopulated and current in dashboards and API. What you need to do: Nothing for dashboard users — figures have updated automatically. If you pulled data via API or export during the affected window (Sept 11–13), we'd recommend re-pulling those dates to capture the final figures. What we've done to prevent recurrence: Pipeline modernization: A complete rewrite of the affected pipeline was already underway and is targeted for completion within the next 60 days, providing a more scalable and resilient foundation. Additional capacity: Increased capacity and throughput on the affected component to improve stability while the replacement is completed. Active oversight: Our on-call team is monitoring the pipeline around the clock, including weekends, while these safeguards remain in place. Enhanced monitoring & alerting: Added hourly monitoring of data delivery, volume, and quality, with alerts calibrated for expected daily and seasonal patterns to catch issues sooner. We appreciate your patience, and please reach out with any questions.
6. Sep 25, 2026, 20:04 UTC
   postmortem
   # Root Cause Analysis: Pixel Measurement Data Delay \(Sept 2–15, 2026\) Sep 24, 2026 ## Summary Between September 2–15, 2026, a data pipeline issue caused delays in processing pixel-based measurement data \(impressions and conversion/pixel events\). No data was lost. All affected data was reprocessed and validated by September 18th, and the reported figures are now complete and accurate. ## What Happened and Customer Impact Two related issues affected the same measurement data pipeline: an initial disruption from Sept 2–5 and a shorter follow-on issue from Sept 10–13. * Impression and conversion data for Sept 2–6 and Sept 11–13 appeared temporarily incomplete while processing and recovery were underway. * Reporting figures updated automatically as the data was reprocessed and are now complete and accurate. * No action was required from customers. ## Root Cause The issue was caused by a capacity constraint within a legacy component of our data pipeline. Existing monitoring did not provide sufficient visibility into the developing condition, which delayed detection. Once the issue was identified and addressed, the pipeline’s existing processing design required additional time to work through the accumulated backlog and update the reporting dashboard. ## Resolution We restored the affected pipeline component, increased its processing capacity, reprocessed the backlog, and validated the corrected figures in the reporting dashboard. ## Preventive Measures We're addressing this on two tracks — a permanent fix and immediate interim safeguards: * Long-term resolution: Work is underway to modernize the affected portion of the pipeline to reduce reliance on the legacy component associated with this incident. We expect this work to be completed in the next 60 days. * Enhanced monitoring: In the interim, we have expanded monitoring of data delivery, volume, and quality, so potential shortfalls are detected and addressed quickly. * Additional capacity: We have increased capacity and throughput within the affected component to improve stability while the modernization work is completed. * Improved alerting: We have refined our alerts to better account for unexpected variation in data volumes and enabled faster identification of genuine issues. * Active oversight: Our on-call team continues to monitor the pipeline closely, including outside regular business hours, to ensure issues are investigated and addressed promptly. We take the accuracy and timeliness of your measurement data seriously, and apologize for the disruption this incident caused. If you have any questions about this incident or its impact on your data, please reach out to your Customer Success representative.

Updates as published by iSpot (original).