Vimeo OTT experienced a critical incident on March 28, 2025 affecting Vimeo OTT Analytics, lasting 62d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 28, 2025, 06:56 PM UTC
We have identified issues with a decline in available data in the Subscribers & Viewership Reports after March 24, 2025. We are investigating and will update you here when we have more information.
- investigating Mar 28, 2025, 09:33 PM UTC
The issue with Subscribers Report data has been resolved. We are still investigating an issue with data in the Viewership report. We will update you here when we have more information.
- investigating Apr 01, 2025, 06:57 PM UTC
We have identified a decline in available data in the Subscribers Report after March 28, 2025 and will investigate that along with the Viewership Report data discrepancies. We will continue to provide updates as we investigate the issue.
- investigating Apr 04, 2025, 08:04 PM UTC
The issue with Subscribers Report data (from 3/28) has been resolved. We are still investigating an issue with data in the Viewership report. We will update you here when we have more information.
- investigating Apr 04, 2025, 08:05 PM UTC
We are continuing to investigate this issue.
- investigating May 07, 2025, 06:03 PM UTC
We continue investigating ongoing issues affecting both the Viewership Report and Subscribers Report.
- investigating May 09, 2025, 06:43 PM UTC
The issue with viewership data has been identified and is currently being addressed by our developers. We're hoping to have a resolution by the end of next week. We’ll provide another update here once the issue is resolved.
- identified May 22, 2025, 10:12 PM UTC
The scope of the data discrepancies has been fully identified and the remaining fixes are in progress. Viewership data is fully caught up through April 24. Some discrepancies remain in the data between April 25 and May 21. These are being corrected on an ongoing basis, and we expect to have them fully resolved by May 28.
- resolved May 29, 2025, 07:32 PM UTC
This incident has been resolved.