SCB Global Ltd Status - Incident history https://status.scb-global.com SCB Global Ltd Tue, 3 Feb 2026 21:00:00 +0000 Attendant Console for Dialogue Cloud | EMEA | Emergency Maintenance Type: Maintenance Duration: 17 hours and 21 minutes Affected Components: Anywhere365 Feb 3, 21:00:00 GMT+0 - Identified - Dear customers and partners, We would like to inform you of an upcoming Emergency Maintenance Window on the Attendant Console for Dialogue Cloud platform, scheduled for today, February 03, at 21:00 UTC / 22:00 CET. During this window, we will deploy a configuration update to enhance platform stability. Maintenance Details: Date: Tuesday, February 03, 2026 Time: 21:00 UTC / 22:00 CET User Impact: The platform will experience a brief service interruption during the maintenance window. During this time, contact searches may not return results and caller recognition will be temporarily unavailable, while call control and other functionality will continue to operate normally. Expected Duration: We have allocated a maximum of 60 minutes for this maintenance activity. However, we anticipate that the actual change and tests will be completed within 30 minutes. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: [https://status.scb-global.com](https://status.anywhere.now) Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://supportdesk.anywhere.now) We apologize for the short notice and appreciate your understanding and cooperation. Thank you. SCB-Global Feb 3, 21:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 4, 14:20:36 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 17 hours and 21 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear customers and partners, We would like to inform you of an upcoming Emergency Maintenance Window on the Attendant Console for Dialogue Cloud platform, scheduled for today, February 03, at 21:00 UTC / 22:00 CET. During this window, we will deploy a configuration update to enhance platform stability. Maintenance Details: Date: Tuesday, February 03, 2026 Time: 21:00 UTC / 22:00 CET User Impact: The platform will experience a brief service interruption during the maintenance window. During this time, contact searches may not return results and caller recognition will be temporarily unavailable, while call control and other functionality will continue to operate normally. Expected Duration: We have allocated a maximum of 60 minutes for this maintenance activity. However, we anticipate that the actual change and tests will be completed within 30 minutes. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: [https://status.scb-global.com](https://status.anywhere.now) Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://supportdesk.anywhere.now) We apologize for the short notice and appreciate your understanding and cooperation. Thank you. SCB-Global.</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>21:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>14:20:36</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 3 Feb 2026 21:00:00 +0000 https://status.scb-global.com/maintenance/cml6uc5d508je8qowp5j5yusw https://status.scb-global.com/maintenance/cml6uc5d508je8qowp5j5yusw WebAgent | Global | https://webagent.anywhere365.io/ might be temporarily down Type: Incident Duration: 23 hours and 5 minutes Affected Components: Anywhere365 Oct 29, 16:43:17 GMT+0 - Investigating - Dear valued Customer and Partners, We are writing to inform you about a potential incident that has come to our attention. Please find the details below: User impact (Symptom): The webpage at <https://webagent.anywhere365.io/> might be temporarily down or it may have moved permanently to a new web address. Start Time: OCT 29, 16:24 UTC Scope of impact: Customers using the global WebAgent site. Current status: Investigating Root Cause: Under Investigation Next Steps: We are actively investigating the issue and will provide further updates within the next 60 minutes. Thank you for your collaboration and patience during this time. SCB - Global Oct 29, 17:05:46 GMT+0 - Investigating - Update: The issue may be related to a broader Microsoft outage, as indicated on the Azure Status Page: <https://azure.status.microsoft/en-us/status> We are continuing to investigate the incident to eliminate infrastructure components as a potential cause. An update will be provided within the next 60 min Thank you! Oct 29, 17:25:13 GMT+0 - Investigating - Incident Update: We continue our investigation; however, progress is limited due to the ongoing Azure outage, which is impacting our ability to fully troubleshoot our infrastructure. Workaround Available: As a temporary solution while services are being restored, customers can use the regional WebAgents addresses, which are currently unaffected by this issue. Oct 29, 18:01:31 GMT+0 - Investigating - Update from Microsoft: <https://azure.status.microsoft/en-us/status> "Starting at approximately 16:00 UTC, customers and Microsoft services that leverage Azure Front Door (AFD) may have experienced issues resulting in latencies, timeouts and errors. We have confirmed that an inadvertent configuration change as the trigger event for this issue. We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. " Update: Our ability to fully troubleshoot our infrastructure has been restored, and we are currently performing comprehensive checks. At this time, we have not identified any malfunctions within our infrastructure beyond the impact of the Microsoft outage. Investigation is ongoing. Workaround available: As a temporary solution while services are being restored, customers can use the regional WebAgents addresses, which are currently unaffected by this issue. Impacted customers who do not have a regional WebAgent configured and wish to apply this workaround can log a case through the support channels. Thank you! Oct 29, 19:05:58 GMT+0 - Investigating - Incident Update from: We continue to investigate further to eliminate infrastructure components as a potential cause. At this point, all evidence indicates that the Microsoft outage remains the most plausible root cause. Investigation is still ongoing. Workaround Status: The workaround offered, configuring regional WebAgents, has proven successful. We strongly encourage impacted customers to request assistance in applying this workaround by logging a support case through the usual channels. Microsoft Incident Status: <https://azure.status.microsoft/en-us/status> Azure Front Door - Connectivity issues - Applying mitigation Starting at approximately 16:00 UTC, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Current status: "We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure management portal directly, and while most portal extensions are functioning correctly, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes or once the deployment has completed. At that point, we will have a clearer understanding of the timeline for full recovery." Thank you! Oct 29, 19:24:33 GMT+0 - Monitoring - Incident status: Monitoring Incident Update: Our investigation confirms that the Microsoft outage is the root cause of this incident. We will continue to monitor the situation closely while assisting impacted customers with transitioning to regional WebAgents to ensure service continuity. Thank you! Oct 30, 10:54:17 GMT+0 - Monitoring - **Update** \- Update: Microsoft has completed their mitigation steps overnight, and we are now receiving confirmation that the Global WebAgent is back online and functioning as expected. We will keep this incident under monitoring and continue to observe the situation closely, in case the issue reappears. If any customer is still experiencing issues, please reach out to us via your regular support channels. Thank you! Oct 29, 20:38:24 GMT+0 - Monitoring - Incident Update: Our Global WebAgent URL is now accessible from some locations; however, it remains unavailable in others. We will keep this incident in Monitoring status while Microsoft continues implementing mitigation steps and will continue assisting impacted customers in restoring services via the available workaround. Progress on Microsoft’s side can be tracked here: <https://azure.status.microsoft/en-us/status> Workaround Status: Impacted customers can use the regional WebAgent URLs. This solution has proven successful, and we continue assisting customers who have requested help with its configuration. We encourage any affected customers to log a support case to apply this workaround. Oct 30, 15:48:45 GMT+0 - Resolved - Dear SCB-Global customers and partners, The Global WebAgent has been restored and remains stable after Microsoft completed its mitigation steps last night. We are therefore marking this incident as resolved now while we continue to observe the situation closely. If any customer is still experiencing issues, please reach out to us via your regular support channels. Thank you for your patience and cooperation. Type: Incident

Duration: 23 hours and 5 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>16:43:17</var> GMT+0</small><br><strong>Investigating</strong> - Dear valued Customer and Partners, We are writing to inform you about a potential incident that has come to our attention. Please find the details below: User impact (Symptom): The webpage at <https://webagent.anywhere365.io/> might be temporarily down or it may have moved permanently to a new web address. Start Time: OCT 29, 16:24 UTC Scope of impact: Customers using the global WebAgent site. Current status: Investigating Root Cause: Under Investigation Next Steps: We are actively investigating the issue and will provide further updates within the next 60 minutes. Thank you for your collaboration and patience during this time. SCB - Global.</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>17:05:46</var> GMT+0</small><br><strong>Investigating</strong> - Update: The issue may be related to a broader Microsoft outage, as indicated on the Azure Status Page: <https://azure.status.microsoft/en-us/status> We are continuing to investigate the incident to eliminate infrastructure components as a potential cause. An update will be provided within the next 60 min Thank you!.</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>17:25:13</var> GMT+0</small><br><strong>Investigating</strong> - Incident Update: We continue our investigation; however, progress is limited due to the ongoing Azure outage, which is impacting our ability to fully troubleshoot our infrastructure. Workaround Available: As a temporary solution while services are being restored, customers can use the regional WebAgents addresses, which are currently unaffected by this issue..</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>18:01:31</var> GMT+0</small><br><strong>Investigating</strong> - Update from Microsoft: <https://azure.status.microsoft/en-us/status> "Starting at approximately 16:00 UTC, customers and Microsoft services that leverage Azure Front Door (AFD) may have experienced issues resulting in latencies, timeouts and errors. We have confirmed that an inadvertent configuration change as the trigger event for this issue. We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. " Update: Our ability to fully troubleshoot our infrastructure has been restored, and we are currently performing comprehensive checks. At this time, we have not identified any malfunctions within our infrastructure beyond the impact of the Microsoft outage. Investigation is ongoing. Workaround available: As a temporary solution while services are being restored, customers can use the regional WebAgents addresses, which are currently unaffected by this issue. Impacted customers who do not have a regional WebAgent configured and wish to apply this workaround can log a case through the support channels. Thank you!.</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>19:05:58</var> GMT+0</small><br><strong>Investigating</strong> - Incident Update from: We continue to investigate further to eliminate infrastructure components as a potential cause. At this point, all evidence indicates that the Microsoft outage remains the most plausible root cause. Investigation is still ongoing. Workaround Status: The workaround offered, configuring regional WebAgents, has proven successful. We strongly encourage impacted customers to request assistance in applying this workaround by logging a support case through the usual channels. Microsoft Incident Status: <https://azure.status.microsoft/en-us/status> Azure Front Door - Connectivity issues - Applying mitigation Starting at approximately 16:00 UTC, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Current status: "We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure management portal directly, and while most portal extensions are functioning correctly, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes or once the deployment has completed. At that point, we will have a clearer understanding of the timeline for full recovery." Thank you!.</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>19:24:33</var> GMT+0</small><br><strong>Monitoring</strong> - Incident status: Monitoring Incident Update: Our investigation confirms that the Microsoft outage is the root cause of this incident. We will continue to monitor the situation closely while assisting impacted customers with transitioning to regional WebAgents to ensure service continuity. Thank you!.</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>10:54:17</var> GMT+0</small><br><strong>Monitoring</strong> - **Update** \- Update: Microsoft has completed their mitigation steps overnight, and we are now receiving confirmation that the Global WebAgent is back online and functioning as expected. We will keep this incident under monitoring and continue to observe the situation closely, in case the issue reappears. If any customer is still experiencing issues, please reach out to us via your regular support channels. Thank you!.</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>20:38:24</var> GMT+0</small><br><strong>Monitoring</strong> - Incident Update: Our Global WebAgent URL is now accessible from some locations; however, it remains unavailable in others. We will keep this incident in Monitoring status while Microsoft continues implementing mitigation steps and will continue assisting impacted customers in restoring services via the available workaround. Progress on Microsoft’s side can be tracked here: <https://azure.status.microsoft/en-us/status> Workaround Status: Impacted customers can use the regional WebAgent URLs. This solution has proven successful, and we continue assisting customers who have requested help with its configuration. We encourage any affected customers to log a support case to apply this workaround..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>15:48:45</var> GMT+0</small><br><strong>Resolved</strong> - Dear SCB-Global customers and partners, The Global WebAgent has been restored and remains stable after Microsoft completed its mitigation steps last night. We are therefore marking this incident as resolved now while we continue to observe the situation closely. If any customer is still experiencing issues, please reach out to us via your regular support channels. Thank you for your patience and cooperation..</p> ]]> Wed, 29 Oct 2025 16:43:17 +0000 https://status.scb-global.com/incident/cmhc85ilw00hf6ynwug5akow1 https://status.scb-global.com/incident/cmhc85ilw00hf6ynwug5akow1 Dialogue Cloud | EMEA - NORA | Certain phone numbers not working Type: Incident Duration: 6 days, 3 hours and 22 minutes Affected Components: Anywhere365 Oct 28, 12:43:50 GMT+0 - Identified - New incident: Identified Dear valued Customer and Partners, We would like to inform you of a service incident that may be affecting your experience. Please find the details below: User Impact: The main symptom is a number that was assigned to a working UCC no longer answers/completes. Scope of Impact: The issue is impacting a limited number of customers, and it affects random endpoints, not necessarily causing a full outage. Start Time: 27 October 2025, after 19:15 CET Current Status: Identified Root Cause: Under investigation Next Steps: We are actively supporting impacted customers to restore services. A full root cause analysis will be conducted, and findings will be shared through our Support portal. Thank you for your collaboration and patience during this time. Oct 28, 15:58:36 GMT+0 - Monitoring - **Update** \- We are continuing to monitor for any further issues. Oct 28, 2025 - 15:55 UTC **Monitoring** \- Dear SCB-Global Customers and Partners, We would like to provide an update regarding the previously reported issue affecting UCC Endpoint numbers. Scope of Impact: Initially reported for EMEA and NORA regions, the impact has now been confirmed to affect only a very limited number of customers in EMEA. Thank you for your collaboration and patience during this time. SCB-Global Nov 3, 16:06:16 GMT+0 - Resolved - **Resolved** \- Dear customers and partners, Mitigation steps have been successfully applied and confirmed effective for all affected customers. We are closing this incident as resolved now. A Root Cause Analysis (RCA) will be provided through our regular support channels. Customers who are still experiencing any issues, or who applied the resolution steps themselves and would like to receive the RCA, are invited to register a support case. We appreciate your patience and cooperation throughout this process. SCB-Global. Type: Incident

Duration: 6 days, 3 hours and 22 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>12:43:50</var> GMT+0</small><br><strong>Identified</strong> - New incident: Identified Dear valued Customer and Partners, We would like to inform you of a service incident that may be affecting your experience. Please find the details below: User Impact: The main symptom is a number that was assigned to a working UCC no longer answers/completes. Scope of Impact: The issue is impacting a limited number of customers, and it affects random endpoints, not necessarily causing a full outage. Start Time: 27 October 2025, after 19:15 CET Current Status: Identified Root Cause: Under investigation Next Steps: We are actively supporting impacted customers to restore services. A full root cause analysis will be conducted, and findings will be shared through our Support portal. Thank you for your collaboration and patience during this time..</p> <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>15:58:36</var> GMT+0</small><br><strong>Monitoring</strong> - **Update** \- We are continuing to monitor for any further issues. Oct 28, 2025 - 15:55 UTC **Monitoring** \- Dear SCB-Global Customers and Partners, We would like to provide an update regarding the previously reported issue affecting UCC Endpoint numbers. Scope of Impact: Initially reported for EMEA and NORA regions, the impact has now been confirmed to affect only a very limited number of customers in EMEA. Thank you for your collaboration and patience during this time. SCB-Global.</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>16:06:16</var> GMT+0</small><br><strong>Resolved</strong> - **Resolved** \- Dear customers and partners, Mitigation steps have been successfully applied and confirmed effective for all affected customers. We are closing this incident as resolved now. A Root Cause Analysis (RCA) will be provided through our regular support channels. Customers who are still experiencing any issues, or who applied the resolution steps themselves and would like to receive the RCA, are invited to register a support case. We appreciate your patience and cooperation throughout this process. SCB-Global..</p> ]]> Tue, 28 Oct 2025 12:43:50 +0000 https://status.scb-global.com/incident/cmhak5ptb00gt5unm4nqmcvko https://status.scb-global.com/incident/cmhak5ptb00gt5unm4nqmcvko Attendant Console for Dialogue Cloud | APAC | Scheduled Maintenance Type: Maintenance Duration: 1 hour Affected Components: Anywhere365 Oct 27, 12:00:00 GMT+0 - Identified - Dear SCB-Global customers and partners, We would like to inform you about an upcoming maintenance window for our Attendant Console for Dialogue Cloud platform. During this window, we will update the platform to a new release DC2025.01 Maintenance Details: Date: Monday, October 27, 2025 Time: 12:00 UTC User Impact: During this maintenance, users might notice a short service disruption Expected Duration: We have allocated 1 hour for this maintenance activity. However, we anticipate that the actual change will be completed within 30 min. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: [https://status.scb-global.com](https://status.anywhere365.io/) Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://supportdesk@scb-global.com](https://supportdesk.anywhere365.net/) Thank you. SCB-Global Oct 27, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 27, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear SCB-Global customers and partners, We would like to inform you about an upcoming maintenance window for our Attendant Console for Dialogue Cloud platform. During this window, we will update the platform to a new release DC2025.01 Maintenance Details: Date: Monday, October 27, 2025 Time: 12:00 UTC User Impact: During this maintenance, users might notice a short service disruption Expected Duration: We have allocated 1 hour for this maintenance activity. However, we anticipate that the actual change will be completed within 30 min. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: [https://status.scb-global.com](https://status.anywhere365.io/) Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://supportdesk@scb-global.com](https://supportdesk.anywhere365.net/) Thank you. SCB-Global.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 27 Oct 2025 12:00:00 +0000 https://status.scb-global.com/maintenance/cmh91wbnc00lw25bzg4s6ivjc https://status.scb-global.com/maintenance/cmh91wbnc00lw25bzg4s6ivjc Attendant Console for Dialogue Cloud | NORA | Scheduled Maintenance Type: Maintenance Duration: 3 hours and 40 minutes Affected Components: Anywhere365 Oct 27, 07:00:00 GMT+0 - Identified - Dear SCB - Gloabl customers and partners, We would like to inform you about an upcoming maintenance window for our Attendant Console for Dialogue Cloud platform. During this window, we will update the platform to a new release DC2025.01. Maintenance Details: Date: Monday, October 27, 2025 Time: 08:00 UTC User Impact: During this maintenance, users might notice a short service disruption Expected Duration: We have allocated 1 hour for this maintenance activity. However, we anticipate that the actual change will be completed within 30 min. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: <https://status.scb-global.com/> Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://supportdesk.anywhere365.net/) Thank you for your understanding and cooperation. Kind regards, SCB-Global Oct 27, 10:01:52 GMT+0 - Identified - Maintenance update Update: We are currently performing post-maintenance sanity checks. The process is progressing as expected, and we estimate completion within the next 30 minutes. We will provide a final update once the maintenance is fully completed. Oct 27, 10:40:21 GMT+0 - Completed - Update: All post-maintenance tests have been completed successfully, and the system is fully operational. Thank you for your patience during this maintenance window Oct 27, 08:58:34 GMT+0 - Identified - Maintenance update Update: The ongoing maintenance is taking longer than anticipated and will be extended by approximately one additional hour. We are actively working to complete the process as quickly as possible and will provide further updates once the maintenance has concluded. Thank you for your patience and understanding. Type: Maintenance

Duration: 3 hours and 40 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear SCB - Gloabl customers and partners, We would like to inform you about an upcoming maintenance window for our Attendant Console for Dialogue Cloud platform. During this window, we will update the platform to a new release DC2025.01. Maintenance Details: Date: Monday, October 27, 2025 Time: 08:00 UTC User Impact: During this maintenance, users might notice a short service disruption Expected Duration: We have allocated 1 hour for this maintenance activity. However, we anticipate that the actual change will be completed within 30 min. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: <https://status.scb-global.com/> Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://supportdesk.anywhere365.net/) Thank you for your understanding and cooperation. Kind regards, SCB-Global.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:01:52</var> GMT+0</small><br><strong>Identified</strong> - Maintenance update Update: We are currently performing post-maintenance sanity checks. The process is progressing as expected, and we estimate completion within the next 30 minutes. We will provide a final update once the maintenance is fully completed..</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:40:21</var> GMT+0</small><br><strong>Completed</strong> - Update: All post-maintenance tests have been completed successfully, and the system is fully operational. Thank you for your patience during this maintenance window.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>08:58:34</var> GMT+0</small><br><strong>Identified</strong> - Maintenance update Update: The ongoing maintenance is taking longer than anticipated and will be extended by approximately one additional hour. We are actively working to complete the process as quickly as possible and will provide further updates once the maintenance has concluded. Thank you for your patience and understanding..</p> ]]> Mon, 27 Oct 2025 07:00:00 +0000 https://status.scb-global.com/maintenance/cmh8snyt800i011lht1v4hcyx https://status.scb-global.com/maintenance/cmh8snyt800i011lht1v4hcyx Receptionist for Broadworks | Emergency Maintenance | Identity Service Type: Maintenance Duration: 11 hours Affected Components: Anywhere365 Oct 27, 07:00:01 GMT+0 - Completed - Maintenance has completed successfully Oct 27, 18:00:00 GMT+0 - Identified - Dear SCB - Global Customer & Partner, We would like to inform you about an upcoming maintenance window. During this window, we will update the Identity Service to ensure browser compatibility via <https://teams.cloud.microsoft/> Maintenance Details: Date: Monday, October 27, 2025 Time: 18:00 UTC / 20:00 CET User Impact: During this maintenance, users will notice a short service disruption in which the platform will not be available. New calls will not be established during this period, but the already established calls will not be impacted. Expected Duration: We have allocated 1 hour for this maintenance activity. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: <https://status.scb-global.com/> Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://support.anywhere.now/) We apologize for the short notice and appreciate your understanding as we work to ensure a seamless and secure experience across supported platforms. Kind regards, SCB-Global Oct 27, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 11 hours

Affected Components:

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear SCB - Global Customer & Partner, We would like to inform you about an upcoming maintenance window. During this window, we will update the Identity Service to ensure browser compatibility via <https://teams.cloud.microsoft/> Maintenance Details: Date: Monday, October 27, 2025 Time: 18:00 UTC / 20:00 CET User Impact: During this maintenance, users will notice a short service disruption in which the platform will not be available. New calls will not be established during this period, but the already established calls will not be impacted. Expected Duration: We have allocated 1 hour for this maintenance activity. System Status and Maintenance Schedule: To check the system status and review upcoming and previous maintenance windows, please visit our status page: <https://status.scb-global.com/> Support and Questions: If you have any questions or encounter issues, please submit them via our support desk: [https://support@scb-global.com](https://support.anywhere.now/) We apologize for the short notice and appreciate your understanding as we work to ensure a seamless and secure experience across supported platforms. Kind regards, SCB-Global.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Mon, 27 Oct 2025 06:00:01 +0000 https://status.scb-global.com/maintenance/cmh3mdjft00986u6yrmbqsaq5 https://status.scb-global.com/maintenance/cmh3mdjft00986u6yrmbqsaq5 Azure Front Door Services experiencing 5XX errors - WebAgent loading and sign-in issues Type: Incident Duration: 19 hours and 43 minutes Affected Components: Anywhere365 Sep 15, 19:28:13 GMT+0 - Identified - \*\*Update\*\* \\- Dear Customer/Partner, Microsoft has provided a new status update: Our automated service monitoring detected a gradual increase in request failures, primarily affecting a small subset of cache-miss traffic. The issue has been intermittent and, at peak, impacted approximately 0.25% of overall traffic in affected environments. Preliminary investigation attributes the failures to increased traffic volume. Most retry requests succeed, and to mitigate the issue, we have provisioned additional capacity in overloaded environments. Further optimizations are also being deployed to reduce load and improve resilience. Recovery has already been observed for some customers, and we continue to closely monitor the situation. We will keep you informed as the situation evolves. Kind regards, SCB Global. Sep 15, 16:00:00 GMT+0 - Identified - Dear Customer/Partner, Microsoft has informed us they are currently experiencing an issue with customers using Azure Front Door Services. As a result of these issue, customers may experience intermittent errors when using our WebAgent services. Impacted regions are: \- Azure Frontdoor Central US \- East US \- East US 2 \- North Central US \- South Central US \- West US Microsoft has stated in their communication that they have detected a gradual increase in request failures, although most requests succeed after a retry. Microsoft has provisioned additional capacity to alleviate overloaded environments, and further optimizations are currentlu being deployed by Microsoft to reduce load on affected services. We are actively monitoring the situation, and recovery has already been observed by some customers. We will keep you informed as the situation evolves. Kind regards, SCB Global Sep 16, 11:43:25 GMT+0 - Resolved - Incident Update We are pleased to confirm that the issue has been fully resolved, and this announcement is now being closed. A root cause analysis has already been initiated, and the details will be shared following our standard processes. Thank you for your patience and understanding. Sep 17, 13:28:31 GMT+0 - Postmortem - **Reason for Outage (RfO) Report for Slowness in WebAgent** | Date & Time of Outage | 12:05 UTC 15/09/2025 - 21:33 UTC | | --------------------- | ----------------------------------------------------- | | Severity Level | P2 - Core Systems Failure (Partial Services Affected) | | Affected Service(s) | WebAgent | | Report Date | 17 September 2025 | **Incident Details** **What users experienced**: * Users encountered very slow loading times when accessing the WebAgent URL and also experienced difficulties signing in. Sometimes users were experiencing 504 (Gateway Timeout) errors. **Who was impacted:** * Microsoft initially communicated multiple regions in the US, but later narrowed this down to customers accessing services in the East US. **When did the issue start:** * Customers informed us that on 15 September, they received a lot of reports from their users of the slowness to login to WebAgent. **When was the issue resolved:** * Microsoft communicated the following actions during the event: 17:19 UTC on 15 September 2025 * Additional capacity was provisioned to address overloaded environments. * This reduced the frequency of error rates, but lower-volume error rates were still observed from our telemetry. * 20:12 UTC on 15 September 2025 - Additional throughput optimization was rolled out to reduce system load further. * 21:33 UTC on 15 September 2025 – Service(s) restored, customer impact mitigated, and verified by service telemetry. ### **SCB Global apologizes for any inconvenience this incident may have caused.** **Root Cause:** A platform issue impacted Azure Front Door (Standard, Premium, and Classic SKUs) and Azure CDN Standard from Microsoft. The impact was limited to two Points of Presence (PoPs) in East US and affected only cache-miss traffic **Detection Method:** Manual verification and troubleshooting by the SCB technical team. **Corrective Actions:** Actions taken, lessons learned, and next step from customer/partner: * Microsoft’s initial communication was delayed by three hours from the time the issue occurred, which prevented us from providing proactive, meaningful updates to customers. As we are technically dependent on Microsoft and no actions on our side could have prevented this incident, no further measures will be taken. Type: Incident

Duration: 19 hours and 43 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>19:28:13</var> GMT+0</small><br><strong>Identified</strong> - \*\*Update\*\* \\- Dear Customer/Partner, Microsoft has provided a new status update: Our automated service monitoring detected a gradual increase in request failures, primarily affecting a small subset of cache-miss traffic. The issue has been intermittent and, at peak, impacted approximately 0.25% of overall traffic in affected environments. Preliminary investigation attributes the failures to increased traffic volume. Most retry requests succeed, and to mitigate the issue, we have provisioned additional capacity in overloaded environments. Further optimizations are also being deployed to reduce load and improve resilience. Recovery has already been observed for some customers, and we continue to closely monitor the situation. We will keep you informed as the situation evolves. Kind regards, SCB Global..</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear Customer/Partner, Microsoft has informed us they are currently experiencing an issue with customers using Azure Front Door Services. As a result of these issue, customers may experience intermittent errors when using our WebAgent services. Impacted regions are: \- Azure Frontdoor Central US \- East US \- East US 2 \- North Central US \- South Central US \- West US Microsoft has stated in their communication that they have detected a gradual increase in request failures, although most requests succeed after a retry. Microsoft has provisioned additional capacity to alleviate overloaded environments, and further optimizations are currentlu being deployed by Microsoft to reduce load on affected services. We are actively monitoring the situation, and recovery has already been observed by some customers. We will keep you informed as the situation evolves. Kind regards, SCB Global.</p> <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>11:43:25</var> GMT+0</small><br><strong>Resolved</strong> - Incident Update We are pleased to confirm that the issue has been fully resolved, and this announcement is now being closed. A root cause analysis has already been initiated, and the details will be shared following our standard processes. Thank you for your patience and understanding..</p> <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>13:28:31</var> GMT+0</small><br><strong>Postmortem</strong> - **Reason for Outage (RfO) Report for Slowness in WebAgent** | Date & Time of Outage | 12:05 UTC 15/09/2025 - 21:33 UTC | | --------------------- | ----------------------------------------------------- | | Severity Level | P2 - Core Systems Failure (Partial Services Affected) | | Affected Service(s) | WebAgent | | Report Date | 17 September 2025 | **Incident Details** **What users experienced**: * Users encountered very slow loading times when accessing the WebAgent URL and also experienced difficulties signing in. Sometimes users were experiencing 504 (Gateway Timeout) errors. **Who was impacted:** * Microsoft initially communicated multiple regions in the US, but later narrowed this down to customers accessing services in the East US. **When did the issue start:** * Customers informed us that on 15 September, they received a lot of reports from their users of the slowness to login to WebAgent. **When was the issue resolved:** * Microsoft communicated the following actions during the event: 17:19 UTC on 15 September 2025 * Additional capacity was provisioned to address overloaded environments. * This reduced the frequency of error rates, but lower-volume error rates were still observed from our telemetry. * 20:12 UTC on 15 September 2025 - Additional throughput optimization was rolled out to reduce system load further. * 21:33 UTC on 15 September 2025 – Service(s) restored, customer impact mitigated, and verified by service telemetry. ### **SCB Global apologizes for any inconvenience this incident may have caused.** **Root Cause:** A platform issue impacted Azure Front Door (Standard, Premium, and Classic SKUs) and Azure CDN Standard from Microsoft. The impact was limited to two Points of Presence (PoPs) in East US and affected only cache-miss traffic **Detection Method:** Manual verification and troubleshooting by the SCB technical team. **Corrective Actions:** Actions taken, lessons learned, and next step from customer/partner: * Microsoft’s initial communication was delayed by three hours from the time the issue occurred, which prevented us from providing proactive, meaningful updates to customers. As we are technically dependent on Microsoft and no actions on our side could have prevented this incident, no further measures will be taken..</p> ]]> Mon, 15 Sep 2025 16:00:00 +0000 https://status.scb-global.com/incident/cmflgbvvs01zbv7mpiu47ik8o https://status.scb-global.com/incident/cmflgbvvs01zbv7mpiu47ik8o Web Agent on Dialogue Cloud V3 | EMEA | Presence Synchronization. Type: Incident Duration: 1 day, 1 hour and 34 minutes Affected Components: Anywhere365 Jul 7, 13:04:08 GMT+0 - Investigating - Dear Valued Customers and Partners, Current Status: Investigating Root Cause: Under Investigation Next Steps: Following a comprehensive internal review, we have successfully ruled out the majority of components within our own infrastructure as potential causes. While we continue to investigate on our side, we are now escalating the issue by logging a support case with Microsoft. We are closely monitoring the situation and will collaborate with Microsoft to identify and resolve the issue as swiftly as possible. We remain committed to keeping you informed and will provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding. Jul 7, 14:23:33 GMT+0 - Identified - Web Agent on Dialogue Cloud V3 | EMEA | Presence Synchronization. Incident status: Identified Dear Valued Customers and Partners, Incident State Update Current Impact: Due to incorrect presence status being returned, agents are not being hunted as expected, which may result in missed or delayed call routing. Current Status: Identified We are seeing intermittent improvements in presence updates, followed by recurring delays. The delays appear to stem from Microsoft’s Graph API, which is impacting the retrieval of user presence information. This affects our ability to route calls accurately, as real-time presence data is essential for determining agent availability. Through testing via Graph Explorer in a fully isolated environment outside of the Anywhere365 infrastructure, we have confirmed that the issue originates externally, likely on Microsoft’s side, though this has not yet been officially acknowledged by Microsoft. Workaround: For customers using WebAgent or Snapper, agents can manually pick up calls from the queue as a temporary measure while we await further updates from Microsoft. Next Steps: We continue to escalate the case with Microsoft and will provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding. Jul 7, 14:56:36 GMT+0 - Identified - Update Dear Valued Customers and Partners, Microsoft is currently investigating our escalation regarding the ongoing issue. To help expedite the resolution, we kindly ask that you open your own support ticket with Microsoft and reference our case number: 2507070050002791. By raising additional tickets, you help highlight the urgency and increase the priority of the case on Microsoft's side. We will continue to keep you informed as soon as we receive further updates from Microsoft. Thank you for your continued support and patience. Jul 7, 16:58:27 GMT+0 - Identified - Update Dear valued Customers and Partners, We would like to inform you that Microsoft has acknowledged an ongoing outage in Microsoft 365 / Exchange Online affecting free/busy and presence data. This issue specifically impacts the EMEA region and may cause delays or inconsistencies in presence updates within their platform, which in turn impacts the functionality of AnywhereNow. This incident is tracked by Microsoft under Service Incident ID: EX1110700 and is visible in the Microsoft 365 Admin Center under the Service Health Dashboard. Please note that this is a Microsoft-side issue, and we are closely monitoring their updates. We will continue to keep you informed as more information becomes available. Thank you for your understanding and continued patience. Jul 7, 19:09:25 GMT+0 - Identified - Update: Dear valued Customer and Partners, We are still experiencing an issue where agents are not being hunted due to presence delays. Microsoft has confirmed this problem originates from Microsoft Exchange Online, where a portion of the infrastructure responsible for handling presence data is not processing requests efficiently. As a result, certain requests for availability information are timing out before a response is returned. Microsoft is actively working on the problem. Their engineering teams are analyzing detailed logs and network traces to pinpoint the root cause and develop a fix to restore normal functionality. Until the issue is fully resolved on Microsoft's side, presence features within Anywhere365 may behave inconsistently for impacted users. Best regards, Jul 7, 20:37:41 GMT+0 - Identified - Update: Dear valued Customer and Partners, We've received feedback from several customers indicating that Service Incident ID: EX1110700 is not visible in their Microsoft 365 Admin Center under the Service Health Dashboard. We have escalated this concern to Microsoft and provided them with the details of the impacted tenants. Microsoft has confirmed they will begin working on ensuring the incident is properly surfaced to all affected customers. Best regards, Jul 8, 10:25:50 GMT+0 - Identified - Update: Dear Valued Customers and Partners, Incident Update: We are seeing noticeable improvements in our logs for most customers who were impacted by this issue. Additionally, we’ve received some positive feedback from customers, indicating that the situation is improving for them. We continue to monitor the situation closely while awaiting further updates from Microsoft to confirm a full resolution We appreciate your continued patience and will share more information as it becomes available. Jul 8, 12:01:49 GMT+0 - Monitoring - Dear valued Customers, Incident status update: We have received confirmation from Microsoft that the fix has been successfully deployed. Our internal monitoring also confirms continued improvements in our logs. We will be reaching out to impacted customers directly to confirm that service has been fully restored. If you are still experiencing issues, please contact us via your regular support channel. If you have an open case with Microsoft, we recommend updating them as well. Thank you for your patience and continued collaboration. Jul 8, 14:38:31 GMT+0 - Resolved - Resolved Dear valued Customers and Partners, We are pleased to confirm that the issue has been fully resolved, and services are functioning normally. We are collaborating closely with Microsoft and will provide the RCA to affected customers through their support cases, following our usual process. Thank you for your patience and understanding during this incident. Feel free to contact us with any questions or for further clarification. Type: Incident

Duration: 1 day, 1 hour and 34 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>13:04:08</var> GMT+0</small><br><strong>Investigating</strong> - Dear Valued Customers and Partners, Current Status: Investigating Root Cause: Under Investigation Next Steps: Following a comprehensive internal review, we have successfully ruled out the majority of components within our own infrastructure as potential causes. While we continue to investigate on our side, we are now escalating the issue by logging a support case with Microsoft. We are closely monitoring the situation and will collaborate with Microsoft to identify and resolve the issue as swiftly as possible. We remain committed to keeping you informed and will provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:23:33</var> GMT+0</small><br><strong>Identified</strong> - Web Agent on Dialogue Cloud V3 | EMEA | Presence Synchronization. Incident status: Identified Dear Valued Customers and Partners, Incident State Update Current Impact: Due to incorrect presence status being returned, agents are not being hunted as expected, which may result in missed or delayed call routing. Current Status: Identified We are seeing intermittent improvements in presence updates, followed by recurring delays. The delays appear to stem from Microsoft’s Graph API, which is impacting the retrieval of user presence information. This affects our ability to route calls accurately, as real-time presence data is essential for determining agent availability. Through testing via Graph Explorer in a fully isolated environment outside of the Anywhere365 infrastructure, we have confirmed that the issue originates externally, likely on Microsoft’s side, though this has not yet been officially acknowledged by Microsoft. Workaround: For customers using WebAgent or Snapper, agents can manually pick up calls from the queue as a temporary measure while we await further updates from Microsoft. Next Steps: We continue to escalate the case with Microsoft and will provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:56:36</var> GMT+0</small><br><strong>Identified</strong> - Update Dear Valued Customers and Partners, Microsoft is currently investigating our escalation regarding the ongoing issue. To help expedite the resolution, we kindly ask that you open your own support ticket with Microsoft and reference our case number: 2507070050002791. By raising additional tickets, you help highlight the urgency and increase the priority of the case on Microsoft's side. We will continue to keep you informed as soon as we receive further updates from Microsoft. Thank you for your continued support and patience..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>16:58:27</var> GMT+0</small><br><strong>Identified</strong> - Update Dear valued Customers and Partners, We would like to inform you that Microsoft has acknowledged an ongoing outage in Microsoft 365 / Exchange Online affecting free/busy and presence data. This issue specifically impacts the EMEA region and may cause delays or inconsistencies in presence updates within their platform, which in turn impacts the functionality of AnywhereNow. This incident is tracked by Microsoft under Service Incident ID: EX1110700 and is visible in the Microsoft 365 Admin Center under the Service Health Dashboard. Please note that this is a Microsoft-side issue, and we are closely monitoring their updates. We will continue to keep you informed as more information becomes available. Thank you for your understanding and continued patience..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>19:09:25</var> GMT+0</small><br><strong>Identified</strong> - Update: Dear valued Customer and Partners, We are still experiencing an issue where agents are not being hunted due to presence delays. Microsoft has confirmed this problem originates from Microsoft Exchange Online, where a portion of the infrastructure responsible for handling presence data is not processing requests efficiently. As a result, certain requests for availability information are timing out before a response is returned. Microsoft is actively working on the problem. Their engineering teams are analyzing detailed logs and network traces to pinpoint the root cause and develop a fix to restore normal functionality. Until the issue is fully resolved on Microsoft's side, presence features within Anywhere365 may behave inconsistently for impacted users. Best regards,.</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>20:37:41</var> GMT+0</small><br><strong>Identified</strong> - Update: Dear valued Customer and Partners, We've received feedback from several customers indicating that Service Incident ID: EX1110700 is not visible in their Microsoft 365 Admin Center under the Service Health Dashboard. We have escalated this concern to Microsoft and provided them with the details of the impacted tenants. Microsoft has confirmed they will begin working on ensuring the incident is properly surfaced to all affected customers. Best regards,.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>10:25:50</var> GMT+0</small><br><strong>Identified</strong> - Update: Dear Valued Customers and Partners, Incident Update: We are seeing noticeable improvements in our logs for most customers who were impacted by this issue. Additionally, we’ve received some positive feedback from customers, indicating that the situation is improving for them. We continue to monitor the situation closely while awaiting further updates from Microsoft to confirm a full resolution We appreciate your continued patience and will share more information as it becomes available..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:01:49</var> GMT+0</small><br><strong>Monitoring</strong> - Dear valued Customers, Incident status update: We have received confirmation from Microsoft that the fix has been successfully deployed. Our internal monitoring also confirms continued improvements in our logs. We will be reaching out to impacted customers directly to confirm that service has been fully restored. If you are still experiencing issues, please contact us via your regular support channel. If you have an open case with Microsoft, we recommend updating them as well. Thank you for your patience and continued collaboration..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>14:38:31</var> GMT+0</small><br><strong>Resolved</strong> - Resolved Dear valued Customers and Partners, We are pleased to confirm that the issue has been fully resolved, and services are functioning normally. We are collaborating closely with Microsoft and will provide the RCA to affected customers through their support cases, following our usual process. Thank you for your patience and understanding during this incident. Feel free to contact us with any questions or for further clarification..</p> ]]> Mon, 7 Jul 2025 13:04:08 +0000 https://status.scb-global.com/incident/cmct44kql00025gd3kw95mjn9 https://status.scb-global.com/incident/cmct44kql00025gd3kw95mjn9 Scheduled Maintenance – Application Server Downtime Type: Maintenance Duration: 30 minutes Affected Components: OPTO4Teams Portal, OPTO4 SMS, Operator Connect Jul 4, 16:00:00 GMT+0 - Identified - Dear Team, Please be informed that the application server will undergo scheduled maintenance as part of our regular efforts to ensure optimal performance, security and backup. **Maintenance Details:** **Date:** Friday, 4th of July 2025 **Time: 18:00** _UK_ **Duration:** 30 Minutes **Affected Services:** OPTO4Teams Portal, SMS and Operator Connect. **Purpose:** Backup and Security During this time, the application(s) may be temporarily unavailable. We advise all users to save their work and log off from the system before the maintenance window begins. We apologize for any inconvenience this may cause and appreciate your cooperation and understanding. If you have any questions or concerns, please share with us. Thank you for your attention. Best regards, SCB - Global Type: Maintenance

Duration: 30 minutes

Affected Components: , ,

<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - Dear Team, Please be informed that the application server will undergo scheduled maintenance as part of our regular efforts to ensure optimal performance, security and backup. **Maintenance Details:** **Date:** Friday, 4th of July 2025 **Time: 18:00** _UK_ **Duration:** 30 Minutes **Affected Services:** OPTO4Teams Portal, SMS and Operator Connect. **Purpose:** Backup and Security During this time, the application(s) may be temporarily unavailable. We advise all users to save their work and log off from the system before the maintenance window begins. We apologize for any inconvenience this may cause and appreciate your cooperation and understanding. If you have any questions or concerns, please share with us. Thank you for your attention. Best regards, SCB - Global.</p> ]]> Fri, 4 Jul 2025 16:00:00 +0000 https://status.scb-global.com/maintenance/cmcjgqe1l000uw15qnbkvfw90 https://status.scb-global.com/maintenance/cmcjgqe1l000uw15qnbkvfw90 Anywhere365 Dialogue Cloud V3 Direct Routing | AMER region Type: Incident Duration: 1 hour and 33 minutes Affected Components: Anywhere365 Mar 28, 20:58:14 GMT+0 - Identified - Dear Customer/Partner, We have identified the potential issue and are actively working on implementing a resolution. Thank you for your patience as we work to restore normal service. Mar 28, 19:59:23 GMT+0 - Investigating - **Investigating** \- Dear Customer and Partner, We are currently experiencing a service disruption on our Dialogue Cloud V3 platform in the NORA region and are actively investigating the issue. Our team is working to identify and resolve the problem as quickly as possible. If you are experiencing this issue, please inform us by raising it through our Support Portal. [https://supportdesk.anywhere365.net/ We](https://supportdesk.anywhere365.net/We) appreciate your patience and will provide updates as soon as we have more information. Thank you for your patience and understanding. Mar 28, 2025 - 19:52 UTC Mar 28, 20:30:23 GMT+0 - Investigating - Dear Customers and Partners, Our team is still actively investigating the issue. We are working diligently to identify the cause and implement a resolution as soon as possible. We appreciate your patience and will share further updates as soon as we have more information. Posted 1 minute ago. Mar 28, 2025 - 20:23 UTC Mar 28, 21:31:55 GMT+0 - Resolved - Dear Customer/Partner, We have identified the root cause of the issue and implemented the necessary actions to resolve it. At this time, the issue should be fully resolved. We kindly ask you to test and confirm this. If you are still experiencing any issues, please update the existing support case so we can investigate further. Additionally, we will provide a detailed Root Cause Analysis (RCA) via opened Support cases. Thank you for your patience and cooperation. Type: Incident

Duration: 1 hour and 33 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>20:58:14</var> GMT+0</small><br><strong>Identified</strong> - Dear Customer/Partner, We have identified the potential issue and are actively working on implementing a resolution. Thank you for your patience as we work to restore normal service..</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>19:59:23</var> GMT+0</small><br><strong>Investigating</strong> - **Investigating** \- Dear Customer and Partner, We are currently experiencing a service disruption on our Dialogue Cloud V3 platform in the NORA region and are actively investigating the issue. Our team is working to identify and resolve the problem as quickly as possible. If you are experiencing this issue, please inform us by raising it through our Support Portal. [https://supportdesk.anywhere365.net/ We](https://supportdesk.anywhere365.net/We) appreciate your patience and will provide updates as soon as we have more information. Thank you for your patience and understanding. Mar 28, 2025 - 19:52 UTC.</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>20:30:23</var> GMT+0</small><br><strong>Investigating</strong> - Dear Customers and Partners, Our team is still actively investigating the issue. We are working diligently to identify the cause and implement a resolution as soon as possible. We appreciate your patience and will share further updates as soon as we have more information. Posted 1 minute ago. Mar 28, 2025 - 20:23 UTC.</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>21:31:55</var> GMT+0</small><br><strong>Resolved</strong> - Dear Customer/Partner, We have identified the root cause of the issue and implemented the necessary actions to resolve it. At this time, the issue should be fully resolved. We kindly ask you to test and confirm this. If you are still experiencing any issues, please update the existing support case so we can investigate further. Additionally, we will provide a detailed Root Cause Analysis (RCA) via opened Support cases. Thank you for your patience and cooperation..</p> ]]> Fri, 28 Mar 2025 19:59:23 +0000 https://status.scb-global.com/incident/cm8t7hk4k000d33io4q0f7aml https://status.scb-global.com/incident/cm8t7hk4k000d33io4q0f7aml