Partial Outage on DeepL Pro
major- Started
- Mar 6, 10:39 AM EST
- Resolved
- Mar 6, 12:56 PM EST
- Duration
- 2h 17m
DeepL's updates (7)
- investigating · Mar 6, 10:39 AM EST
We are looking into errors within the authentication layer which are preventing users from using DeepL Pro services.
- monitoring · Mar 6, 10:58 AM EST
We've identified and rolled out a fix. Error rates are reducing are services are being restored. We will continue monitoring.
- monitoring · Mar 6, 11:17 AM EST
We can confirm that service is restored and error rates have further reduced. We will continue monitoring for errors.
- identified · Mar 6, 12:29 PM EST
We are again seeing a small number of API requests fail, we have identified the problem and are working on a fix.
- identified · Mar 6, 12:31 PM EST
We are continuing to work on a fix for this issue.
- resolved · Mar 6, 12:56 PM EST
We have rolled out a fix and the issue has been resolved.
- postmortem · Mar 6, 1:04 PM EST
During routine maintenance on our database system, an isolated node unexpectedly rejoined the cluster, causing intermittent service interruptions to customers. We quickly followed established procedures to resolve the issue and successfully restored full functionality. Later on we noticed that some customers using the API still experienced issues validating their API key. This was also due to data not being replicated properly to all nodes of the database cluster, yet. We addressed the issue by making the API key resolution process more robust in such cases.
Updates are DeepL's own words from its status page (status: postmortem); we never add an inferred cause. The vendor's incident page ↗