- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 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-09-14 04:46 UTC and 2026-09-14 04:46 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
- resolved
Affected Services: DeepL Pro - Voice for Meetings Started: Mon, 14 Sep 2026 04:46:00 GMT Last Updated: Mon, 14 Sep 2026 04:46:00 GMT Updates: 04:46:00: On 14 September 2026, between approximately 04:46 and 05:27 UTC, customers using the legacy DeepL Voice integration in Microsoft Teams experienced failures when starting translation and interruptions to translation in ongoing meetings. Service has been restored. We are investigating the underlying cause. We apologize for the disruption.
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-530a6c98c4
Is DeepL still down?
No, this incident was resolved 2026-09-14 04:46 UTC. For DeepL's live state, see https://down.guide/deepl.
How long did it last?
0m, from 2026-09-14 04:46 UTC to 2026-09-14 04:46 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.