- Level
- confirmed
- Worst impact
- Major outage
- Phrase says
- 2025-10-10 10:17 to 10:26 UTC (9m)
- Regions
- eu
What to do
Check whether you use Phrase in eu. 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 0m it lasted.
Anything that failed between 2025-10-10 10:17 UTC and 2025-10-10 10:17 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.
Root cause
12:26 PM CEST: Platform engineers restarted unresponsive database nodes and increased instance size Root Cause For a few minutes, the _Custom Metadata Service_ experienced a temporary overload due to a sudden increase in load.
Category: Capacity
Read the postmortemUpdates from Phrase 2
- resolved
Between 12:17 and 12:40 PM CEST on October 10, 2025, some users were unable to access Phrase TMS (EU). Service availability returned to normal by 12:40 PM CEST. No further impact has been observed since.
provider
- postmortem
Root Cause Analysis October 10, 2025 Introduction We would like to share more details about the events that occurred with Phrase between 12:17 PM CEST and 12:26 PM CEST on October 10, 2025, which led to a performance disruption of all Phrase TMS \(EU\) components and what Phrase engineers are doing to prevent these issues from reoccurring. Timeline 12:16 PM CEST: Platform & Engineering team was alerted by the monitoring system 12:18 PM CEST: The Tech Support team was alerted to an issue affecting access to Phrase TMS \(EU\). 12:26 PM CEST: Platform engineers restarted unresponsive database nodes and increased instance size Root Cause For a few minutes, the _Custom Metadata Service_ experienced a temporary overload due to a sudden increase in load. This caused the service to become inaccessible. Because the TMS UI was incorrectly dependent on this internal service, customers using _Custom Metadata_ were unable to access the TMS during this period. Service was restored once the system load normalized. Actions to Prevent Recurrence * Updated the UI API endpoint to remove the dependency on the Custom Metadata Service. TMS will now remain accessible, with only Custom Metadata functionality limited during similar conditions. * Increased the database node instance size to better handle sudden spikes in resource utilization and prevent similar overloads.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8bc447f750
Is Phrase still down?
No, this incident was resolved 2025-10-10 10:17 UTC. For Phrase's live state, see https://down.guide/providers/phrase.
How long did it last?
0m, from 2025-10-10 10:17 UTC to 2025-10-10 10:17 UTC, by the times Phrase posted.
What was affected?
Phrase named in eu.
What caused it?
Capacity. Phrase wrote: "12:26 PM CEST: Platform engineers restarted unresponsive database nodes and increased instance size Root Cause For a few minutes, the _Custom Metadata Service_ experienced a temporary overload due to a sudden increase in load." The postmortem: https://stspg.io/0l3nd09tmjpx
Where does this come from?
Phrase's official status page, https://status.phrase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.