- 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-07-16 09:50 UTC and 2026-07-16 09:50 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: Thu, 16 Jul 2026 05:45:00 GMT Last Updated: Thu, 16 Jul 2026 09:50:00 GMT Updates: 05:45:00: We are currently investigating a increased error rate from Legacy Microsoft Teams bots failing to join meetings. We are currently trying to reproduce the issue. The issue was caused by an underlying problem with the Microsoft Azure infrastructure. We identified and fixed the root cause. 09:50:00: Subsequent investigation of the problems raised this mornign led to the discovery of a problem with the meeting bot. This is now fully 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-6f21379bd5
Is DeepL still down?
No, this incident was resolved 2026-07-16 09:50 UTC. For DeepL's live state, see https://down.guide/deepl.
How long did it last?
0m, from 2026-07-16 09:50 UTC to 2026-07-16 09:50 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.