Degraded Performance of Translation center in Phrase Strings (EU & US) between July 10, 2026 16:21 CEST and July 10, 2026 17:13 CEST

What to do

• Check whether you use Phrase Translation center, Translation center in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 1m it lasted.

  Anything that failed between 2026-07-10 14:24 UTC and 2026-07-10 15:24 UTC may need a replay.

• Subscribe to Phrase's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=phrase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Phrase 4

1. investigatingJul 10, 2026, 2:24 PM UTC

   We are currently investigating an issue affecting the Translation Center in Phrase Strings (EU and US regions), where strings are failing to load. Our engineering team has identified a potential cause and is actively working to resolve it. We will provide further updates as our investigation progresses.

   provider

2. monitoringJul 10, 2026, 2:37 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

3. resolvedJul 10, 2026, 3:24 PM UTC

   This incident has been resolved.

   provider

4. postmortemAug 7, 2026, 7:14 AM UTC

   Introduction On July 10, 2026, parts of the Phrase Strings frontend at app.phrase.com (http://app.phrase.com/) failed to load correctly for a short period, after required stylesheets and scripts failed to load — the underlying service itself stayed available. The issue began at 16:08 CEST and was resolved by 16:27 CEST. This post-mortem explains what happened and what we're doing to prevent a recurrence. Timeline * Jul 10, 2026 at 16:08 CEST – A deployment introduced new application assets that were never uploaded to our storage service, so the application could no longer load its stylesheets and scripts for customers. * Jul 10, 2026 at 16:21 CEST – Issue detected, incident declared. * Jul 10, 2026 at 16:24 CEST – Root cause identified. * Jul 10, 2026 at 16:26 CEST – Fix applied. * Jul 10, 2026 at 16:27 CEST – Customer-facing impact ended. * Jul 10, 2026 at 16:32 CEST – Incident downgraded to monitoring while the underlying configuration was addressed. * Jul 10, 2026 at 17:12 CEST – Configuration corrected, incident resolved. Root Cause During a planned, routine maintenance, a configuration change unintentionally disabled the process that uploads application assets \(stylesheets, scripts\) to our storage and content-delivery service. This went unnoticed at first, since the assets already in place kept working and no new versions had been shipped yet. On July 10, 2026, a deployment shipped new versions of these assets. Because uploading was still disabled, the new files never reached the storage service, and the application could not load its stylesheets and scripts. Actions to Prevent Recurrence 1. Asset synchronization re-enabled – The disabled process was fixed, restoring correct asset delivery. 2. Asset availability monitoring – Adding monitoring to detect asset load failures automatically, before customers are affected.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.