Articulate incident

Localization: Translation failures with DeepL glossaries

Minor Resolved View vendor source →

Articulate experienced a minor incident on June 22, 2026 affecting Localization, lasting 7h 21m. The incident has been resolved; the full update timeline is below.

Started
Jun 22, 2026, 03:30 PM UTC
Resolved
Jun 22, 2026, 10:52 PM UTC
Duration
7h 21m
Detected by Pingoru
Jun 22, 2026, 03:30 PM UTC

Affected components

Localization

Update timeline

  1. investigating Jun 22, 2026, 03:30 PM UTC

    Rise 360 and Storyline 360 customers using a glossary for translation may experience translation failures. We’ve identified an issue with DeepL glossary creation and are investigating. Translations that don’t use a glossary are not affected at this time.

  2. investigating Jun 22, 2026, 04:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 22, 2026, 06:12 PM UTC

    Rise 360 and Storyline 360 customers using a glossary for translation may experience translation failures. Glossary creation continues to be impacted. We’re working with our upstream providers to investigate the issue. Translations appear stable when a glossary is not used.

  4. investigating Jun 22, 2026, 07:30 PM UTC

    We are continuing to investigate this issue.

  5. identified Jun 22, 2026, 08:19 PM UTC

    Rise 360 and Storyline 360 customers using a glossary for translation may experience translation failures. We’ve identified the root cause and are working on a fix. Glossary creation continues to be impacted. Translations remain stable when a glossary is not used.

  6. monitoring Jun 22, 2026, 09:46 PM UTC

    A fix has been deployed to address the issue affecting translations in Rise 360 and Storyline 360 when using a glossary. Translation requests using glossaries should now process successfully. We will continue to monitor the situation and provide further updates as needed.

  7. resolved Jun 22, 2026, 10:52 PM UTC

    This incident has been resolved.