-
Time: May 28, 2024, 1:02 a.m.
Status: Resolved
Update: This incident has been resolved.
-
Time: May 23, 2024, 7:51 p.m.
Status: Monitoring
Update: All DSM SaaS AMER|UK|AU|EU|APAC regions are fully operational and currently under monitoring.
-
Time: May 23, 2024, 5:45 a.m.
Status: Monitoring
Update: AU, UK, EU, AMER regions are now fully operational, permanent fix for APAC will be applied at 18:00 UTC today.
-
Time: May 23, 2024, 4:15 a.m.
Status: Monitoring
Update: AU, UK & EU regions are now fully operational, permanent fix for AMER is in progress and for APAC fix will be applied at 18:00 UTC
-
Time: May 22, 2024, 3:57 p.m.
Status: Monitoring
Update: AU & UK region both are now fully operational after the provider implemented the fix; permanent fixes for AMER, APAC & EU will be applied in a scheduled change window with prior customer notification.
-
Time: May 22, 2024, 1:05 p.m.
Status: Monitoring
Update: UK region is now fully operational after the provider implemented the fix; permanent fixes for AMER, APAC, AU, and EU will be applied in a scheduled change window with prior customer notification.
-
Time: May 22, 2024, 2:08 a.m.
Status: Monitoring
Update: We are actively monitoring for any further issues in all DSM SaaS regions. Our provider has identified the issue and working on a permanent fix.
-
Time: May 21, 2024, 10:07 p.m.
Status: Monitoring
Update: We are actively monitoring for any further issues in all DSM SaaS regions. Our provider is still working on a permanent fix.
-
Time: May 21, 2024, 7:24 p.m.
Status: Monitoring
Update: We are actively monitoring for any further issues in all DSM SaaS regions. Our provider is still working on a permanent fix.
-
Time: May 21, 2024, 4:57 p.m.
Status: Monitoring
Update: All regions are currently in a monitoring state. We are working with our provider to determine if the issue is resolved.
-
Time: May 21, 2024, 3:11 p.m.
Status: Monitoring
Update: We are continuing to monitor for any further issues.
-
Time: May 21, 2024, 3 p.m.
Status: Monitoring
Update: We are continuing to monitor for any further issues in our DSM SaaS. Our provider is still working on implementing a permanent solution.
-
Time: May 21, 2024, 2:20 p.m.
Status: Monitoring
Update: After the workaround was implemented, all regions are currently in a monitoring state. Furthermore, our provider is still working on implementing a permanent solution.
-
Time: May 21, 2024, 2:14 p.m.
Status: Monitoring
Update: After the workaround was implemented, all regions are currently in a monitoring state. AMER and EU regions are fully operational. Furthermore, our provider is still working on implementing a permanent solution.
-
Time: May 21, 2024, 2:04 p.m.
Status: Identified
Update: AMER and EU are up and currently in a monitoring state. APAC, AU, and UK have limited access with the workaround functioning properly. Our provider is still working on implementing a permanent solution.
-
Time: May 21, 2024, 1:11 p.m.
Status: Identified
Update: All regions now have limited access, and the workaround is functioning properly. Our provider is still working to implement a permanent solution.
-
Time: May 21, 2024, 12:35 p.m.
Status: Identified
Update: With the workaround, all regions have limited access. Our provider is still working on a permanent solution.
-
Time: May 21, 2024, 11:59 a.m.
Status: Identified
Update: With the workaround implemented, all regions are accessible at limited capacity. Our provider is still working towards implementing a permanent fix as well.
-
Time: May 21, 2024, 11:26 a.m.
Status: Investigating
Update: We are actively rolling out the workaround across all regions. Our provider is working toward implementing a permanent fix. We will update further.
-
Time: May 21, 2024, 10:42 a.m.
Status: Investigating
Update: The roll out of the workaround is still in progress across regions and our provider is continuing to work on a permanent fix. Further updates will be provided soon.
-
Time: May 21, 2024, 10:08 a.m.
Status: Investigating
Update: The roll out of the workaround is still in progress, and our provider is continuing to work on a permanent fix. We appreciate your patience and will provide further updates as they become available.
-
Time: May 21, 2024, 9:42 a.m.
Status: Investigating
Update: We are deploying a workaround. The Provider team is still working on a permanent fix. Further updates will follow as we progress.
-
Time: May 21, 2024, 9:06 a.m.
Status: Investigating
Update: We have verified a workaround and will proceed with deployment. Concurrently, our provider is working internally to find a viable solution and fix the issue.
-
Time: May 21, 2024, 8:30 a.m.
Status: Investigating
Update: Our team continues to work diligently with our vendor and on internal workaround solutions. We appreciate your continued patience and will keep you updated with any new developments. Thank you for your understanding.
-
Time: May 21, 2024, 8 a.m.
Status: Investigating
Update: Troubleshooting with our vendor is still in progress, and we are actively working on a workaround solution. We will inform you as soon as we make progress with the workaround.
-
Time: May 21, 2024, 7:21 a.m.
Status: Investigating
Update: The issue with our provider persists, but we are actively working on an internal workaround to mitigate the impact.
-
Time: May 21, 2024, 6:44 a.m.
Status: Investigating
Update: Our team is still working closely with our provider to address the situation. We understand the impact this may have and appreciate your continued patience.
-
Time: May 21, 2024, 6:04 a.m.
Status: Investigating
Update: We are continuing to work closely with our provider to resolve the ongoing issue. Our teams are fully engaged and we appreciate your patience as we work towards a resolution.
-
Time: May 21, 2024, 5:12 a.m.
Status: Investigating
Update: The issue has been identified with one of our providers, and we are working with them to fix it.
-
Time: May 21, 2024, 2:37 a.m.
Status: Investigating
Update: We are continuing to investigate this issue.
-
Time: May 21, 2024, 1:20 a.m.
Status: Investigating
Update: We are currently investigating this issue.