# Vimeo.com is not accessible for logged out users

- Provider: [Vimeo](https://down.guide/vimeo)
- Level: confirmed
- Impact: Major outage
- lasted 3h 27m
- started 2025-07-31 05:16 UTC
- Website
- us
- id: DWN-7f533f4d96
- Official page: https://stspg.io/v488kmjq9dq6

## Updates from Vimeo
### 2025-07-31 05:16 UTC: investigating
We have identified the issue and working on a fix.

### 2025-07-31 06:07 UTC: identified
The issue has been identified and a fix is being implemented.

### 2025-07-31 07:23 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2025-07-31 08:43 UTC: resolved
This incident has been resolved.

### 2025-08-08 20:34 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).