3b68eb55-25c3-41c1-8daa-3a248fd856b8 18cb9b9e-003f-47b7-8e72-f8c077e709f0 d6d7a227-6bfa-4eb7-8325-7cb6d3613614 cbcae857-2974-431d-9e50-581a15d34c1d d5a590ad-e391-40bc-82e7-2202650e62c5 244f749f-a98a-470a-9769-3caa9050ac9a All failing with "Unknown error" From TWILIO: Debug event SID NO6e8568280c38fc1285a70a6b1a67c3bb Service SID -- Resource SID CA8fd2fee9b732746b62efdf73dff0f80e Timestamp 2:30pm UTC 2024-Aug-30 Message Stream - WebSocket - Connection Timeout Error Description Possible Solutions Verify server connectivity Verify the TwiML URL is correct Verify intermediate elements are routing traffic and firewall are not blocking ports Possible Causes WebSocket server is not connected to any network Bad IP address provided in the TwiML URL Intermediate elements (like ngrok) are not routing traffic There is a firewall blocking the traffic

@Alberto I'm sorry to hear that you're experiencing issues with multiple call failures and an "Unknown error" message. It seems like there might be a problem with the WebSocket connection based on the debug event SID from Twilio you've provided. Here are some steps you can take to troubleshoot the issue: 1. **Verify Server Connectivity**: Ensure that the server you're trying to connect to is up and running and that there are no network issues that might be causing the connection timeout. 2. **Check the TwiML URL**: Make sure that the TwiML URL provided in your call setup is correct and accessible. The URL should return valid TwiML instructions for Twilio to execute. 3. **Intermediate Elements**: If you're using services like ngrok for tunneling or any other intermediate elements, verify that they are correctly routing traffic to your server. 4. **Firewall Settings**: Check if there are any firewalls that might be blocking the WebSocket traffic. Ensure that the necessary ports are open for communication. 5. **WebSocket Server Network**: Confirm that the WebSocket server is properly connected to a network and that the IP address provided in the TwiML URL is correct. If you've gone through these steps and the problem persists, it might be beneficial to look into the specific error codes associated with each failed call ID you've provided. This can give us more insight into what might be causing the issue. If you need further assistance with this matter, please don't hesitate to ask for more information.

This seems to be stabilized now

It was intermittent (maybe still is)

Same here, we had bunch of

unknwon-errors

on that same day. I guess vapi had some instabilities at that time. But it's not visible on the status page @User 🤔

can you create a new support ticket for it

I won't create a new support ticket as it's the same issue as this one, and it's stabilized now. But I'm interested on knowing the root cause

someone tried to played with our system but we dodge the ball.