High latency on DeepL Pro API in US datacenter
minor- Started
- Apr 29, 4:54 AM EDT
- Resolved
- Apr 29, 5:24 AM EDT
- Duration
- 30 min
DeepL's updates (4)
- investigating · Apr 29, 4:54 AM EDT
We are investigating high latency for customers using the DeepL Pro API in our US datacenter.
- identified · Apr 29, 5:01 AM EDT
The issue has been identified and a fix is being implemented.
- monitoring · Apr 29, 5:12 AM EDT
We've rolled out a fix and will continue monitoring latencies. Customers using the new v3 glossary endpoints (edited or multi-language glossaries) will see errors as a side effect of this fix. Translation with monolingual (v2) glossaries will work as expected. We are working to restore behaviour for glossaries with v3 features. For customers that need translation with v3 glossaries, can use api.deepl.com/v2/translate (with a higher latency since it is served by a datacenter outside the US).
- resolved · Apr 29, 5:24 AM EDT
This incident has been resolved.
Updates are DeepL's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗