# Performance Disruption of All Phrase TMS (EU) Components between October 10, 2025, 12:16 PM CEST and 12:26 PM CEST

- Provider: [Phrase](https://down.guide/providers/phrase)
- Confidence: Confirmed
- Impact: Major outage
- lasted 0m
- started 2025-10-10 10:17 UTC
- eu
- Phrase states the impact was 2025-10-10 10:17 to 10:26 UTC (9m)
- id: DWN-8bc447f750
- Official page: https://stspg.io/0l3nd09tmjpx

## 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. [Postmortem](https://stspg.io/0l3nd09tmjpx)

## Updates from Phrase
### 2025-10-10 10:17 UTC: 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.

### 2025-11-05 08:14 UTC: 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.

From the builder: does your app depend on Phrase? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=phrase) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Phrase.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-8bc447f750), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.