Istoricul incidentelor Webdam

1. 14 septembrie 2026 la 16:20 UTCinvestigating

   Investigăm activ un incident care cauzează erori intermitente 502 Bad Gateway, latență de navigație, și întârzieri de încărcare/scărcare pentru utilizatorii Webdam. În timp ce echipa noastră de inginerie lucrează pentru a identifica cauza rădăcină în infrastructura backend, utilizatorii pot încerca reconfortant pagina lor ca o muncă temporară în jurul. Vom furniza actualizări suplimentare pe măsură ce vor fi disponibile mai multe informații.

2. 14 septembrie 2026 la 16:21 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 14 septembrie 2026 la 17:16 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

4. 14 septembrie 2026 la 19:33 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

5. 14 septembrie 2026 la 21:55 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 16 ianuarie 2026 la 23: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. 16 ianuarie 2026 la 23:50 UTCmonitoring

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

3. 17 ianuarie 2026 la 00:12 UTCresolved

   This incident has been resolved.

1. 20 octombrie 2025 la 21: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. 21 octombrie 2025 la 00: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. 21 octombrie 2025 la 17:57 UTCresolved

   This incident has been resolved.

1. 13 august 2025 la 17:40 UTCinvestigating

   We are currently investigating reports that Webdam is not loading.

2. 13 august 2025 la 18:25 UTCresolved

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

1. 11 aprilie 2025 la 15:52 UTCinvestigating

   We are currently investigating issues.

2. 11 aprilie 2025 la 16:21 UTCidentified

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

3. 11 aprilie 2025 la 18:02 UTCidentified

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

4. 11 aprilie 2025 la 20:29 UTCmonitoring

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

5. 11 aprilie 2025 la 23:01 UTCresolved

   The incident has been resolved.

1. 25 februarie 2025 la 21:13 UTCinvestigating

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

2. 25 februarie 2025 la 22:37 UTCidentified

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

3. 26 februarie 2025 la 16:36 UTCmonitoring

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

4. 26 februarie 2025 la 20: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. 28 februarie 2025 la 00: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. 1 martie 2025 la 00: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. 3 martie 2025 la 20:48 UTCresolved

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

1. 4 noiembrie 2024 la 18:37 UTCinvestigating

   We are currently investigating this issue.

2. 4 noiembrie 2024 la 19:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 noiembrie 2024 la 19:42 UTCidentified

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

4. 4 noiembrie 2024 la 19:49 UTCmonitoring

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

5. 4 noiembrie 2024 la 20:56 UTCresolved

   The incident around assets stuck processing has been resolved.

1. 19 septembrie 2024 la 22: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. 19 septembrie 2024 la 23:26 UTCidentified

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

3. 19 septembrie 2024 la 23:42 UTCmonitoring

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

4. 20 septembrie 2024 la 15:50 UTCidentified

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

5. 20 septembrie 2024 la 17:45 UTCidentified

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

6. 20 septembrie 2024 la 23: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. 23 septembrie 2024 la 14:02 UTCmonitoring

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

8. 23 septembrie 2024 la 16: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. 24 septembrie 2024 la 00:46 UTCmonitoring

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

10. 24 septembrie 2024 la 21:42 UTCmonitoring

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

11. 26 septembrie 2024 la 17:31 UTCidentified

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

12. 26 septembrie 2024 la 20: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. 26 septembrie 2024 la 20:57 UTCmonitoring

    We are continuing to monitor for any further issues.

14. 27 septembrie 2024 la 23: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. 30 septembrie 2024 la 15: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. 30 septembrie 2024 la 15: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. 1 octombrie 2024 la 23: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. 3 octombrie 2024 la 17: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. 3 octombrie 2024 la 20:34 UTCidentified

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

20. 7 octombrie 2024 la 18: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. 8 octombrie 2024 la 16:54 UTCidentified

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

22. 9 octombrie 2024 la 16: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. 11 octombrie 2024 la 17:58 UTCinvestigating

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

24. 14 octombrie 2024 la 17: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. 15 octombrie 2024 la 00:13 UTCmonitoring

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

26. 15 octombrie 2024 la 18: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. 17 octombrie 2024 la 00: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. 2 septembrie 2024 la 08:57 UTCinvestigating

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

2. 2 septembrie 2024 la 09:09 UTCmonitoring

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

3. 2 septembrie 2024 la 13:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2 septembrie 2024 la 13:20 UTCresolved

   This incident has been resolved.

1. 29 iulie 2024 la 14:02 UTCinvestigating

   We are currently investigating reports that Webdam is not loading.

2. 29 iulie 2024 la 14:08 UTCidentified

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

3. 29 iulie 2024 la 14:15 UTCidentified

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

4. 29 iulie 2024 la 14:30 UTCmonitoring

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

5. 29 iulie 2024 la 18:48 UTCresolved

   The incident has been resolved.

1. 22 iulie 2024 la 07:58 UTCinvestigating

   We are currently investigating this issue.

2. 22 iulie 2024 la 10:47 UTCidentified

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

3. 22 iulie 2024 la 10:56 UTCmonitoring

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

4. 22 iulie 2024 la 17:05 UTCresolved

   This incident has been resolved.

1. 19 iulie 2024 la 16:01 UTCinvestigating

   We are currently investigating this issue.

2. 19 iulie 2024 la 16:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 iulie 2024 la 16:25 UTCidentified

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

4. 19 iulie 2024 la 22:29 UTCmonitoring

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

5. 20 iulie 2024 la 00:24 UTCresolved

   This incident has been resolved.

1. 10 iulie 2024 la 15:37 UTCinvestigating

   We are currently investigating this issue.

2. 10 iulie 2024 la 16:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 iulie 2024 la 16:22 UTCidentified

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

4. 10 iulie 2024 la 16:50 UTCmonitoring

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

5. 10 iulie 2024 la 16:59 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 10 iulie 2024 la 18:09 UTCresolved

   This incident has been resolved.

1. 1 iulie 2024 la 16:34 UTCinvestigating

   We are currently investigating this issue.

2. 1 iulie 2024 la 16:43 UTCinvestigating

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

3. 1 iulie 2024 la 18:38 UTCidentified

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

4. 1 iulie 2024 la 19:07 UTCidentified

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

5. 1 iulie 2024 la 21: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. 2 iulie 2024 la 13:13 UTCresolved

   This incident has been resolved.

1. 20 iunie 2024 la 18:01 UTCinvestigating

   We are currently investigating this issue.

2. 20 iunie 2024 la 20:11 UTCidentified

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

3. 21 iunie 2024 la 13:49 UTCresolved

   This incident has been resolved.

1. 14 iunie 2024 la 15:16 UTCinvestigating

   We are currently investigating brand portal view not fully loading.

2. 14 iunie 2024 la 16:34 UTCidentified

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

3. 14 iunie 2024 la 19:08 UTCmonitoring

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

4. 14 iunie 2024 la 19:42 UTCresolved

   This incident has been resolved.

1. 11 iunie 2024 la 22:05 UTCinvestigating

   We are currently investigating this issue

2. 11 iunie 2024 la 22:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 iunie 2024 la 23:03 UTCidentified

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

4. 12 iunie 2024 la 01:49 UTCidentified

   A fix has been identified and is being reviewed

5. 12 iunie 2024 la 15:53 UTCmonitoring

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

6. 13 iunie 2024 la 16:16 UTCresolved

   This issue has been confirmed to be resolved.

1. 10 iunie 2024 la 20:32 UTCinvestigating

   We are currently investigating download request delays.

2. 10 iunie 2024 la 20:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 iunie 2024 la 20:46 UTCidentified

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

4. 10 iunie 2024 la 22:08 UTCmonitoring

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

5. 11 iunie 2024 la 00:47 UTCresolved

   The incident has been resolved.

1. 21 mai 2024 la 14:44 UTCinvestigating

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

2. 21 mai 2024 la 15:31 UTCidentified

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

3. 21 mai 2024 la 17:27 UTCmonitoring

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

4. 21 mai 2024 la 22:16 UTCresolved

   This incident has been resolved.

1. 15 mai 2024 la 19:31 UTCinvestigating

   We are currently investigating this issue.

2. 15 mai 2024 la 20:45 UTCinvestigating

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

3. 15 mai 2024 la 22:37 UTCmonitoring

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

4. 16 mai 2024 la 16:51 UTCresolved

   This incident for download request has been resolved.