Classic Interactive Downtime

What to do

• Check whether your product depends on Vimeo. 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 4d 17h it lasted.

  Anything that failed between 2025-09-05 12:35 UTC and 2025-09-10 06:27 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 8

1. investigatingSep 5, 2025, 12:35 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingSep 5, 2025, 12:37 PM UTC

   Interactive Editor (Classic) is down

   provider

3. identifiedSep 5, 2025, 2:24 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

4. identifiedSep 5, 2025, 2:49 PM UTC

   We are continuing to work on a fix for this issue.

   provider

5. identifiedSep 5, 2025, 3:11 PM UTC

   We are continuing to work on a fix for this issue.

   provider

6. identifiedSep 5, 2025, 4:37 PM UTC

   We are continuing to work on a fix for this issue.

   provider

7. monitoringSep 8, 2025, 7:43 AM UTC

   The fix has been implemented, and Interactive Editor (Classic) is now available in 93% of geographic locations. For the remaining locations, it may take up to 72 hours for DNS changes to propagate. As a workaround, it's possible to use Interactive Editor (Classic) in these regions through a VPN.

   provider

8. resolvedSep 10, 2025, 6:27 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.