All Systems Operational

Uptime over the past 90 days. View historical uptime.
API Operational
Management Portal Operational
Translation Memory Operational
GenAI and Machine Translation Operational
Editor Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 10, 2026

No incidents reported today.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

Rare situations where a corrected segment is not carried to the next step
Postmortem - Read details
Oct 7, 23:39 UTC
Resolved - This incident has been resolved.
Oct 7, 23:35 UTC
Monitoring - The complete fix was validated in our test environment on 5 October and we expect it in production by 7 October.
Oct 5, 15:00 UTC
Identified - We identified five rare situations in which a correction to an already confirmed segment stays in its own workflow step: saves of the same segment arriving almost at the same time, glossary terms inserted into a confirmed segment, bulk actions (confirm, lock, fix tags), repetitions updated together with the corrected segment, and corrections made after the next step had started. They affect projects with two or more linguistic steps and about 1 in 200 edits passed between steps. Nothing is deleted: every version remains in the segment history.
Oct 2, 11:00 UTC

Oct 6, 2026

No incidents reported.

Oct 5, 2026

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

Oct 1, 2026

No incidents reported.

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

Corrections to confirmed segments not carried to the next workflow step
Postmortem - Read details
Oct 6, 00:30 UTC
Resolved - The fix is in production. Corrections to confirmed segments are carried to the next step again. Segments corrected during 21–28 September are not corrected automatically. We are contacting the accounts we identified as affected with the list of segments and the options for correcting them.
Sep 28, 16:00 UTC
Identified - We identified the main cause. A release on 21 September changed how an editor correction to a confirmed segment is recorded, so the platform no longer recognized it as a new confirmation. Corrections made to confirmed segments between 21 and 28 September may not have reached the next step. A fix is being released today.
Sep 28, 12:00 UTC
Investigating - We are investigating reports that, in projects with more than one linguistic step, a correction made to an already confirmed segment can stay in its own step and not reach the next one. The segment looks correct where it was corrected, and no error is shown. We are working on it as a priority.
Sep 25, 08:00 UTC

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage