We started checking Phrase on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Phrase reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Phrase's own status page declared. Below it, any public chatter we saw about Phrase and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Phrase's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Phrase in the last 24 hours, which is not evidence that nothing is wrong.
Phrase's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Phrase's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Phrase next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts1 in the last hour (prior day averaged 0.8/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
443
US-West
98.19%
332
Europe
100.00%
304
Asia-Pacific
100.00%
184
Their declared record
Phrase's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Degraded Performance of Phrase TMS (EU) starting on November 3, 2026 10:28 CETPartial outage
Nov 3, 2026, 9:40 AM UTC to Nov 3, 2026, 10:01 AM UTC (20 min)resolved
their latest update (Nov 3, 2026, 10:01 AM UTC): The issue affecting the Style Guides landing page in our EU region has been resolved. Access to Style Guides, Content Groups, and Phrase Ecosystem pages within Phrase TMS has been restored. We will continue to monitor the situation and implement further improvements to prevent re…
Performance Disruption of Phrase TMS (EU) between 11:35 AM and 11:46 AM CEST on October 15, 2026Major outage
Oct 15, 2026, 9:44 AM UTC to Oct 15, 2026, 10:24 AM UTC (40 min)resolved
their latest update (Oct 15, 2026, 10:24 AM UTC): This incident has been resolved.
Degraded Performance of Identity management - IDM (EU and US) between 9:02 AM CEST and 11:27 AM CEST on September 23, 2026Minor incident
Sep 23, 2026, 8:48 AM UTC to Sep 23, 2026, 10:03 AM UTC (1h 15m)postmortem published
their latest update (Sep 30, 2026, 12:12 PM UTC): ## Introduction
We would like to share details about an incident that affected access to Phrase TMS on September 23, 2026. Between 9:02 AM and 11:27 AM CEST, users opening Phrase TMS from Phrase Platform could not complete the sign-in. They were either caught in a redirect loop …
Degraded Performance of Phrase Strings & Phrase TMS (EU) starting on September 10, 2026 06:52 CESTPartial outage
Sep 10, 2026, 5:06 AM UTC to Sep 10, 2026, 6:03 AM UTC (57 min)resolved
their latest update (Sep 10, 2026, 6:03 AM UTC): We are pleased to confirm that the webhook synchronization issue between Phrase Strings and Phrase TMS has been resolved and verified as fully operational, including for US data center customers. This incident is now closed.
Degraded Performance of Project management in Phrase TMS (EU) starting on September 1, 2026 16:12 CESTPartial outage
Sep 1, 2026, 2:18 PM UTC to Sep 1, 2026, 4:23 PM UTC (2h 5m)resolved
their latest update (Sep 1, 2026, 4:23 PM UTC): The issue has been resolved and performance is stable.
Disruption of Gengo Translation Orders - API Timeouts Affecting Order Submission (Strings EU and US DC)Partial outage
Aug 31, 2026, 3:06 PM UTC to Sep 2, 2026, 11:46 AM UTC (1d 20h)resolved
their latest update (Sep 2, 2026, 11:46 AM UTC): Gengo has resolved the underlying issue on their end. Price calculations and translation order submissions to Gengo are now working again.
Degraded performance of TMS Project Management Component (EU and US DC) between August 31 2:26 PM CEST and August 31 5:57 PM CESTMajor outage
Aug 31, 2026, 1:11 PM UTC to Aug 31, 2026, 4:53 PM UTC (3h 42m)postmortem published
their latest update (Sep 4, 2026, 8:45 AM UTC): ## Introduction
We would like to share details about an incident that affected Phrase TMS on August 31, 2026. Between 2:26 and 5:57 PM CEST, some users of the legacy Project page were unable to use Tools-menu actions such as creating or editing jobs and running analyses, and cli…
Degraded Performance of Translation Memory Component in Phrase TMS (EU) between August 19, 2016 2:11 PM CEST and August 19, 2016 4:10 PM CESTPartial outage
Aug 19, 2026, 12:16 PM UTC to Aug 19, 2026, 2:09 PM UTC (1h 53m)postmortem published
their latest update (Oct 6, 2026, 8:14 AM UTC): ## **Introduction**
We would like to share more details about the events that occurred with Phrase between 2:11 PM CEST and 4:10 PM CEST on August 19, 2026, which led to degraded Translation Memory functionality in Phrase TMS \(EU\) and what Phrase engineers are doing to prevent…
Degraded Performance of Branching in Phrase Strings (EU) between August 6, 2026 03:45 PM CEST and August 7, 2026 10:46 AM CESTPartial outage
Aug 7, 2026, 7:27 AM UTC to Aug 7, 2026, 2:12 PM UTC (6h 45m)postmortem published
their latest update (Sep 11, 2026, 6:11 AM UTC): ## Introduction
We would like to share details about an incident that affected Phrase Strings on the EU platform between August 6 and August 7, 2026. During this period, changes made in branches were not being recorded by our change-processing pipeline. As a result, branches tha…
Degraded Performance of Connectors in Phrase TMS (EU) on August 6, 2026Partial outage
Aug 6, 2026, 8:11 AM UTC to Aug 6, 2026, 1:19 PM UTC (5h 8m)resolved
their latest update (Aug 6, 2026, 1:19 PM UTC): The incident has been resolved and all components are back to operational.
Showing the 10 most recent of 51 incidents Phrase has declared in the history we hold.
These entries are Phrase's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Phrase's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.