Skip to main content
DeepL

Transcriptions were failing

Degraded Lasted 0m · started · DeepL's page

Level
confirmed
Worst impact
Degraded
Down Index
18of 100

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-26 05:55 UTC and 2026-08-26 05:55 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. resolved

    Affected Services: DeepL Pro - Voice for Meetings, DeepL Pro - Voice for Conversations Started: Wed, 26 Aug 2026 05:55:00 GMT Last Updated: Wed, 26 Aug 2026 05:55:00 GMT Updates: 05:55:00: The incident is 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-18c880fa20

Is DeepL still down?

No, this incident was resolved 2026-08-26 05:55 UTC. For DeepL's live state, see https://down.guide/deepl.

How long did it last?

0m, from 2026-08-26 05:55 UTC to 2026-08-26 05:55 UTC, by the times DeepL posted.

What caused it?

DeepL hasn't published a root cause. If it does, it shows here.

Where does this come from?

DeepL's official status page, https://status.deepl.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.