IAM and DCD Availability Issues
<p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>18:55</var> UTC</small><br><strong>Resolved</strong> - We are marking this incident as resolved. We will compile a Root Cause Analysis and will publish it as an update to this incident.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>18:24</var> UTC</small><br><strong>Monitoring</strong> - We have recovered the affected Object Storage and are currently monitoring the recovery of affected systems and services.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>18:24</var> UTC</small><br><strong>Update</strong> - We have recovered the affected Object Storage and are currently monitoring the recovery of affected systems and services.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>17:57</var> UTC</small><br><strong>Update</strong> - We have traced the issue to an internal object storage system. Our infrastructure team is currently working on recovery. At this time, users may continue to experience DCD login issues, IAM service disruptions, and delays or errors related to provisioning. We see no evidence of further user-facing network issues and are updating the status accordingly.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>17:08</var> UTC</small><br><strong>Identified</strong> - We have identified a connectivity issue preventing our identity service to reach an upstream database. Our Operations Team is currently working to mitigate the connectivity issue. We will be updating this page regularly to keep you informed about our progress.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>16:37</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>16:35</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating alerts related to DCD and IAM service availability in TXL DC</p>