# Performance Disruption of Phrase Portal (EU) between January 15, 2026, 04:15 PM UTC and 06:03 PM UTC

- Provider: [Phrase](https://down.guide/providers/phrase)
- Confidence: Confirmed
- Impact: Major outage
- lasted 1h 12m
- started 2026-01-15 17:38 UTC
- Phrase Portal (EU)
- eu
- Phrase states the impact was 2026-01-15 04:20 to 17:00 UTC (12h 40m)
- id: DWN-75ba56db56
- Official page: https://stspg.io/0prp2dg1z4zr

## Root cause
> The disruption was caused by a capacity limit being exceeded in our routing infrastructure.

Category: BGP or network. [Postmortem](https://stspg.io/0prp2dg1z4zr)

## Updates from Phrase
### 2026-01-15 17:38 UTC: investigating
Phrase Portal is currently not accessible. Our engineering team is investigating the issue.

### 2026-01-15 18:04 UTC: identified
Engineers identified the cause of the issue and will deploy a fix.

### 2026-01-15 18:15 UTC: identified
A fix has been deployed and now Phrase Portal is accessible. We continue to monitor performance.

### 2026-01-15 18:15 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2026-01-15 18:22 UTC: monitoring
We are continuing to monitor for any further issues.

### 2026-01-15 18:50 UTC: resolved
This incident has been resolved.

### 2026-01-23 16:07 UTC: postmortem
Introduction
We would like to share details about an incident that affected the availability of the RawMT UI portal between 4:15 PM and 6:03 PM UTC on January 15, 2026. During this time, users were unable to access the portal. The disruption was caused by a capacity limit being exceeded in our routing infrastructure. This post-mortem outlines what occurred and the steps we are taking to prevent similar issues in the future.
Timeline
Jan 15, 2026 @ 4:15 PM UTC – A high-severity alert was triggered as the RawMT UI portal became inaccessible to users.
Jan 15, 2026 @ 4:20–5:00 PM UTC – Engineering teams identified that the issue was related to the routing layer reaching a fixed platform limit, preventing service traffic from being properly directed.
Jan 15, 2026 @ 5:03 PM UTC – A mitigation was applied, re-routing affected services through alternate infrastructure.
Jan 15, 2026 @ 6:03 PM UTC – Service was confirmed fully restored and the incident was marked as stable.
Root Cause
The issue occurred when the platform’s traffic routing infrastructure reached a fixed capacity limit on the number of active service associations it could manage. Once this limit was exceeded, configuration updates failed, preventing traffic from being correctly routed to certain services.
Although application services remained operational, they became unreachable to users because there were no valid routing paths available. This resulted in a complete outage of the RawMT UI portal.
Actions to Prevent Recurrence
1. Improved Alerting 
 Alert thresholds for routing capacity have been adjusted to ensure earlier visibility and to elevate urgency before reaching critical limits.
2. Service Distribution Across Infrastructure 
 Services have been actively rebalanced across multiple routing layers to reduce pressure on any single entry point.
3. Planned Architecture Improvements 
 Work is underway to evaluate longer-term changes to the routing architecture to better support scale and reduce the risk of reaching fixed limits in the future.

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-75ba56db56), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.