Resolved incident

Vimeo.com is not accessible for logged out users

Vimeo · Critical · Started

Duration
3h 27m
Severity
Critical
Status
Postmortem

Summary

Critical · Postmortem

# **What happened** On July 31, between approximately 12:30 AM and 2:00 AM EDT, some logged-out Vimeo users encountered an issue when visiting the Vimeo home page. Instead of the expected content, impacted users received a blank screen with a brief error message.  # **What caused it** Corrupted memory on the server side caused some isolated web server processes to fail. As a result, requests for the logged-out Vimeo home page that relied on these processes resulted in the error message.  # **How we responded** We became aware of the outage within 30 minutes of the initial event and immediately began investigating. Once we confirmed the issue, we applied a manual fix to restore normal functionality.  # **What we’re doing to prevent a recurrence** We’re improving our internal reporting to alert us to similar conditions sooner. We’re also making sure that future errors of this type generate our standard HTTP 500 error page instead of a blank screen with a technical readout.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Investigating

    Vimeo

    We have identified the issue and working on a fix.

  2. Identified

    Vimeo

    The issue has been identified and a fix is being implemented.

  3. Monitoring

    Vimeo

    A fix has been implemented and we are monitoring the results.

  4. Resolved

    Vimeo

    This incident has been resolved.

  5. Postmortem

    Vimeo

    # **What happened** On July 31, between approximately 12:30 AM and 2:00 AM EDT, some logged-out Vimeo users encountered an issue when visiting the Vimeo home page. Instead of the expected content, impacted users received a blank screen with a brief error message.  # **What caused it** Corrupted memory on the server side caused some isolated web server processes to fail. As a result, requests for the logged-out Vimeo home page that relied on these processes resulted in the error message.  # **How we responded** We became aware of the outage within 30 minutes of the initial event and immediately began investigating. Once we confirmed the issue, we applied a manual fix to restore normal functionality.  # **What we’re doing to prevent a recurrence** We’re improving our internal reporting to alert us to similar conditions sooner. We’re also making sure that future errors of this type generate our standard HTTP 500 error page instead of a blank screen with a technical readout.