Brand Portal users and integration may have limited access.

Update timeline

1. investigating Sep 19, 2024, 10:09 PM UTC

   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. identified Sep 19, 2024, 11:26 PM UTC

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

3. monitoring Sep 19, 2024, 11:42 PM UTC

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

4. identified Sep 20, 2024, 03:50 PM UTC

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

5. identified Sep 20, 2024, 05:45 PM UTC

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

6. monitoring Sep 20, 2024, 11:19 PM UTC

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

7. monitoring Sep 23, 2024, 02:02 PM UTC

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

8. identified Sep 23, 2024, 04:58 PM UTC

   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. monitoring Sep 24, 2024, 12:46 AM UTC

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

10. monitoring Sep 24, 2024, 09:42 PM UTC

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

11. investigating Sep 25, 2024, 04:35 PM UTC

    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.

12. monitoring Sep 25, 2024, 08:49 PM UTC

    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. investigating Sep 26, 2024, 04:02 PM UTC

    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.

14. identified Sep 26, 2024, 05:31 PM UTC

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

15. monitoring Sep 26, 2024, 08:57 PM UTC

    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.

16. monitoring Sep 26, 2024, 08:57 PM UTC

    We are continuing to monitor for any further issues.

17. investigating Sep 27, 2024, 04:05 PM UTC

    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.

18. monitoring Sep 27, 2024, 11:36 PM UTC

    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.

19. investigating Sep 30, 2024, 03:25 PM UTC

    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.

20. identified Sep 30, 2024, 03:42 PM UTC

    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.

21. monitoring Oct 01, 2024, 11:19 PM UTC

    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.

22. investigating Oct 03, 2024, 05:37 PM UTC

    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.

23. identified Oct 03, 2024, 08:34 PM UTC

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

24. investigating Oct 07, 2024, 06:50 PM UTC

    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

25. identified Oct 08, 2024, 04:54 PM UTC

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

26. investigating Oct 09, 2024, 04:05 PM UTC

    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.

27. investigating Oct 11, 2024, 05:58 PM UTC

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

28. identified Oct 14, 2024, 05:54 PM UTC

    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.

29. monitoring Oct 15, 2024, 12:13 AM UTC

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

30. monitoring Oct 15, 2024, 06:41 PM UTC

    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).

31. resolved Oct 17, 2024, 12:54 AM UTC

    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.