Landis Technologies Status - Incident history https://status.landis.cloud Landis Technologies Thu, 2 Apr 2026 10:14:10 +0000 Calls May not Appear in Live and Historical Reports. Type: Incident Duration: 58 minutes Affected Components: Portal Apr 2, 10:14:10 GMT+0 - Investigating - We are currently investigating this incident. Apr 2, 10:47:41 GMT+0 - Monitoring - Our engineering team has applied backend infrastructure changes, and the issue appears to be resolved. We are actively monitoring to confirm continued normal operation. Apr 2, 11:12:31 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 58 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>10:14:10</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>10:47:41</var> GMT+0</small><br><strong>Monitoring</strong> - Our engineering team has applied backend infrastructure changes, and the issue appears to be resolved. We are actively monitoring to confirm continued normal operation..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>11:12:31</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 2 Apr 2026 10:14:10 +0000 https://status.landis.cloud/incident/cmnhbi4o900013ubzlazgk6rs https://status.landis.cloud/incident/cmnhbi4o900013ubzlazgk6rs [Microsoft Issue] Intermittent Dropped Calls When Transferring from Microsoft Teams Auto Attendant to Landis Contact Center Type: Incident Duration: 4 days, 1 hour and 15 minutes Affected Components: Call Routing, Call Routing Mar 27, 20:03:37 GMT+0 - Resolved - Microsoft has completed the rollout of the fix, and we expect the issue to be resolved across all Microsoft 365 tenants. If you continue to experience any issues, please submit a ticket through <https://support.landis.cloud>. Mar 23, 18:48:22 GMT+0 - Identified - Some Microsoft 365 tenants may experience dropped calls when transferring from a Microsoft Teams auto attendant to Landis Contact Center queue or IVR. Microsoft has acknowledged this issue and is actively working on a bug fix. Microsoft has provided an ETA of Friday 3/27\. Microsoft ticket number 2603110040009217 ### **Workaround** Configure the Microsoft Teams Auto Attendant to transfer calls to the **PSTN number** of the Landis Contact Center resource account instead of transferring directly to the resource account. Mar 27, 15:42:55 GMT+0 - Monitoring - Microsoft has begun rolling out a fix, and the issue is already resolved for some Microsoft 365 tenants. We are monitoring the progress. Type: Incident

Duration: 4 days, 1 hour and 15 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>20:03:37</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft has completed the rollout of the fix, and we expect the issue to be resolved across all Microsoft 365 tenants. If you continue to experience any issues, please submit a ticket through <https://support.landis.cloud>..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>18:48:22</var> GMT+0</small><br><strong>Identified</strong> - Some Microsoft 365 tenants may experience dropped calls when transferring from a Microsoft Teams auto attendant to Landis Contact Center queue or IVR. Microsoft has acknowledged this issue and is actively working on a bug fix. Microsoft has provided an ETA of Friday 3/27\. Microsoft ticket number 2603110040009217 ### **Workaround** Configure the Microsoft Teams Auto Attendant to transfer calls to the **PSTN number** of the Landis Contact Center resource account instead of transferring directly to the resource account..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>15:42:55</var> GMT+0</small><br><strong>Monitoring</strong> - Microsoft has begun rolling out a fix, and the issue is already resolved for some Microsoft 365 tenants. We are monitoring the progress..</p> ]]> Mon, 23 Mar 2026 18:48:22 +0000 https://status.landis.cloud/incident/cmn3jgw1z00ilnhurnedtwnmb https://status.landis.cloud/incident/cmn3jgw1z00ilnhurnedtwnmb [Microsoft Issue] Intermittent Audio Prompt Playback Issues for Callers Type: Incident Duration: 10 hours and 44 minutes Affected Components: Call Routing, Call Routing Mar 5, 19:09:09 GMT+0 - Resolved - RCA: A recent validation change from Microsoft in how Graph handled inputs caused certain requests to be rejected. This has caused intermittent failures and Microsoft is in the process of rolling it back. Once this was identified, we released a fix to mitigate the intermittent failures and restore normal operation. Mar 4, 16:30:11 GMT+0 - Investigating - We are currently investigating this incident. Microsoft Graph is intermittently returning an error when attempting to play a prompt. Mar 4, 18:16:43 GMT+0 - Identified - We are actively working with Microsoft on this issue and are investigating possible workarounds. Mar 5, 01:40:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 5, 03:14:03 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 10 hours and 44 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>19:09:09</var> GMT+0</small><br><strong>Resolved</strong> - RCA: A recent validation change from Microsoft in how Graph handled inputs caused certain requests to be rejected. This has caused intermittent failures and Microsoft is in the process of rolling it back. Once this was identified, we released a fix to mitigate the intermittent failures and restore normal operation. .</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>16:30:11</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Microsoft Graph is intermittently returning an error when attempting to play a prompt..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>18:16:43</var> GMT+0</small><br><strong>Identified</strong> - We are actively working with Microsoft on this issue and are investigating possible workarounds..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>01:40:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>03:14:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 4 Mar 2026 16:30:11 +0000 https://status.landis.cloud/incident/cmmc95zr8022bxr57j2g1sza9 https://status.landis.cloud/incident/cmmc95zr8022bxr57j2g1sza9 Some Calls May Not Route as Expected or be Displayed in Live Reports Type: Incident Duration: 1 hour and 14 minutes Affected Components: Portal, Call Routing Mar 2, 15:36:00 GMT+0 - Investigating - We are currently investigating this incident. Mar 2, 16:50:00 GMT+0 - Resolved - Traffic was successfully rerouted to unaffected infrastructure to mitigate impact. Normal service has been fully restored, and the incident is now resolved. Type: Incident

Duration: 1 hour and 14 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>15:36:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>16:50:00</var> GMT+0</small><br><strong>Resolved</strong> - Traffic was successfully rerouted to unaffected infrastructure to mitigate impact. Normal service has been fully restored, and the incident is now resolved..</p> ]]> Mon, 2 Mar 2026 15:36:00 +0000 https://status.landis.cloud/incident/cmm9gm3i10brt48oq3x3eo0ud https://status.landis.cloud/incident/cmm9gm3i10brt48oq3x3eo0ud [Microsoft Service Issue] Some calls may not progress though IVRs and queues. Type: Incident Duration: 4 days, 4 hours and 38 minutes Affected Components: Call Routing, Call Routing Feb 13, 21:09:37 GMT+0 - Resolved - Our engineering team has completed a permanent update to address this issue. The service has been modified to fully accommodate the change in the Microsoft API behavior, and audio prompts and call flows are now functioning as expected. We will continue to monitor, but this incident is considered resolved. Feb 11, 21:43:47 GMT+0 - Identified - The Microsoft product group is still actively investigating the issue. While we are waiting on them to address the root cause, we have implemented another code change that enables calls to progress through an IVR after an audio prompt is played. Organizations should see improvements over the next few hours. Feb 10, 20:54:18 GMT+0 - Identified - The Microsoft product group is aware and is still actively investigating the issue. Feb 12, 16:42:43 GMT+0 - Identified - The Microsoft product group is still actively investigating the issue. Feb 9, 16:32:00 GMT+0 - Identified - We are currently experiencing an intermittent issue with the Microsoft calling APIs in which audio prompts are not completing as expected. Microsoft is not sending audio prompt completion notifications, preventing call flows from progressing after a prompt is played. As a result, callers may remain at audio prompts indefinitely, including initial welcome messages within call queues. This may impact call routing. We have reported this issue to Microsoft. Feb 11, 16:50:16 GMT+0 - Identified - The Microsoft product group is still actively investigating the issue. As a temporary partial mitigation, we have implemented a minor code adjustment that enables calls to progress beyond a queue’s welcome message. This will help alleviate the situation in which no agents are alerted to an incoming call in the queue. Feb 12, 19:47:58 GMT+0 - Identified - The Microsoft product group is still actively investigating the issue. While we are continuing to wait on them to address the root cause, we have implemented another code change. This change will ensure prompts continue playing for callers waiting in queue. Organizations should see improvements over the next few hours. Based on these recent code changes, we anticipate that the agent and caller experience will largely be unaffected by the underlying Microsoft API issue. Type: Incident

Duration: 4 days, 4 hours and 38 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:09:37</var> GMT+0</small><br><strong>Resolved</strong> - Our engineering team has completed a permanent update to address this issue. The service has been modified to fully accommodate the change in the Microsoft API behavior, and audio prompts and call flows are now functioning as expected. We will continue to monitor, but this incident is considered resolved..</p> <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>21:43:47</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft product group is still actively investigating the issue. While we are waiting on them to address the root cause, we have implemented another code change that enables calls to progress through an IVR after an audio prompt is played. Organizations should see improvements over the next few hours..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>20:54:18</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft product group is aware and is still actively investigating the issue..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>16:42:43</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft product group is still actively investigating the issue..</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>16:32:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently experiencing an intermittent issue with the Microsoft calling APIs in which audio prompts are not completing as expected. Microsoft is not sending audio prompt completion notifications, preventing call flows from progressing after a prompt is played. As a result, callers may remain at audio prompts indefinitely, including initial welcome messages within call queues. This may impact call routing. We have reported this issue to Microsoft..</p> <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>16:50:16</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft product group is still actively investigating the issue. As a temporary partial mitigation, we have implemented a minor code adjustment that enables calls to progress beyond a queue’s welcome message. This will help alleviate the situation in which no agents are alerted to an incoming call in the queue..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>19:47:58</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft product group is still actively investigating the issue. While we are continuing to wait on them to address the root cause, we have implemented another code change. This change will ensure prompts continue playing for callers waiting in queue. Organizations should see improvements over the next few hours. Based on these recent code changes, we anticipate that the agent and caller experience will largely be unaffected by the underlying Microsoft API issue..</p> ]]> Mon, 9 Feb 2026 16:32:00 +0000 https://status.landis.cloud/incident/cmlgmnkw918e05p7vq32y9w87 https://status.landis.cloud/incident/cmlgmnkw918e05p7vq32y9w87 Landis Contact Center Teams App No Longer Accessible in Teams Type: Incident Duration: 1 day, 21 hours and 43 minutes Affected Components: Portal, , , , Portal, EMEA Datacenter → North America Datacenter → Landis Contact Center → Feb 3, 15:17:05 GMT+0 - Investigating - We are currently investigating this incident. If you are affected, please use the browser to access Landis Contact Center: [Agent Panel | Landis Contact Center for Microsoft Teams](https://cc.landis.cloud/client/agentpanel) [Dashboard | Landis Contact Center for Microsoft Teams](https://cc.landis.cloud/app/main/dashboard) Feb 3, 17:23:57 GMT+0 - Identified - We are working with Microsoft to restore the app in the Teams app Store. Feb 4, 17:39:06 GMT+0 - Monitoring - Microsoft has republished the app. We would expect it to become available in Teams in the next few hours. Feb 5, 12:59:50 GMT+0 - Resolved - This incident has been resolved. Feb 4, 21:28:08 GMT+0 - Monitoring - The app is now available in Teams for most users. Users may need to pin the app again in Teams. We are continuing to monitor. Type: Incident

Duration: 1 day, 21 hours and 43 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>15:17:05</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. If you are affected, please use the browser to access Landis Contact Center: [Agent Panel | Landis Contact Center for Microsoft Teams](https://cc.landis.cloud/client/agentpanel) [Dashboard | Landis Contact Center for Microsoft Teams](https://cc.landis.cloud/app/main/dashboard).</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:23:57</var> GMT+0</small><br><strong>Identified</strong> - We are working with Microsoft to restore the app in the Teams app Store..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>17:39:06</var> GMT+0</small><br><strong>Monitoring</strong> - Microsoft has republished the app. We would expect it to become available in Teams in the next few hours..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>12:59:50</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>21:28:08</var> GMT+0</small><br><strong>Monitoring</strong> - The app is now available in Teams for most users. Users may need to pin the app again in Teams. We are continuing to monitor..</p> ]]> Tue, 3 Feb 2026 15:17:05 +0000 https://status.landis.cloud/incident/cml6qs9wo09yi86dhbdhlvpwr https://status.landis.cloud/incident/cml6qs9wo09yi86dhbdhlvpwr Internal Error May Appear in the Portal for Some Organizations Type: Incident Duration: 1 hour and 38 minutes Affected Components: Portal Dec 16, 17:54:54 GMT+0 - Monitoring - Portal traffic has been moved to the new infrastructure and we are monitoring. Dec 16, 18:09:29 GMT+0 - Resolved - This incident has been resolved. RCA: During an update, newly deployed portal instances wrote cache entries that were incompatible with the older instances. The incident persisted until all traffic was directed to the updated portal instances at which point compatibility issues were resolved. Dec 16, 16:31:51 GMT+0 - Investigating - We are currently investigating this incident. Dec 16, 17:36:17 GMT+0 - Identified - We are continuing to work on a fix for this incident. We are currently moving portal traffic to new infrastructure to mitigate the issue. Type: Incident

Duration: 1 hour and 38 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>17:54:54</var> GMT+0</small><br><strong>Monitoring</strong> - Portal traffic has been moved to the new infrastructure and we are monitoring..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>18:09:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. RCA: During an update, newly deployed portal instances wrote cache entries that were incompatible with the older instances. The incident persisted until all traffic was directed to the updated portal instances at which point compatibility issues were resolved..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>16:31:51</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>17:36:17</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. We are currently moving portal traffic to new infrastructure to mitigate the issue. .</p> ]]> Tue, 16 Dec 2025 16:31:51 +0000 https://status.landis.cloud/incident/cmj8svp2500hbqxwq27znkm83 https://status.landis.cloud/incident/cmj8svp2500hbqxwq27znkm83 [Microsoft Service Issue] Attendant Console Application Outage Type: Incident Duration: 9 hours and 13 minutes Affected Components: Landis Attendant Console Oct 29, 16:10:09 GMT+0 - Investigating - We are currently investigating this incident. Oct 29, 16:15:08 GMT+0 - Identified - Microsoft Azure Front Door is experiencing a degradation that is affecting the application. Microsoft is working to resolve the issue. Oct 29, 20:36:51 GMT+0 - Monitoring - We are monitoring and access is intermittent and seems to be improving. Update from Microsoft: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. Oct 30, 01:23:06 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 9 hours and 13 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:10:09</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:15:08</var> GMT+0</small><br><strong>Identified</strong> - Microsoft Azure Front Door is experiencing a degradation that is affecting the application. Microsoft is working to resolve the issue..</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>20:36:51</var> GMT+0</small><br><strong>Monitoring</strong> - We are monitoring and access is intermittent and seems to be improving. Update from Microsoft: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>01:23:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 Oct 2025 16:10:09 +0000 https://status.landis.cloud/incident/cmhc6ywpm00956ynwufkmvgxk https://status.landis.cloud/incident/cmhc6ywpm00956ynwufkmvgxk [Microsoft Service Issue] Contact Center Portal Service Outage Type: Incident Duration: 9 hours and 29 minutes Affected Components: Portal, Portal Oct 29, 15:54:57 GMT+0 - Investigating - We are currently investigating this incident. Oct 29, 16:13:23 GMT+0 - Identified - Microsoft Azure Front Door is experiencing a degradation that is affecting the portal. Microsoft is working to resolve the issue. Oct 29, 20:37:42 GMT+0 - Monitoring - We are monitoring and access is intermittent and seems to be improving. Update from Microsoft: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. Oct 30, 01:23:32 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 9 hours and 29 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>15:54:57</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:13:23</var> GMT+0</small><br><strong>Identified</strong> - Microsoft Azure Front Door is experiencing a degradation that is affecting the portal. Microsoft is working to resolve the issue..</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>20:37:42</var> GMT+0</small><br><strong>Monitoring</strong> - We are monitoring and access is intermittent and seems to be improving. Update from Microsoft: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>01:23:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 Oct 2025 15:54:57 +0000 https://status.landis.cloud/incident/cmhc6fc7o003jqlutiywtcq3z https://status.landis.cloud/incident/cmhc6fc7o003jqlutiywtcq3z An error may appear when playing recordings in the portal Type: Incident Duration: 1 day, 6 hours and 37 minutes Affected Components: Recording, Landis Attendant Console Oct 21, 13:37:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 21, 20:08:00 GMT+0 - Identified - Issue has been identified and resolved for all new recordings. Recordings during the incident period will become available over the next few days. Oct 21, 20:36:29 GMT+0 - Monitoring - We are currently working on uploading your recordings. They will become available over the next few days. Oct 22, 20:14:00 GMT+0 - Resolved - This incident has been resolved. RCA: An invalid configuration in a customer's organization caused recording upload failures which delayed the upload of other organizations recordings. Type: Incident

Duration: 1 day, 6 hours and 37 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>13:37:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>20:08:00</var> GMT+0</small><br><strong>Identified</strong> - Issue has been identified and resolved for all new recordings. Recordings during the incident period will become available over the next few days..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>20:36:29</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently working on uploading your recordings. They will become available over the next few days..</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>20:14:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. RCA: An invalid configuration in a customer's organization caused recording upload failures which delayed the upload of other organizations recordings..</p> ]]> Tue, 21 Oct 2025 13:37:00 +0000 https://status.landis.cloud/incident/cmh0yn1gu00zenrzpfvcwkvja https://status.landis.cloud/incident/cmh0yn1gu00zenrzpfvcwkvja [Microsoft Service Issue] Teams Call Alert Displays Invitation to Join a Meeting Type: Incident Duration: 2 days Affected Components: Call Routing, , Call Routing, , , EMEA Datacenter → North America Datacenter → Landis Contact Center → Sep 15, 15:16:19 GMT+0 - Identified - Microsoft has released an update which in some scenarios will display an invite to join a meeting when there is an incoming call from a Landis queue. When this toast is displayed, it is not possible to join the call. This is also affecting Teams native queue alerts as well. If your organization is affected, please reach out to Microsoft Support. Sep 17, 15:16:00 GMT+0 - Resolved - Microsoft has resolved this issue. Type: Incident

Duration: 2 days

Affected Components: , , , ,

<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>15:16:19</var> GMT+0</small><br><strong>Identified</strong> - Microsoft has released an update which in some scenarios will display an invite to join a meeting when there is an incoming call from a Landis queue. When this toast is displayed, it is not possible to join the call. This is also affecting Teams native queue alerts as well. If your organization is affected, please reach out to Microsoft Support..</p> <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>15:16:00</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft has resolved this issue..</p> ]]> Mon, 15 Sep 2025 15:16:19 +0000 https://status.landis.cloud/incident/cmfl9o6ed005a10qz7chykvn5 https://status.landis.cloud/incident/cmfl9o6ed005a10qz7chykvn5 Intermittent Portal Service Outage Type: Incident Duration: 2 hours and 57 minutes Affected Components: Portal, Portal Sep 2, 20:07:52 GMT+0 - Resolved - This incident has been resolved. RCA: The portal service experienced performance degradation and partial outages due to an unanticipated spike in traffic. We have scaled out the service to increase capacity. Sep 2, 17:11:00 GMT+0 - Investigating - Portal may be intermittently unavailable. Sep 2, 18:02:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 2 hours and 57 minutes

Affected Components: ,

<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>20:07:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. RCA: The portal service experienced performance degradation and partial outages due to an unanticipated spike in traffic. We have scaled out the service to increase capacity..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>17:11:00</var> GMT+0</small><br><strong>Investigating</strong> - Portal may be intermittently unavailable..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>18:02:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Tue, 2 Sep 2025 17:11:00 +0000 https://status.landis.cloud/incident/cmf2t9o6i00aqpp27wdwmqcph https://status.landis.cloud/incident/cmf2t9o6i00aqpp27wdwmqcph Teams Presence May Fail to Update For Some Customers Type: Incident Duration: 2 hours and 50 minutes Affected Components: Portal May 6, 16:30:00 GMT+0 - Investigating - We are currently investigating this incident. May 6, 19:20:00 GMT+0 - Resolved - For Contact Center organizations hosted in North America, the IP ranges for the Teams API service account have changed. If your organization is affected, please update the IP whitelist for the Presence API service account. [Presence API Service Account | Landis Contact Center for Microsoft Teams](https://cc.docs.landis.cloud/appendix/presence-api-service-account) Type: Incident

Duration: 2 hours and 50 minutes

Affected Components:

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>19:20:00</var> GMT+0</small><br><strong>Resolved</strong> - For Contact Center organizations hosted in North America, the IP ranges for the Teams API service account have changed. If your organization is affected, please update the IP whitelist for the Presence API service account. [Presence API Service Account | Landis Contact Center for Microsoft Teams](https://cc.docs.landis.cloud/appendix/presence-api-service-account).</p> ]]> Tue, 6 May 2025 16:30:00 +0000 https://status.landis.cloud/incident/cmae1tzxn006our2r4jf60f2q https://status.landis.cloud/incident/cmae1tzxn006our2r4jf60f2q [Microsoft Service Issue] Microsoft Teams-provisioned auto attendants and call queues not functioning properly Type: Incident Duration: 3 hours and 19 minutes Affected Components: Landis Attendant Console, Recording, Recording, Call Routing, Portal, Call Routing, Portal, Chat Routing Mar 3, 16:46:00 GMT+0 - Monitoring - Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. [Microsoft 365 Status on X: "We're investigating an issue impacting Microsoft Teams-provisioned auto attendants and call queues. For more information, please see TM1022107 in the admin center." / X](https://x.com/MSFT365Status/status/1896613470180680179) * _Landis Contact Center queues and IVRs continue to function normally. Calls that are first routed through a Teams auto attendant or Teams call queue before being transferred to Landis Contact Center may be affected._ * _If your organization is affected, we recommend using Landis Contact Center queues and IVRs_ Mar 3, 20:05:00 GMT+0 - Resolved - Microsoft identified a recent change that inadvertently caused impact to auto attendant and call queues. They have deployed a fix to restore service. Additional information can be found in the admin center under TM1022107. Type: Incident

Duration: 3 hours and 19 minutes

Affected Components: , , , , , , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:46:00</var> GMT+0</small><br><strong>Monitoring</strong> - Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues. [Microsoft 365 Status on X: "We're investigating an issue impacting Microsoft Teams-provisioned auto attendants and call queues. For more information, please see TM1022107 in the admin center." / X](https://x.com/MSFT365Status/status/1896613470180680179) * _Landis Contact Center queues and IVRs continue to function normally. Calls that are first routed through a Teams auto attendant or Teams call queue before being transferred to Landis Contact Center may be affected._ * _If your organization is affected, we recommend using Landis Contact Center queues and IVRs_.</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>20:05:00</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft identified a recent change that inadvertently caused impact to auto attendant and call queues. They have deployed a fix to restore service. Additional information can be found in the admin center under TM1022107..</p> ]]> Mon, 3 Mar 2025 16:46:00 +0000 https://status.landis.cloud/incident/cm7te7gii006vv93smgxdbi1g https://status.landis.cloud/incident/cm7te7gii006vv93smgxdbi1g Realtime Queue Data in Reports Maybe Delayed Type: Incident Duration: 1 hour and 45 minutes Affected Components: Portal Feb 4, 16:32:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 4, 18:17:22 GMT+0 - Resolved - This incident has been resolved. Feb 4, 18:05:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 1 hour and 45 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:32:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>18:17:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>18:05:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Tue, 4 Feb 2025 16:32:00 +0000 https://status.landis.cloud/incident/cm6qrox8l002fzns6i3ydrlcb https://status.landis.cloud/incident/cm6qrox8l002fzns6i3ydrlcb [Microsoft Service Issue] Web chat messages may not appear in the widget. Type: Incident Duration: 3 hours and 26 minutes Affected Components: Chat Routing Jan 21, 15:38:00 GMT+0 - Investigating - We are currently investigating this incident. Jan 21, 16:00:00 GMT+0 - Identified - The Microsoft APIs are not relaying chat messages. Our Engineers are working with Microsoft to find a resolution. Jan 21, 19:04:00 GMT+0 - Resolved - Microsoft fixed the underlying issue. This incident has been resolved. Type: Incident

Duration: 3 hours and 26 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>15:38:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft APIs are not relaying chat messages. Our Engineers are working with Microsoft to find a resolution..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>19:04:00</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft fixed the underlying issue. This incident has been resolved..</p> ]]> Tue, 21 Jan 2025 15:38:00 +0000 https://status.landis.cloud/incident/cm66tj5x8008wagrzc4r3a2gz https://status.landis.cloud/incident/cm66tj5x8008wagrzc4r3a2gz A maintenance window is scheduled for Tuesday 11/5/2024 at 10pm EST for 1 hour. Type: Maintenance Duration: 1 hour and 30 minutes Affected Components: Recording, Recording, , Call Routing, Portal, Call Routing, , Portal, EMEA Datacenter → North America Datacenter → Nov 6, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 6, 04:01:18 GMT+0 - Identified - The maintenance is taking longer than expected. New estimated completion time is 11:30pm EST. Thank you for your patience. Nov 6, 04:30:00 GMT+0 - Completed - Maintenance has completed successfully Nov 6, 03:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 1 hour and 30 minutes

Affected Components: , , , , , , ,

<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>04:01:18</var> GMT+0</small><br><strong>Identified</strong> - The maintenance is taking longer than expected. New estimated completion time is 11:30pm EST. Thank you for your patience..</p> <p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> ]]> Wed, 6 Nov 2024 03:00:00 +0000 https://status.landis.cloud/maintenance/cm34jxbqh0005bkqrv8jsda7s https://status.landis.cloud/maintenance/cm34jxbqh0005bkqrv8jsda7s [Microsoft Service Issue] Calls may fail to connect to Landis Queues and/or IVRs Type: Incident Duration: 1 hour and 46 minutes Affected Components: Call Routing, Call Routing Oct 10, 16:53:00 GMT+0 - Investigating - Microsoft: We're investigating a potential issue with users' Auto Attendant and Call Queue calls failing within Microsoft Teams. Oct 10, 17:36:00 GMT+0 - Identified - Microsoft: We've identified an issue in which traffic for Auto attendant and Call queue calls is being routed to an unhealthy portion of service infrastructure, resulting in impact. We're re-routing traffic to a healthy portion of service infrastructure Oct 10, 18:38:39 GMT+0 - Resolved - Microsoft: We've routed the affected call requests to a healthy portion of service infrastructure and confirmed through monitoring service telemetry that impact has been remediated. Type: Incident

Duration: 1 hour and 46 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>16:53:00</var> GMT+0</small><br><strong>Investigating</strong> - Microsoft: We're investigating a potential issue with users' Auto Attendant and Call Queue calls failing within Microsoft Teams..</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>17:36:00</var> GMT+0</small><br><strong>Identified</strong> - Microsoft: We've identified an issue in which traffic for Auto attendant and Call queue calls is being routed to an unhealthy portion of service infrastructure, resulting in impact. We're re-routing traffic to a healthy portion of service infrastructure.</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>18:38:39</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft: We've routed the affected call requests to a healthy portion of service infrastructure and confirmed through monitoring service telemetry that impact has been remediated..</p> ]]> Thu, 10 Oct 2024 16:53:00 +0000 https://status.landis.cloud/incident/cm23ksxe6002lo9ujcb0uyq2z https://status.landis.cloud/incident/cm23ksxe6002lo9ujcb0uyq2z [Microsoft Service Issue] Portal Service Outage Type: Incident Duration: 39 minutes Affected Components: Portal, Portal Aug 21, 07:36:23 GMT+0 - Resolved - Our engineers have been monitoring and have confirmed this incident to be resolved. Aug 21, 06:42:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 21, 06:37:00 GMT+0 - Identified - Our engineers have identified the issue and are working on a resolution. Aug 21, 07:07:00 GMT+0 - Monitoring - Our engineers have resolved the issue, and we are monitoring. Type: Incident

Duration: 39 minutes

Affected Components: ,

<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>07:36:23</var> GMT+0</small><br><strong>Resolved</strong> - Our engineers have been monitoring and have confirmed this incident to be resolved..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>06:42:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>06:37:00</var> GMT+0</small><br><strong>Identified</strong> - Our engineers have identified the issue and are working on a resolution..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>07:07:00</var> GMT+0</small><br><strong>Monitoring</strong> - Our engineers have resolved the issue, and we are monitoring..</p> ]]> Wed, 21 Aug 2024 06:37:00 +0000 https://status.landis.cloud/incident/cm03i3vx1000dkpe4viitdfet https://status.landis.cloud/incident/cm03i3vx1000dkpe4viitdfet [Microsoft Service Issue] Teams user presence may appear incorrect in Landis Contact Center. Type: Incident Duration: 8 days, 17 hours and 38 minutes Affected Components: Recording, Recording, , Call Routing, Portal, Call Routing, , Portal, EMEA Datacenter → North America Datacenter → Aug 11, 02:00:00 GMT+0 - Investigating - User Impact: Teams Presence may not be updating correctly resulting in calls not routing to users. We are currently investigating this incident. If your organization is using Presence based routing for queues, we recommend turning it off until the issue is resolved. Aug 12, 13:18:32 GMT+0 - Identified - The Microsoft Presence API is not sending valid presence data to Landis Contact Center. We have reported this to Microsoft and are working with them on a resolution. Aug 12, 18:40:43 GMT+0 - Identified - Microsoft has acknowledged the issue of Presence Subscriptions not working properly and their engineers are currently working on a fix. Once more, we recommend that any organization using Teams Presence Based Routing turn that feature off until Microsoft fixes the issue. Aug 15, 01:21:00 GMT+0 - Monitoring - UPDATE FROM MICROSOFT: Issue ID: TM859169 Affected services: Microsoft Teams Status: Service degradation Issue type: Advisory Start time: Aug 12, 2024, 8:37 AM EDT User impact Users' Microsoft Teams presence information is displayed incorrectly in a specific third-party application. More info Impact is specific to some users who are creating a Graph API change notification subscription for presence using the third-party application. Scope of impact Your organization is affected by this event, and some users' utilizing a third-party presence-related application are impacted. Root cause A code issue in a recently deployed update to introduce a new feature intended to support regional notifications is resulting in impact. Current status Our operation to deploy the previously mentioned fix is complete, and we've monitored our service health telemetry to confirm that impact is remediated. History of updates Aug 13, 2024, 2:13 PM EDT We've validated the code fix and have started deploying it to the impacted environments. We anticipate the deployment will complete and the impact will be remediated by our next scheduled update. Aug 12, 2024, 2:28 PM EDT We've identified a code issue in a recently deployed update to introduce a new feature intended to support regional notifications, which is resulting in impact. We've developed and are validating a code fix, which we anticipate may be ready for deployment by our next schedule update. Once the deployment begins, we'll aim to provide a resolution timeline. Aug 12, 2024, 10:58 AM EDT We're reviewing recent service updates that may be contributing to impact, alongside affected user Webhook logs. Once we've confirmed the root cause, we'll review available mitigation options to develop an effective remediation plan Aug 12, 2024, 9:03 AM EDT We're reviewing support provided information to determine our next troubleshooting steps. Aug 19, 14:25:27 GMT+0 - Monitoring - Microsoft has updated the incident and marked the issue as resolved. We are currently monitoring. Aug 19, 19:37:57 GMT+0 - Resolved - We have confirmed Microsoft has resolved the issue. Type: Incident

Duration: 8 days, 17 hours and 38 minutes

Affected Components: , , , , , , ,

<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Investigating</strong> - User Impact: Teams Presence may not be updating correctly resulting in calls not routing to users. We are currently investigating this incident. If your organization is using Presence based routing for queues, we recommend turning it off until the issue is resolved..</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>13:18:32</var> GMT+0</small><br><strong>Identified</strong> - The Microsoft Presence API is not sending valid presence data to Landis Contact Center. We have reported this to Microsoft and are working with them on a resolution..</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>18:40:43</var> GMT+0</small><br><strong>Identified</strong> - Microsoft has acknowledged the issue of Presence Subscriptions not working properly and their engineers are currently working on a fix. Once more, we recommend that any organization using Teams Presence Based Routing turn that feature off until Microsoft fixes the issue..</p> <p><small>Aug <var data-var='date'> 15</var>, <var data-var='time'>01:21:00</var> GMT+0</small><br><strong>Monitoring</strong> - UPDATE FROM MICROSOFT: Issue ID: TM859169 Affected services: Microsoft Teams Status: Service degradation Issue type: Advisory Start time: Aug 12, 2024, 8:37 AM EDT User impact Users' Microsoft Teams presence information is displayed incorrectly in a specific third-party application. More info Impact is specific to some users who are creating a Graph API change notification subscription for presence using the third-party application. Scope of impact Your organization is affected by this event, and some users' utilizing a third-party presence-related application are impacted. Root cause A code issue in a recently deployed update to introduce a new feature intended to support regional notifications is resulting in impact. Current status Our operation to deploy the previously mentioned fix is complete, and we've monitored our service health telemetry to confirm that impact is remediated. History of updates Aug 13, 2024, 2:13 PM EDT We've validated the code fix and have started deploying it to the impacted environments. We anticipate the deployment will complete and the impact will be remediated by our next scheduled update. Aug 12, 2024, 2:28 PM EDT We've identified a code issue in a recently deployed update to introduce a new feature intended to support regional notifications, which is resulting in impact. We've developed and are validating a code fix, which we anticipate may be ready for deployment by our next schedule update. Once the deployment begins, we'll aim to provide a resolution timeline. Aug 12, 2024, 10:58 AM EDT We're reviewing recent service updates that may be contributing to impact, alongside affected user Webhook logs. Once we've confirmed the root cause, we'll review available mitigation options to develop an effective remediation plan Aug 12, 2024, 9:03 AM EDT We're reviewing support provided information to determine our next troubleshooting steps..</p> <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>14:25:27</var> GMT+0</small><br><strong>Monitoring</strong> - Microsoft has updated the incident and marked the issue as resolved. We are currently monitoring..</p> <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>19:37:57</var> GMT+0</small><br><strong>Resolved</strong> - We have confirmed Microsoft has resolved the issue..</p> ]]> Sun, 11 Aug 2024 02:00:00 +0000 https://status.landis.cloud/incident/clzqz9q1c663984ifoh8tz8dh10 https://status.landis.cloud/incident/clzqz9q1c663984ifoh8tz8dh10 [Microsoft Service Issue] Intermittent Portal Service Outage Type: Incident Duration: 22 days and 11 hours Affected Components: Portal, Portal Jul 30, 11:57:00 GMT+0 - Investigating - We are currently investigating this incident. It appears that Azure is having intermittent connectivity issues for some customers. Jul 30, 20:56:00 GMT+0 - Resolved - Microsoft has implemented networking configuration changes and have performed failovers to alternate networking paths to provide relief. Their monitoring telemetry shows improvement in service availability, and they are continuing to monitor to ensure full recovery. Type: Incident

Duration: 22 days and 11 hours

Affected Components: ,

<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>11:57:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. It appears that Azure is having intermittent connectivity issues for some customers..</p> <p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>20:56:00</var> GMT+0</small><br><strong>Resolved</strong> - Microsoft has implemented networking configuration changes and have performed failovers to alternate networking paths to provide relief. Their monitoring telemetry shows improvement in service availability, and they are continuing to monitor to ensure full recovery..</p> ]]> Tue, 30 Jul 2024 11:57:00 +0000 https://status.landis.cloud/incident/clz8f4gw911027hno531jvmy04 https://status.landis.cloud/incident/clz8f4gw911027hno531jvmy04 A maintenance window is scheduled for Tuesday 7/2/2024 at 10pm EST for 1 hour. Type: Maintenance Duration: 1 hour Affected Components: Recording, Recording, , Call Routing, Portal, Call Routing, , Portal, EMEA Datacenter → North America Datacenter → Jul 3, 02:00:00 GMT+0 - Identified - Typically, during this maintenance window there is minimal downtime. If this occurs during working hours and downtime is a concern, we recommend temporarily failing over to Teams queues and/or auto attendants over this time period. We apologize for any inconvenience. Jul 3, 02:00:00 GMT+0 - Identified - Maintenance is now in progress. Jul 3, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully. For more details see: <https://cc.docs.landis.cloud/releases#july-2-2024> Type: Maintenance

Duration: 1 hour

Affected Components: , , , , , , ,

<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - Typically, during this maintenance window there is minimal downtime. If this occurs during working hours and downtime is a concern, we recommend temporarily failing over to Teams queues and/or auto attendants over this time period. We apologize for any inconvenience..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully. For more details see: <https://cc.docs.landis.cloud/releases#july-2-2024>.</p> ]]> Wed, 3 Jul 2024 02:00:00 +0000 https://status.landis.cloud/maintenance/clxvsk40s0224bjn39xlpfq0d https://status.landis.cloud/maintenance/clxvsk40s0224bjn39xlpfq0d [Microsoft Service Issue] Queue Call Routing Type: Incident Duration: 35 minutes Affected Components: Call Routing Jun 25, 14:15:00 GMT+0 - Investigating - User Impact: Queue calls may not be routed to agents. Scope of impact: Customers may be experiencing call routing issues. We are currently investigating this incident. Jun 25, 14:22:00 GMT+0 - Identified - An Azure service is experiencing a degradation. Jun 25, 14:44:00 GMT+0 - Monitoring - The Azure service degradation appears to have been resolved. We are monitoring. Jun 25, 14:50:00 GMT+0 - Resolved - We have confirmed Microsoft has resolved the issue. Type: Incident

Duration: 35 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br><strong>Investigating</strong> - User Impact: Queue calls may not be routed to agents. Scope of impact: Customers may be experiencing call routing issues. We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:22:00</var> GMT+0</small><br><strong>Identified</strong> - An Azure service is experiencing a degradation..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:44:00</var> GMT+0</small><br><strong>Monitoring</strong> - The Azure service degradation appears to have been resolved. We are monitoring..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:50:00</var> GMT+0</small><br><strong>Resolved</strong> - We have confirmed Microsoft has resolved the issue..</p> ]]> Tue, 25 Jun 2024 14:15:00 +0000 https://status.landis.cloud/incident/clxui1go248381booojkkt2mt7 https://status.landis.cloud/incident/clxui1go248381booojkkt2mt7 [Microsoft Service Issue] Teams User Presence Errors in Landis Contact Center Type: Incident Duration: 3 days, 7 hours and 29 minutes Affected Components: Call Routing, Portal Jun 16, 07:00:00 GMT+0 - Investigating - Some customers may see Teams user presence errors. User Impact: Teams user presence may not appear Landis contact center. If Teams presence based routing is enabled on queues, calls may not route to available agents. If you are affected, we recommend temporarily disabling Teams presence based routing your queues. Jun 17, 15:27:00 GMT+0 - Identified - Microsoft Azure service is using an incorrect IP address to query Teams user presence. Customers that have a conditional access policy with IP restrictions configured for the presence API service account will be affected. We are working with Microsoft to resolve this issue. Jun 18, 18:00:49 GMT+0 - Identified - We are continuing to work with Microsoft on this incident. Jun 18, 22:50:00 GMT+0 - Monitoring - Microsoft has applied a mitigation, and we are currently monitoring the result. Jun 18, 23:00:00 GMT+0 - Resolved - We have confirmed Microsoft has resolved the issue. Type: Incident

Duration: 3 days, 7 hours and 29 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Some customers may see Teams user presence errors. User Impact: Teams user presence may not appear Landis contact center. If Teams presence based routing is enabled on queues, calls may not route to available agents. If you are affected, we recommend temporarily disabling Teams presence based routing your queues..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>15:27:00</var> GMT+0</small><br><strong>Identified</strong> - Microsoft Azure service is using an incorrect IP address to query Teams user presence. Customers that have a conditional access policy with IP restrictions configured for the presence API service account will be affected. We are working with Microsoft to resolve this issue..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>18:00:49</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work with Microsoft on this incident..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>22:50:00</var> GMT+0</small><br><strong>Monitoring</strong> - Microsoft has applied a mitigation, and we are currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Resolved</strong> - We have confirmed Microsoft has resolved the issue..</p> ]]> Sun, 16 Jun 2024 07:00:00 +0000 https://status.landis.cloud/incident/clxj3aj2g71575bkoifd3wv2y4 https://status.landis.cloud/incident/clxj3aj2g71575bkoifd3wv2y4 Teams user presence may intermittently appear incorrect in Landis contact center. Type: Incident Duration: 1 day and 40 minutes Affected Components: Recording, Recording, , Call Routing, Portal, Call Routing, , Portal, EMEA Datacenter → North America Datacenter → Jun 5, 15:50:00 GMT+0 - Resolved - This incident has been resolved. Jun 5, 13:10:00 GMT+0 - Identified - In some cases a backend process is not able to correctly update the Teams presence for some organizations. Our engineers are working to resolve the issue. Jun 4, 15:10:00 GMT+0 - Investigating - User Impact: Teams user presence may intermittently appear incorrect in Landis contact center. If Teams presence based routing is enabled on queues, call may not route to available agents. If you are affected, we recommend temporarily disabling Teams presence based routing your queues. Jun 5, 13:33:00 GMT+0 - Monitoring - A fix has been pushed and we are monitoring. Organization that are affected should see the issue resolved over the next few hours. Type: Incident

Duration: 1 day and 40 minutes

Affected Components: , , , , , , ,

<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>15:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>13:10:00</var> GMT+0</small><br><strong>Identified</strong> - In some cases a backend process is not able to correctly update the Teams presence for some organizations. Our engineers are working to resolve the issue..</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>15:10:00</var> GMT+0</small><br><strong>Investigating</strong> - User Impact: Teams user presence may intermittently appear incorrect in Landis contact center. If Teams presence based routing is enabled on queues, call may not route to available agents. If you are affected, we recommend temporarily disabling Teams presence based routing your queues..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>13:33:00</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been pushed and we are monitoring. Organization that are affected should see the issue resolved over the next few hours..</p> ]]> Tue, 4 Jun 2024 15:10:00 +0000 https://status.landis.cloud/incident/clx1ylabo139783bgmyg3l3njmu https://status.landis.cloud/incident/clx1ylabo139783bgmyg3l3njmu [Microsoft Service Issue] Teams user presence may appear incorrect in Landis contact center. Type: Incident Duration: 11 hours and 39 minutes Affected Components: Call Routing, Portal, Call Routing, Portal Apr 16, 22:11:00 GMT+0 - Identified - User Impact: Teams user presence may appear incorrect in Landis contact center. If Teams presence based routing is enabled on queues, call may not route to available agents. Apr 17, 09:50:00 GMT+0 - Resolved - It appears that the Microsoft presence API is delayed or is not sending presence updates to Landis Contact Center. 4/17/2024 1:11AM EDT We have confirmed the Microsoft Presence API is not sending valid presence data to Landis Contact Center. We have reported this to Microsoft and are working with them on a resolution. Microsoft has resolved the issue. Microsoft's RCA: A recent scheduled service update contained a change intended to optimize presence-related data flow, which was unexpectedly causing impact. Type: Incident

Duration: 11 hours and 39 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>22:11:00</var> GMT+0</small><br><strong>Identified</strong> - User Impact: Teams user presence may appear incorrect in Landis contact center. If Teams presence based routing is enabled on queues, call may not route to available agents..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:50:00</var> GMT+0</small><br><strong>Resolved</strong> - It appears that the Microsoft presence API is delayed or is not sending presence updates to Landis Contact Center. 4/17/2024 1:11AM EDT We have confirmed the Microsoft Presence API is not sending valid presence data to Landis Contact Center. We have reported this to Microsoft and are working with them on a resolution. Microsoft has resolved the issue. Microsoft's RCA: A recent scheduled service update contained a change intended to optimize presence-related data flow, which was unexpectedly causing impact..</p> ]]> Tue, 16 Apr 2024 22:11:00 +0000 https://status.landis.cloud/incident/clw6g9ff512778bemxfdgdt7rr https://status.landis.cloud/incident/clw6g9ff512778bemxfdgdt7rr [Microsoft Service Issue] Service Outage Type: Incident Duration: 4 days and 19 hours Affected Components: Recording, Portal, Call Routing, Portal Apr 3, 11:50:00 GMT+0 - Investigating - User Impact: Service may be unavailable. Scope of Impact: Users trying to access the portal may see issues loading the page. Also call routing and recording may be affected. We are continuing to investigate the issue. Apr 3, 13:45:00 GMT+0 - Resolved - 4/3/2024 9:29 PM EST: Azure SQL service is experiencing an outage that is affecting the service. 4/3/2024 9:45 PM EST: Azure SQL service outage appears to have resolved. We are continuing to monitor. RCA: Microsoft has stated that they suspect that a potential deployment on there frontend gateways has caused SQL database availability issues impacting customer connectivity. Type: Incident

Duration: 4 days and 19 hours

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>11:50:00</var> GMT+0</small><br><strong>Investigating</strong> - User Impact: Service may be unavailable. Scope of Impact: Users trying to access the portal may see issues loading the page. Also call routing and recording may be affected. We are continuing to investigate the issue..</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>13:45:00</var> GMT+0</small><br><strong>Resolved</strong> - 4/3/2024 9:29 PM EST: Azure SQL service is experiencing an outage that is affecting the service. 4/3/2024 9:45 PM EST: Azure SQL service outage appears to have resolved. We are continuing to monitor. RCA: Microsoft has stated that they suspect that a potential deployment on there frontend gateways has caused SQL database availability issues impacting customer connectivity..</p> ]]> Wed, 3 Apr 2024 11:50:00 +0000 https://status.landis.cloud/incident/clul8kj2s15058b5ogmn8nj5vx https://status.landis.cloud/incident/clul8kj2s15058b5ogmn8nj5vx