Webdam 장애 기록

1. 2026년 9월 14일 오후 4:20 UTCinvestigating

   우리는 간헐적인 502 나쁜 게이트웨이 오류, 탐색 대기 시간 및 Webdam 사용자에 대한 업로드 / 다운로드 지연을 유발하는 사건을 적극적으로 조사하고 있습니다. 엔지니어링 팀은 백엔드 인프라의 루트 원인을 식별하는 데 종사하는 동안 사용자는 임시 작업으로 페이지를 새로 고침 할 수 있습니다. 더 많은 정보로 더 많은 업데이트를 제공할 것입니다.

2. 2026년 9월 14일 오후 4:21 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 9월 14일 오후 5:16 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

4. 2026년 9월 14일 오후 7:33 UTCmonitoring

   수정이 시행되고, 결과를 모니터링하고 있습니다.

5. 2026년 9월 14일 오후 9:55 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 1월 16일 오후 11:07 UTCinvestigating

   We are currently experiencing issues with downloads. We are working hard on the solution of this problem and will keep you updated on the progress.

2. 2026년 1월 16일 오후 11:50 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 1월 17일 오전 12:12 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오후 9:33 UTCinvestigating

   There are ongoing issues related to uploads and downloads due to the ongoing AWS incident. Assets may get stuck in processing when uploading and asset downloads may fail. We are working hard on the solution of this problem and will keep you updated on the progress.

2. 2025년 10월 21일 오전 12:32 UTCmonitoring

   The issue surrounding delays for uploading and downloading assets has been resolved. We will continue to monitor this situation. There are still ongoing issues related to displaying of thumbnails for certain customers due to the ongoing AWS incident. Our team is still looking into this with AWS at this time.

3. 2025년 10월 21일 오후 5:57 UTCresolved

   This incident has been resolved.

1. 2025년 8월 13일 오후 5:40 UTCinvestigating

   We are currently investigating reports that Webdam is not loading.

2. 2025년 8월 13일 오후 6:25 UTCresolved

   A fix has been implemented, and we are monitoring the results.

1. 2025년 4월 11일 오후 3:52 UTCinvestigating

   We are currently investigating issues.

2. 2025년 4월 11일 오후 4:21 UTCidentified

   The issue has been identified, and we are working on a solution.

3. 2025년 4월 11일 오후 6:02 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2025년 4월 11일 오후 8:29 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

5. 2025년 4월 11일 오후 11:01 UTCresolved

   The incident has been resolved.

1. 2025년 2월 25일 오후 9:13 UTCinvestigating

   We are investigating reports of delayed or not receiving email notifications.

2. 2025년 2월 25일 오후 10:37 UTCidentified

   The issue has been identified, and we are working on a solution.

3. 2025년 2월 26일 오후 4:36 UTCmonitoring

   A fix has been implemented, and we are monitoring the results of email deliveries.

4. 2025년 2월 26일 오후 8:00 UTCmonitoring

   We are continuing to monitor the email deliveries. However, if you feel like you are having issues, please get in touch with [email protected] for assistance.

5. 2025년 2월 28일 오전 12:21 UTCmonitoring

   We have rolled out a fix to address email delivery issues. However, depending on your email security tools, our emails may still be blocked. We are actively working with our email vendor to resolve this at their level. If you're encountering any issues or need further assistance, please reach out to us at [email protected].

6. 2025년 3월 1일 오전 12:58 UTCmonitoring

   We have rolled out a fix to address email delivery. However, our emails may still be blocked depending on your email security tools. We are continuing to collaborate with our email vendor to address this issue at their level. If you encounter any issues or need further assistance, please get in touch with us at [email protected].

7. 2025년 3월 3일 오후 8:48 UTCresolved

   This incident has been resolved. Email delivery is now functional.

1. 2024년 11월 4일 오후 6:37 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 11월 4일 오후 7:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 11월 4일 오후 7:42 UTCidentified

   The issue has been identified, and a fix is being implemented.

4. 2024년 11월 4일 오후 7:49 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

5. 2024년 11월 4일 오후 8:56 UTCresolved

   The incident around assets stuck processing has been resolved.

1. 2024년 9월 19일 오후 10:09 UTCinvestigating

   Brand Portal is accessible, but if users encounter an error, please have them refresh the page. We are currently investigating API errors connected with integration access.

2. 2024년 9월 19일 오후 11:26 UTCidentified

   The issue for Brand Portal access has been identified, and a fix is being implemented.

3. 2024년 9월 19일 오후 11:42 UTCmonitoring

   A fix has been implemented for BP access and API errors. We are monitoring the results.

4. 2024년 9월 20일 오후 3:50 UTCidentified

   The team has identified issues with access to Brand Portal and integration, and a fix is being implemented.

5. 2024년 9월 20일 오후 5:45 UTCidentified

   We are actively working on implementing a fix for all the affected servers.

6. 2024년 9월 20일 오후 11:19 UTCmonitoring

   API is now operational; we're still addressing some intermittent timeouts with the BP (refreshing the page should resolve any ongoing issues).

7. 2024년 9월 23일 오후 2:02 UTCmonitoring

   We are addressing some intermittent timeouts with the BP (refreshing the page should resolve any ongoing issues).

8. 2024년 9월 23일 오후 4:58 UTCidentified

   We are addressing intermittent timeouts with the Brand Portal. But if users encounter an error, please have them refresh the page. We are currently investigating API errors.

9. 2024년 9월 24일 오전 12:46 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

10. 2024년 9월 24일 오후 9:42 UTCmonitoring

    We are continuing to monitor the results of our fix. If you experience any errors, please contact Support.

11. 2024년 9월 26일 오후 5:31 UTCidentified

    The team has identified issues and a fix is being implemented.

12. 2024년 9월 26일 오후 8:57 UTCmonitoring

    A fix has been deployed to address the ongoing issues. We are currently monitoring the results to ensure stability. If you encounter any errors, please contact Support.

13. 2024년 9월 26일 오후 8:57 UTCmonitoring

    We are continuing to monitor for any further issues.

14. 2024년 9월 27일 오후 11:36 UTCmonitoring

    A fix has been deployed to address the ongoing issues. We are currently monitoring the results to ensure stability and have confirmed a reduction in errors. If you encounter an error logging in, please refresh your web browser. If an API call fails with a 5xx error, retrying the call should be successful.

15. 2024년 9월 30일 오후 3:25 UTCinvestigating

    While a potential cause was previously identified, related problems persist. Our teams are actively working on further solutions and monitoring the situation closely. As a temporary workaround, refreshing the page or retrying the API call should resolve the issue. We will provide updates as new information becomes available.

16. 2024년 9월 30일 오후 3:42 UTCidentified

    As a temporary workaround, refreshing the page or retrying the API call should resolve the issue. The team has identified issues and a fix is being implemented.

17. 2024년 10월 1일 오후 11:19 UTCmonitoring

    The API is now operational, but you may still encounter some login/logout errors in BP/Core as the system works through the backlog. We are actively monitoring the situation to ensure everything stabilizes as quickly as possible.

18. 2024년 10월 3일 오후 5:37 UTCinvestigating

    We are conducting further investigation into the BP/Core performance. While BP/Core is currently accessible, please refresh the page if users experience any errors. The API remains operational.

19. 2024년 10월 3일 오후 8:34 UTCidentified

    The BP/Core issue has been identified and a fix is being implemented. The API remains operational.

20. 2024년 10월 7일 오후 6:50 UTCinvestigating

    We are having issues with Single Sign-On (SSO) login and logout functionalities. Our engineering team is investigating the problem and working on a fix. In the meantime, you may try the following steps to mitigate the problem: - Refresh your page - Clear your cache and cookies - Use a different browser

21. 2024년 10월 8일 오후 4:54 UTCidentified

    We have identified the issue, and we are currently upgrading our servers with a fix.

22. 2024년 10월 9일 오후 4:05 UTCinvestigating

    While a potential cause was previously identified, related problems persist. We are conducting further investigation into patterns with the BP/Core SSO and local users login and logout functionalities.

23. 2024년 10월 11일 오후 5:58 UTCinvestigating

    We are continuing our investigation with login and logout issues. Please refresh your webpage as a temporary workaround.

24. 2024년 10월 14일 오후 5:54 UTCidentified

    Our engineering team has identified the issue with our servers and will be implementing a fix. Portals should begin to see improvements following this update.

25. 2024년 10월 15일 오전 12:13 UTCmonitoring

    Our engineering team has implemented a fix for our servers, and we are now monitoring server behavior closely.

26. 2024년 10월 15일 오후 6:41 UTCmonitoring

    We are still monitoring the fix that has been implemented. If you continue to encounter issues, please try the following steps: Clear your cache and cookies. Remove any bookmarks related to the portal. Access the portal using your domain URL (e.g., your-webdam-domain.webdamdb.com).

27. 2024년 10월 17일 오전 12:54 UTCresolved

    Following several identified improvement areas, we’ve seen a notable decline in error reports. As a result, we are now marking this incident as resolved. We are reclassifying it as a bug priority rather than closing it completely. We will continue to work on this in our current sprint. Future updates will be communicated directly through your support ticket rather than via this status page. Please submit a support ticket if you are still experiencing this issue and haven’t yet reported it. This will help our teams focus on higher-priority issues impacting the platform. Thank you for your understanding and cooperation.

1. 2024년 9월 2일 오전 8:57 UTCinvestigating

   We have identified the issue and a fix is being implemented.

2. 2024년 9월 2일 오전 9:09 UTCmonitoring

   A fix has been implemented and we are continuing to monitor for any further issues.

3. 2024년 9월 2일 오후 1:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2024년 9월 2일 오후 1:20 UTCresolved

   This incident has been resolved.

1. 2024년 7월 29일 오후 2:02 UTCinvestigating

   We are currently investigating reports that Webdam is not loading.

2. 2024년 7월 29일 오후 2:08 UTCidentified

   The issue has been identified, and a fix has been implemented.

3. 2024년 7월 29일 오후 2:15 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2024년 7월 29일 오후 2:30 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

5. 2024년 7월 29일 오후 6:48 UTCresolved

   The incident has been resolved.

1. 2024년 7월 22일 오전 7:58 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 22일 오전 10:47 UTCidentified

   the issue has been identified, and a fix is being implemented.

3. 2024년 7월 22일 오전 10:56 UTCmonitoring

   The fix has been implemented, and we are monitoring the results.

4. 2024년 7월 22일 오후 5:05 UTCresolved

   This incident has been resolved.

1. 2024년 7월 19일 오후 4:01 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 19일 오후 4:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 7월 19일 오후 4:25 UTCidentified

   Due to the global Cloudstrike issue, Workstream proofing is currently unavailable. We will provide an update once we have more information.

4. 2024년 7월 19일 오후 10:29 UTCmonitoring

   A 3rd party fix has been implemented, and we are monitoring the results.

5. 2024년 7월 20일 오전 12:24 UTCresolved

   This incident has been resolved.

1. 2024년 7월 10일 오후 3:37 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 10일 오후 4:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 7월 10일 오후 4:22 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 2024년 7월 10일 오후 4:50 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2024년 7월 10일 오후 4:59 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2024년 7월 10일 오후 6:09 UTCresolved

   This incident has been resolved.

1. 2024년 7월 1일 오후 4:34 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 1일 오후 4:43 UTCinvestigating

   While we are investigating a single download issue, batch download requests are still operational and can be used if needed.

3. 2024년 7월 1일 오후 6:38 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 2024년 7월 1일 오후 7:07 UTCidentified

   We are continuing to work on a fix for single download requests and asset processing.

5. 2024년 7월 1일 오후 9:23 UTCmonitoring

   A fix has been implemented and single downloads are working, there is a processing delay due the system backlog catching up and we expect it to finish processing within a few hours.

6. 2024년 7월 2일 오후 1:13 UTCresolved

   This incident has been resolved.

1. 2024년 6월 20일 오후 6:01 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 6월 20일 오후 8:11 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 6월 21일 오후 1:49 UTCresolved

   This incident has been resolved.

1. 2024년 6월 14일 오후 3:16 UTCinvestigating

   We are currently investigating brand portal view not fully loading.

2. 2024년 6월 14일 오후 4:34 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 6월 14일 오후 7:08 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 6월 14일 오후 7:42 UTCresolved

   This incident has been resolved.

1. 2024년 6월 11일 오후 10:05 UTCinvestigating

   We are currently investigating this issue

2. 2024년 6월 11일 오후 10:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 6월 11일 오후 11:03 UTCidentified

   The issue has been identified, and a fix is being developed.

4. 2024년 6월 12일 오전 1:49 UTCidentified

   A fix has been identified and is being reviewed

5. 2024년 6월 12일 오후 3:53 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

6. 2024년 6월 13일 오후 4:16 UTCresolved

   This issue has been confirmed to be resolved.

1. 2024년 6월 10일 오후 8:32 UTCinvestigating

   We are currently investigating download request delays.

2. 2024년 6월 10일 오후 8:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 6월 10일 오후 8:46 UTCidentified

   The issue has been identified, and a fix is being implemented.

4. 2024년 6월 10일 오후 10:08 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

5. 2024년 6월 11일 오전 12:47 UTCresolved

   The incident has been resolved.

1. 2024년 5월 21일 오후 2:44 UTCinvestigating

   We are currently investigating a report of latency in accessing the DAM

2. 2024년 5월 21일 오후 3:31 UTCidentified

   The issue has been identified, and a fix is being implemented.

3. 2024년 5월 21일 오후 5:27 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

4. 2024년 5월 21일 오후 10:16 UTCresolved

   This incident has been resolved.

1. 2024년 5월 15일 오후 7:31 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 5월 15일 오후 8:45 UTCinvestigating

   A fix has been implemented, and we are monitoring the results.

3. 2024년 5월 15일 오후 10:37 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

4. 2024년 5월 16일 오후 4:51 UTCresolved

   This incident for download request has been resolved.