ASGL Service Status Status - Incident history https://asgl.instatus.com ASGL Service Status Thu, 5 Jun 2025 17:55:00 +0000 Loss of messaging platform Type: Incident Duration: 6 hours and 5 minutes Affected Components: Messaging Platform, Contact Centre Jun 6, 00:00:00 GMT+0 - Resolved - Microsoft have rectified the issue and service is now resumed. Jun 5, 17:55:00 GMT+0 - Investigating - Our Azure Database is currently offline and we're escalating with Microsoft. We're able to answer calls, but we currently do not have access to our complete messaging platform. Jun 22, 08:42:09 GMT+0 - Postmortem - The following is the RCA from Microsoft regarding this issue: What happened: Between June 5, 2025, 18:15 UTC and June 6, 2025, 01:29:14 UTC, the SQL Managed Instance pearlsqlmi experienced intermittent unavailability and connectivity issues. Cause: This was caused by multiple failovers triggered by a rare race condition during the rotation of the encryption protector on databases that contain memory-optimized tables. Mitigation Once the root cause was identified, we implemented manual mitigation steps to restore stability. Monitoring and alerting systems remain active to detect any recurrence. This issue is highly unlikely to reoccur and is only triggered during encryption protector changes. Next steps Product team is currently validating a permanent fix, which will be included in an upcoming release. In the meantime, we recommend avoiding encryption protector changes during peak usage hours to minimize potential impact, since during that period you have a slightly higher chance of this particular race condition happening. Type: Incident

Duration: 6 hours and 5 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft have rectified the issue and service is now resumed. .</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>17:55:00</var> GMT+0</small><br><strong>Investigating</strong> - Our Azure Database is currently offline and we're escalating with Microsoft. We're able to answer calls, but we currently do not have access to our complete messaging platform..</p> <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>08:42:09</var> GMT+0</small><br><strong>Postmortem</strong> - The following is the RCA from Microsoft regarding this issue: What happened: Between June 5, 2025, 18:15 UTC and June 6, 2025, 01:29:14 UTC, the SQL Managed Instance pearlsqlmi experienced intermittent unavailability and connectivity issues. Cause: This was caused by multiple failovers triggered by a rare race condition during the rotation of the encryption protector on databases that contain memory-optimized tables. Mitigation Once the root cause was identified, we implemented manual mitigation steps to restore stability. Monitoring and alerting systems remain active to detect any recurrence. This issue is highly unlikely to reoccur and is only triggered during encryption protector changes. Next steps Product team is currently validating a permanent fix, which will be included in an upcoming release. In the meantime, we recommend avoiding encryption protector changes during peak usage hours to minimize potential impact, since during that period you have a slightly higher chance of this particular race condition happening..</p> ]]> Thu, 5 Jun 2025 17:55:00 +0000 https://asgl.instatus.com/incident/cmc521t9a000ffc90fgm2lof3 https://asgl.instatus.com/incident/cmc521t9a000ffc90fgm2lof3