DeepL status history
24 incidents over the last year, newest first; 100.00% uptime (90 days), 100.00% uptime (since Jul 7). History from before down.guide started reading the page is imported from DeepL's own archive.
Month
2026-10
2 incidents
- DeepLPartial outageErrors affecting login and account management
- DeepLMajor outageCustom rules partially impacted
Month
2026-09
7 incidents
- DeepLPartial outageUpdate: Sign-in issues with DeepL Voice for Microsoft Teams
- DeepLPartial outageDeepL Errors
- DeepL Voice product unavailable for 3 minutes in APJ region.
- DeepLPartial outageCustomer are seeing errors reporting "Something went wrong"
- DeepLPartial outageDeepL Voice translation disruption in Microsoft Teams
- DeepLPartial outageDeepL is experiencing a problem with Document Translations
- DeepLDegradedUsers in some regions not able to access DeepL
Month
2026-08
10 incidents
- DeepLMajor outageMajor outage resolved
- DeepLDegradedIssues with multiple DeepL services
- DeepLPartial outagedeepl.com is blocking user agents
- DeepLDegradedTranscriptions were failing
- DeepLDegradedDelayed availability of glossaries and other customizations
- DeepLPartial outageElevated error rates
- DeepLPartial outageTranslator page failing to load on custom DeepL subdomains
- DeepLMajor outageLive translation interrupted for some Voice for Meetings sessions
- DeepLPartial outageWeb errors using DeepL services
- DeepLDegradedSign-ins failing for customers
Month
2026-07
5 incidents
- DeepLMajor outageLimited access to some DeepL Pro subscriptions
- DeepLDegradedVoice for Meetings degraded for some customers
- DeepLDegradedIssue with subscription cancellations
- DeepLPartial outageLegacy teams bot fails to join Meetings
- DeepLPartial outageErrors in Translation Memory