Resolved after 3 hours 26 minutes, affecting Website, on July 31, 2025.
# **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.
Affected components
Update timeline
- investigating Jul 31, 2025, 05:16 AM UTC
We have identified the issue and working on a fix.
- identified Jul 31, 2025, 06:07 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 31, 2025, 07:23 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 31, 2025, 08:43 AM UTC
This incident has been resolved.
- postmortem Aug 08, 2025, 08:34 PM UTC
# **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.
Your product runs on more than Vimeo
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services