История сбоев Crowdin

1. 7 июля 2026 г. в 18:27 UTCresolved

   Резолюция Мы решили проблему с отчетом о статусе страницы и удалили запись инцидента, которая неправильно показала 7 часов и 53 минуты простоя для Crowdin Translate. Сервис был полностью работоспособным все время — не было фактического простоя или воздействия пользователя. Что случилось? Ложный статус «Major Outage» был вызван сбоем в уведомлении об автоматизации. Два противоречивых обновления (DOWN и UP) появились одновременно. Из-за состояния гонки система обработала предупреждение DOWN, но проигнорировала одновременное уведомление UP, оставив страницу статуса застрявшей в неправильном состоянии.

Автоматический перевод официального обновления инцидента.

1. 16 марта 2026 г. в 08:55 UTCinvestigating

   We noticed unexpected service behavior, mainly crowdin.com is impacted. Our developers have already started investigating the case, and you will be posted on further updates.

2. 16 марта 2026 г. в 09:19 UTCidentified

   The issue has been identified, and a solution is being implemented. As a temporary measure, users may encounter a CAPTCHA when navigating between pages.

3. 16 марта 2026 г. в 09:31 UTCmonitoring

   All services are back to the normal state. We will keep the incident open for the next 10 minutes to provide you with a final confirmation.

4. 16 марта 2026 г. в 09:46 UTCresolved

   After thorough monitoring, we can confirm the service is fully back to normal. The incident has now been marked as "Resolved". We will continue to monitor Crowdin's health 24/7/365. Thank you!

1. 19 января 2026 г. в 14:30 UTCinvestigating

   We identified degraded performance among organizations hosted in the EU data center. All other Crowdin components are fully accessible. We will keep you posted on any further updates.

2. 19 января 2026 г. в 14:50 UTCresolved

   The solution was delivered several minutes after the incident was reported, we were monitoring the performance of EU data center organizations and confirmed that it got back to normal

1. 12 ноября 2025 г. в 16:15 UTCresolved

   Between 13:40 and 14:10 UTC, a subset of Crowdin Enterprise users experienced server errors when attempting to access projects via the web interface (UI). The issue affected users with specific project configurations. Access via the API remained operational. The service was fully available for translators, though. Our team identified and deployed a fix for the underlying server issue. The problem is resolved, and project access is fully restored. If you were affected by this issue, please refresh your browser page to ensure full functionality. We apologize for the inconvenience.

1. 20 октября 2025 г. в 20:16 UTCmonitoring

   We have noticed that builds are failing or taking longer than usual due to an issue with the cloud provider. This issue is not global; we are continuing to monitor the status. We will update the status once we confirm that the builds are working properly.

2. 20 октября 2025 г. в 20:29 UTCresolved

   Almost right after the incident was raised, the project builds started working as expected. After conducting various tests, we can confirm that the builds have returned to normal, and the incident can be considered resolved.

1. 20 октября 2025 г. в 10:25 UTCmonitoring

   As you may be aware, Amazon AWS has experienced a major service disruption. The initial reports were logged at 8:11 am UTC, and within an hour, we noticed that translations export via UI and API started to fail almost instantly. Other components of Crowdin (dashboard, translation editor) were not impacted. We hope that it did not affect your work significantly. Our ticketing system got impacted too, and we couldn't react to the live chat efficiently. Sorry about that. All services are operational currently. We will keep monitoring the situation and update the incident once we confirm that every Crowdin component works as usual.

2. 20 октября 2025 г. в 12:39 UTCresolved

   After nearly 3 hours of monitoring, we confirm that translations are exported on time, and all connectors are fully accessible. We consider the case as resolved.

1. 10 октября 2025 г. в 14:58 UTCidentified

   Our team has spotted a performance downgrade at Crowdin Enterprise. We are continuing to monitor the situation and work on a resolution.

2. 10 октября 2025 г. в 15:06 UTCmonitoring

   Everything appears to be working properly. We will continue to monitor the system.

3. 10 октября 2025 г. в 15:30 UTCresolved

   After additional monitoring, we can confirm that the service is fully operational

1. 10 октября 2025 г. в 14:34 UTCinvestigating

   We noticed unusual behavior on the project dashboard, and the API is working more slowly than usual. It's being investigated further by our development team.

2. 10 октября 2025 г. в 14:41 UTCresolved

   All services are fully operational

1. 11 января 2025 г. в 08:09 UTCresolved

   We experienced a temporary downtime of our Downloads and redirect service, which impacted the ability of some users to download translations.

1. 9 января 2025 г. в 22:20 UTCinvestigating

   We noticed that most of the apps are malfunctioning right now, other services (e.g. translation editor, API) function as usual. We are investigating it already

2. 9 января 2025 г. в 22:29 UTCmonitoring

   A fix has been implemented, we will monitor the status for a while

3. 9 января 2025 г. в 22:32 UTCresolved

   The store is fully functioning again, along with all its apps 🙌

1. 10 декабря 2024 г. в 09:13 UTCinvestigating

   We noticed unusual performance on Crowdin, already started investigating it

2. 10 декабря 2024 г. в 09:19 UTCmonitoring

   The service got back to normal, but we keep monitoring the results.

3. 10 декабря 2024 г. в 09:27 UTCresolved

   This accident has been fully resolved, after monitoring we confirmed that all functionality returned to normal

1. 21 ноября 2024 г. в 14:10 UTCresolved

   Between 13:19 and 13:36 UTC, we experienced performance degradation in crowdin.com and Crowdin Enterprise. The issue has been resolved, and the services are now operating normally.

1. 14 ноября 2022 г. в 09:06 UTCinvestigating

   When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

2. 14 ноября 2022 г. в 09:06 UTCidentified

   As you continue to work through the incident, update your customers frequently.

3. 14 ноября 2022 г. в 09:06 UTCmonitoring

   Let your users know once a fix is in place, and keep communication clear and precise.

4. 14 ноября 2022 г. в 09:06 UTCresolved

   Empathize with those affected and let them know everything is operating as normal.