Vimeo OTT had 15 outages in the last 2 years totaling 416h 56m of downtime — averaging 0.6 incidents per month.
There were 15 Vimeo OTT outages since June 10, 2025 totaling 416h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
The Vimeo Player is experiencing issues, also impacting the OTT product. We're working with the Vimeo platform team to resolve the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're currently investigating an issue where the "Continue Watching" feature is not updating user's progress in real time. The updates are happening few hours after the original action. This may cause videos to not resume where you left off and also not show the recently watched videos on the continue watching row. Our team is actively working to resolve this as quickly as possible. We'll post an update as soon as we have more information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are currently investigating reports of increased buffering rates for video playback.
The issue has been identified as affecting videos uploaded after 20:30 UTC. A fix is being implemented.
A fix has been implemented and new uploads are processing normally. Recovery for videos uploaded between 20:30 and 01:40 UTC is in progress.
All affected videos have been queued for reprocessing.
All affected videos are processing normally.
We are currently investigating an issue with Chromecast functionality. Most users will not be able to cast from branded applications.
The issue has been identified and a fix is being implemented.
Casting functionality has been restored.
This incident has been resolved.
The gained, lost, and total subscriber count data is up to date as of September 30th. Beginning October 1st we are experiencing delays in data updates.
We are continuing to work on a fix for this issue.
The subscriber data dashboard is now up to date through October 5th. Subscriber data in Streaming Analytics is still delayed beginning October 1st. We are continuing to work on restoring the rest of the data.
The subscriber data dashboard is now fully up to date. Subscriber data in Streaming Analytics is still delayed beginning October 1st.
We are continuing to work on bringing subscriber data in Streaming Analytics fully up to date.
This incident has been resolved. Subscriber data in Streaming Analytics is fully up to date.
We are currently investigating a recurrence of an issue with playback progress not being updated. This may cause videos to not resume where you left off and also not show the recently watched videos on the Continue Watching row.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
# **What happened** Between September 21 and October 2, some Vimeo OTT users intermittently experienced issues with our Continue Watching feature—recently viewed videos didn’t appear in the correct row, and playback didn’t resume from where it left off. # **What caused it** The migration of our internal event streaming infrastructure, which was ongoing at this time, didn’t initially have enough capacity. In addition, we experienced downstream challenges with both queue processors and related data stores. A combination of these issues occurred multiple times during the incident window. # **How we responded** We resolved the issue by properly scaling and partitioning the event streaming platform, which eliminated the immediate bottlenecks. # **What we’re doing to prevent a recurrence** We’re revisiting services associated with the streaming platform to ensure that they can properly scale in the future. We're also improving our internal monitoring to catch these events sooner.
All incoming requests are experiencing high error rates. The majority of admin and customer pages are currently inaccessible.
# **What happened** On September 11, between approximately 2:18 PM and 2:30 PM EDT, some Vimeo OTT users were unable to access video pages and applications, including admin and staff sites. The API was unaffected during this outage. # **What caused it** A recent update contained faulty logic, which resulted in a cascading error. This error consumed available resources and caused the outage. # **How we responded** Our internal monitoring systems detected this issue almost immediately. Our engineering team quickly identified the faulty update and reverted to a prior stable version of Vimeo OTT. # **What we’re doing to prevent a recurrence** We’re investigating why the code caused the cascading error. Once we have a better understanding of the underlying issue, we plan to implement safeguards in our code review process to reduce the risk of similar outages.
We're currently investigating an issue where the "Continue Watching" feature is not updating user's progress. This may cause videos to not resume where you left off and also not show the recently watched videos on the continue watching row. Our team is actively working to resolve this as quickly as possible. We'll post an update as soon as we have more information.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Viewership data has been delayed since August 10 at 23:00 UTC. It is currently being repaired, and we expect to be fully caught up on August 12.
The data is current through August 11, with the exception of the hour between 21:00-22:00 UTC. Most hours for August 12 are still underreporting by as much as 20%. These are currently being fixed.
This incident has been resolved.
Video playback is not working for most users.
We are continuing to investigate this issue.
The issue has been identified, and we are continuing to fix and monitor the issue. We're seeing recovery on playback.
Playback has been restored for most users.
Playback has been restored for most users.
The incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.