- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Vimeo. 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 5d 6h it lasted.
Anything that failed between 2025-11-27 09:06 UTC and 2025-12-02 15:52 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 are currently investigating this issue.
provider
- investigating
We are investigating reports of elevated buffering
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- investigating
A workaround has been implemented while we investigate the root cause.
provider
- resolved
This incident has been resolved.
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-4fb8ac6033
Is Vimeo still down?
No, this incident was resolved 2025-12-02 15:52 UTC. For Vimeo's live state, see https://down.guide/vimeo.
How long did it last?
5d 6h, from 2025-11-27 09:06 UTC to 2025-12-02 15:52 UTC, by the times Vimeo posted.
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.