Resolved incident

New uploads not transitioning to playable

Vimeo · Major · Started

Duration
4h 42m
Severity
Major
Status
Postmortem

Summary

Major · Postmortem

# **What happened** On July 15, between approximately 11:00 AM and 2:00 PM EDT, some Vimeo users who uploaded videos experienced delays in playback.  # **What caused it** A recent update introduced a bug into the video processing pipeline that prevented some processed videos from being marked as playable. As a result, affected videos appeared to be stuck in the optimization phase. # **How we responded** We promptly identified the bug, rolled back the changes, and deployed a script to mark the affected videos as playable. By 7:00 PM EDT, all impacted videos had been fixed.  # **What we’re doing to prevent a recurrence** We’re reviewing our internal testing and monitoring policies to make bugs like the one that caused the incident easier to detect and harder to introduce in the first place.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Monitoring

    Vimeo

    Some uploads created between 10:55 and 13:55 ET are experiencing delays transitioning to playable status. New uploads are processing normally. Recovery is in-progress for affected uploads; no data loss is expected.

  2. Resolved

    Vimeo

    This incident has been resolved. Recovery is complete for affected uploads.

  3. Postmortem

    Vimeo

    # **What happened** On July 15, between approximately 11:00 AM and 2:00 PM EDT, some Vimeo users who uploaded videos experienced delays in playback.  # **What caused it** A recent update introduced a bug into the video processing pipeline that prevented some processed videos from being marked as playable. As a result, affected videos appeared to be stuck in the optimization phase. # **How we responded** We promptly identified the bug, rolled back the changes, and deployed a script to mark the affected videos as playable. By 7:00 PM EDT, all impacted videos had been fixed.  # **What we’re doing to prevent a recurrence** We’re reviewing our internal testing and monitoring policies to make bugs like the one that caused the incident easier to detect and harder to introduce in the first place.