- Level
- confirmed
- Worst impact
- Degraded
- Components
- Website
- Down Index
- 18of 100
What to do
Check whether you use Vimeo Website. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.
Anything that failed between 2025-08-19 21:40 UTC and 2025-08-19 22:22 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 4
- investigating
We are currently investigating this issue.
provider
- investigating
Some users are experiencing authorization errors with Showcases that should be publicly available. We're currently investigating...
provider
- identified
We've identified the issue and deployed a fix.
provider
- resolved
Showcases are now fully operational.
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-f1b5d5e6ef
Is Vimeo still down?
No, this incident was resolved 2025-08-19 22:22 UTC. For Vimeo's live state, see https://down.guide/vimeo.
How long did it last?
42m, from 2025-08-19 21:40 UTC to 2025-08-19 22:22 UTC, by the times Vimeo posted.
What was affected?
Vimeo named Website.
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.