DeepL Outage History

28 incidents recorded over the last 365 days, 28 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live DeepL status100.00% uptime history

Every Recorded DeepL Incident

DeepL incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 30, 2026DeepL ErrorsAffected datacentres: europe, americas5 minResolved
Sep 9, 2026DeepL is experiencing a problem with Document TranslationsAffected datacentres: europe1h 10mResolved
Aug 31, 2026Major outage resolvedAffected datacentres: europe, americas5 minResolved
Aug 18, 2026Elevated error ratesAffected datacentres: europe, americas21 minResolved
Aug 4, 2026Sign-ins failing for customersAffected datacentres: europe1h 38mResolved
Jul 7, 2026Errors in Translation MemoryAffected datacentres: europe0 minResolved
Apr 27, 2026Major OutageAffected datacentres: europe, americas1h 9mResolved
Apr 23, 2026Degraded Performance on Public APIAffected datacentres: europe0 minResolved
Apr 9, 2026Login currently does not workAffected datacentres: europe, americas0 minResolved
Apr 1, 2026Partial Outage - Voice for Meetings and Voice API impactedAffected datacentres: europe, americas2h 20mResolved
Mar 27, 2026DeepL CAT Tools - Elevated Error & LatencyAffected datacentres: europe21 minResolved
Mar 26, 2026Partial OutageAffected datacentres: europe, americas0 minResolved
Mar 20, 2026Translation errors for select source languagesAffected datacentres: europe, americas3h 59mResolved
Mar 17, 2026Partial Outage - Translations with Glossaries in USAffected datacentres: americas15 minResolved
Mar 16, 2026Glossary API operations degraded in US region (PDX)Affected datacentres: americas0 minResolved
Mar 4, 2026Degraded PerformanceAffected datacentres: americas0 minResolved
Feb 9, 2026Degradation of translation serviceAffected datacentres: europe0 minResolved
Jan 28, 2026Partial Outage - Thai Translations via api-us.deepl.comAffected datacentres: americas0 minResolved
Jan 13, 2026Degraded performanceAffected datacentres: europe9 minResolved
Dec 10, 2025Elevated Error Rate for GlossariesAffected datacentres: europe12 minResolved
Dec 9, 2025Voice API unavailableAffected datacentres: europe5 minResolved
Dec 2, 2025Degraded performance on /v2/TranslateAffected datacentres: europe0 minResolved
Nov 18, 2025Partial Outage - Increased Errors affecting loginAffected datacentres: europe2h 15mResolved
Nov 16, 2025Partial OutageAffected datacentres: americas, europe2h 59mResolved
Nov 15, 2025Partial OutageAffected datacentres: americas36 minResolved
Nov 12, 2025Pro API EU - 500 errorsAffected datacentres: europe28h 35mResolved
Oct 24, 2025Partial OutageAffected datacentres: europe0 minResolved
Oct 19, 2025Service Disruption on DeepL US / Japan LocationsAffected datacentres: americas0 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next DeepL incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This DeepL Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before DeepL acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single DeepL outage in this window ran 1d 4h, against a mean recovery of 1h 39m. If you depend on DeepL in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.