Update - We are continuing to work on a fix for this issue.
Jun 11, 2026 - 17:39 CEST
Update - We are continuing to actively follow up on the situation with our partner AWS and will share additional updates as soon as we receive more information.
Mar 16, 2026 - 06:45 CET
Update - We are continuing to work on a fix for this issue.
Mar 03, 2026 - 12:33 CET
Update - We remain in close coordination with our cloud providers to gain full visibility into the current situation. We will provide timely updates as soon as additional information becomes available.
Mar 03, 2026 - 12:07 CET
Identified - Due to the current geopolitical situation in the Middle East, some of our services operating in this region are currently impacted.
Several services are temporarily unavailable as certain cloud data centers in the affected area are experiencing connectivity and power disruptions.
At this stage, we do not yet have a confirmed timeline for full service restoration. Our teams are actively monitoring the situation and coordinating with our cloud infrastructure providers.
We will provide further updates as soon as additional information becomes available.
We appreciate your understanding and remain fully mobilized to restore normal operations as quickly as possible.
Mar 02, 2026 - 12:01 CET
Australia
Operational
SIP SBC for Webex Calling live recorder
Operational
UCX Cloud Suite
Operational
APJC
Operational
SIP SBC for Webex Calling live recorder
Operational
Resolved -
The service has been confirmed stable
Jul 2, 18:15 CEST
Monitoring -
On June 30, 2026 at 09:00 UTC, Microsoft began a planned, multi-day rotation of the TLS certificates presented by its Teams Direct Routing SIP endpoints, moving them to a new Certificate Authority chain on a staged, per-geography basis. During the rotation window, Teams endpoints presented a mix of legacy and new certificate chains.
Following the start of this activity, TLS sessions between our SBC infrastructure and the Teams SIP endpoints became progressively unstable, degrading Direct Routing signaling for a subset of trunks. Consistent with the staged nature of the Microsoft rotation, not all customers were impacted.
Full restoration required realigning the SBC certificate trust configuration to Microsoft's updated Certificate Authority set and performing a complete reset of all TLS connections towards Microsoft Teams. Service is stable now.
Jul 2, 15:16 CEST