- Level
- confirmed
- Worst impact
- Major outage
- Vimeo says
- 2025-07-31 04:30 to 06:00 UTC (1h 30m)
- Components
- Website
- Regions
- us
- Down Index
- 46of 100
What to do
Check whether you use Vimeo Website in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 27m it lasted.
Anything that failed between 2025-07-31 05:16 UTC and 2025-07-31 08:43 UTC may need a replay.Subscribe to Vimeo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=vimeo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Vimeo 5
- investigating
We have identified the issue and working on a fix.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7f533f4d96
Is Vimeo still down?
No, this incident was resolved 2025-07-31 08:43 UTC. For Vimeo's live state, see https://down.guide/providers/vimeo.
How long did it last?
3h 27m, from 2025-07-31 05:16 UTC to 2025-07-31 08:43 UTC, by the times Vimeo posted.
What was affected?
Vimeo named Website in us.
What caused it?
Vimeo hasn't published a root cause. If it does, it shows here.
Where does this come from?
Vimeo's official status page, https://www.vimeostatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.