Resolution: The remediation was successfully implemented and normal service was restored. We have since received confirmation from impacted customers that the issue is resolved. Based on this validation, we are closing the incident.
Root Cause: The root cause was confirmed as an issue with the static route between the SBC services and the backend components.
Next Steps: An RCA is currently being prepared and will be provided through the standard Support channels once completed.
We sincerely apologize for the disruption this incident caused and thank you for your patience and understanding while our teams worked to restore service.
AnywhereNow
Posted Oct 22, 2026 - 15:23 UTC
Monitoring
Incident Update
Current Status: Monitoring
Resolution: The remediation steps have been successfully implemented and have restored normal call processing. Initial validation confirms that the corrective actions have resolved the service impact.
Root Cause: The root cause was confirmed as an issue with the static network route between the SBC services and the backend components.
Next Steps: We are continuing to monitor the platform to confirm sustained service stability. In parallel, we will proactively contact customers who reported the issue to confirm that services are fully operational within their environments.
Next Update: A further update will be provided once monitoring and customer validation have been completed, or sooner if any significant change is observed.
Posted Oct 22, 2026 - 13:40 UTC
Update
Incident Update
Current Status: Identified
Root Cause: The root cause has been confirmed as an issue with the static network route between the SBC services and the backend components.
Next Steps: Remediation is currently in progress. Based on the current progress, the estimated time to resolution is approximately 30 minutes. Following remediation, our teams will validate service recovery and normal call processing.
Next Update: Within 30 minutes, or sooner if further information becomes available.
Posted Oct 22, 2026 - 13:20 UTC
Identified
Incident Update
Current Status: Identified
Root Cause: The root cause has been confirmed as an issue with the static network route between the SBC services and the backend components.
Next Steps: Our teams are actively implementing the required remediation to restore normal call processing. Service recovery will be validated following the change.
Next Update: Within 45 minutes, or sooner if further information becomes available.
Posted Oct 22, 2026 - 13:17 UTC
Update
Incident Update
Current Status: Investigating
Root Cause: While the root cause has not yet been confirmed, the investigation has narrowed to specific backend components, including SBC-related services.
Next Steps: We are actively validating the identified correlation and performing further investigation to confirm the underlying cause and determine the appropriate remediation.
Next Update: Within 60 minutes.
Posted Oct 22, 2026 - 12:55 UTC
Investigating
Dear valued Customer and Partners,
We are currently investigating an issue affecting Dialogue Cloud, impacting both inbound and outbound interactions on the EMEA WEU Region.
Scope of impact: Dialogue Cloud - EMEA WEU Region - Inbound and Outbound calls
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.
Thanks for your collaboration,
Best regards,
AnywhereNow
Posted Oct 22, 2026 - 12:37 UTC
This incident affected: Dialogue Cloud V3 (EMEA-WEU Direct Routing).