Live translation interrupted for some Voice for Meetings sessions

What to do

• Check whether your product depends on DeepL. 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 0m it lasted.

  Anything that failed between 2026-08-10 17:10 UTC and 2026-08-10 17:10 UTC may need a replay.

• Subscribe to DeepL's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=deepl works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DeepL 1

1. resolvedAug 10, 2026, 5:10 PM UTC

   Affected Services: DeepL Pro - Voice for Meetings, DeepL Pro - Voice for Conversations Started: Mon, 10 Aug 2026 17:10:00 GMT Last Updated: Mon, 10 Aug 2026 17:10:00 GMT Updates: 17:10:00: Between 17:10 and 17:28 UTC on 10 August 2026, a faulty backend deployment prevented DeepL Voice for Meetings from starting or restoring live-translation sessions. Meetings that were in progress when the issue began may have lost translated captions without an error message and could not restore them by restarting or rejoining — for those meetings, captions remained unavailable until the meeting ended. Meetings started after 17:28 UTC were not affected. Additionally, starting a new 1:1 Conversations session failed for a brief period (17:27:55–17:28:27 UTC); retrying after that time succeeded. This incident is being published retroactively following an internal investigation.

   provider

Corrections

None so far.

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