Partial outage on DeepL Voice
major- Started
- Feb 24, 5:08 AM EST
- Resolved
- Feb 24, 5:51 AM EST
- Duration
- 44 min
DeepL's updates (8)
- investigating · Feb 24, 5:08 AM EST
We are investigating this issue.<br><br><b>Affected Services:</b> Voice<br><b>Additional Info:</b> We are investigating issues related to DeepL Voice
- investigating · Feb 24, 5:45 AM EST
We are continuing to investigate this issue.
- investigating · Feb 24, 5:46 AM EST
We are continuing to investigate this issue.
- monitoring · Feb 24, 5:47 AM EST
A fix has been implemented and we are monitoring the results.
- monitoring · Feb 24, 5:48 AM EST
We are continuing to monitor for any further issues.
- monitoring · Feb 24, 5:48 AM EST
We are continuing to monitor for any further issues.
- resolved · Feb 24, 5:51 AM EST
This incident has been resolved.
- postmortem · Feb 24, 6:04 AM EST
On Feb 24 at 10:08 UTC, we experienced a 40-minute outage of teams services when a misconfiguration, specifically involving lost connectivity on a VPN between Microsoft and our central datacenter, disrupted our communications used for MS Teams. Our team promptly investigated the issue, identified the root cause—a faulty configuration that caused connectivity issues—and restored service. We apologize for any inconvenience this caused our customers. Moving forward, we are implementing stricter change controls, enhanced monitoring tools, and additional training to help prevent similar incidents and ensure a more resilient network.
Updates are DeepL's own words from its status page (status: postmortem); we never add an inferred cause. The vendor's incident page ↗