DeepL Voice product unavailable for 3 minutes in APJ region.

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-09-29 10:00 UTC and 2026-09-29 10:00 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.

Root cause

The problem was caused by a routine roll-out of monitoring services causing an unexpected disruption of already running services.

Updates from DeepL 1

1. resolvedSep 29, 2026, 10:00 AM UTC

   Affected Services: DeepL Pro - Voice for Meetings, DeepL Pro - Voice for Conversations Started: Tue, 29 Sep 2026 10:00:00 GMT Last Updated: Tue, 29 Sep 2026 10:00:00 GMT Updates: 10:00:00: System montoring shows there was a brief outage with the voice product for 3 minutes in the AsiaPac region. The issue affected 7 calls during the period in question. The problem was caused by a routine roll-out of monitoring services causing an unexpected disruption of already running services. The same roll-out in other regions did not demonstrate this problem. A retrospective into the incident has altready been completed with 2 activites for improvement identified. The first of which has already been complated. The issue ran from 10:02 -10:05 UTC (19:02-19:05 JTC) Our apologies to those customers who were affected by this incident.

   provider

Corrections

None so far.

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