Crowdin 장애 기록

1. 2026년 10월 22일 오전 11:13 UTCinvestigating

   우리는 현재 Crowdin Enterprise의 느린 수명을 경험하고 있습니다. 우리 팀은 문제의 인식이며 적극적으로 투자하고 있습니다. 우리는 가능한 빨리 정상적인 성과를 복원하는 일입니다.

2. 2026년 10월 22일 오전 11:22 UTCidentified

   Crowdin Enterprise의 성능 향상의 근본적인 원인을 확인했으며 이를 해결하기 위해 단계가 있습니다. 우리는 상황을 모니터링하고 진행 상황을 제공합니다.

3. 2026년 10월 22일 오전 11:25 UTCresolved

   The performance issue affecting Crowdin Enterprise has been resolved, and the service is now operating normally.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 7일 오후 6:27 UTCresolved

   제품 설명 우리는 상태 페이지 보고 문제점을 해결하고 잘못된 사건 기록을 삭제했습니다 7 시간 및 Crowdin 번역을 위한 가동불능시간의 53 분. 서비스는 완전히 가동되었습니다 - 실제 가동 중단 또는 사용자 충격이 없었습니다. 어떤 출혈? false "Major Outage"상태는 자동화 알림 글리트에 의해 유발되었습니다. 두 개의 충돌 업데이트 (DOWN 및 UP)은 정확히 같은 시간에 도착했습니다. 경기 조건으로 인해 DOWN 경고를 처리했지만, 부정확한 상태에 갇힌 상태 페이지를 무시했습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 3월 16일 오전 8: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. 2026년 3월 16일 오전 9: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. 2026년 3월 16일 오전 9: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. 2026년 3월 16일 오전 9: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. 2026년 1월 19일 오후 2: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. 2026년 1월 19일 오후 2: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. 2025년 11월 12일 오후 4: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. 2025년 10월 20일 오후 8: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. 2025년 10월 20일 오후 8: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. 2025년 10월 20일 오전 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. 2025년 10월 20일 오후 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. 2025년 10월 10일 오후 2: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. 2025년 10월 10일 오후 3:06 UTCmonitoring

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

3. 2025년 10월 10일 오후 3:30 UTCresolved

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

1. 2025년 10월 10일 오후 2: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. 2025년 10월 10일 오후 2:41 UTCresolved

   All services are fully operational

1. 2025년 1월 11일 오전 8:09 UTCresolved

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

1. 2025년 1월 9일 오후 10: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. 2025년 1월 9일 오후 10:29 UTCmonitoring

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

3. 2025년 1월 9일 오후 10:32 UTCresolved

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

1. 2024년 12월 10일 오전 9:13 UTCinvestigating

   We noticed unusual performance on Crowdin, already started investigating it

2. 2024년 12월 10일 오전 9:19 UTCmonitoring

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

3. 2024년 12월 10일 오전 9:27 UTCresolved

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

1. 2024년 11월 21일 오후 2: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. 2022년 11월 14일 오전 9: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. 2022년 11월 14일 오전 9:06 UTCidentified

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

3. 2022년 11월 14일 오전 9:06 UTCmonitoring

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

4. 2022년 11월 14일 오전 9:06 UTCresolved

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