Crowdin Incident History

Resolution We've resolved a status page reporting issue and removed an incident record that incorrectly showed 7 hours and 53 minutes of downtime for Crowdin Translate. The service was fully operational the entire time — there was no actual downtime or user impact. What Happened? The false "Major Outage" status was triggered by an automation notification glitch. Two conflicting updates (DOWN and UP) arrived at the exact same time. Due to a race condition, the system processed the DOWN alert but ignored the simultaneous UP notification, leaving the status page stuck in an incorrect state.

ResolutionWe've resolved a status page reporting issue and removed an incident record that incorrectly showed 7 hours and 53 minutes of downtime for Crowdin Translate. The service was fully operational the entire time — there was no actual downtime or user impact.What Happened?The false "Major Outage" status was triggered by an automation notification glitch. Two conflicting updates (DOWN and UP) arrived at the exact same time. Due to a race condition, the system processed the DOWN alert but ignored the simultaneous UP notification, leaving the status page stuck in an incorrect state.