Resolved after 2 hours 23 minutes, affecting Call Completion, on May 27, 2026.
Call flow has returned to normal, and calls are completing as expected. We are closing this incident. Our team will continue with the planned remediation work to reduce future impact from this third-party call-signing dependency.
Affected components
Update timeline
- monitoring May 27, 2026, 07:39 PM UTC
In our primary data center inbound/outbound calls are failing in several voice Pods and they are being routed to our secondary data center. Callers may experience intermittent call failures until we resolve this issue.
- identified May 27, 2026, 08:05 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 27, 2026, 08:48 PM UTC
We identified an issue with a third-party call-signing service provider and temporarily disabled that dependency to restore normal call flow. Calls are currently completing as expected. We are continuing to monitor call completion and will implement a remediation plan to reduce future impact from this dependency.
- resolved May 27, 2026, 10:03 PM UTC
Call flow has returned to normal, and calls are completing as expected. We are closing this incident. Our team will continue with the planned remediation work to reduce future impact from this third-party call-signing dependency.
Your product runs on more than Cytracom
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services