Urgent: Twilio Connection Timeout (Error 11205)
# supporth
hendricmartens
01/29/2025, 12:26 PMHi VAPI Team,
We are experiencing an issue where Twilio fails to connect to the VAPI servers, resulting in a timeout error (11205). The error message states:
Request to https://api.vapi.ai/twilio/inbound_call timed out.
According to Twilio’s logs, the issue appears to be a network connection failure, where Twilio is unable to establish a TCP connection or receive an HTTP response within the timeout period. The error details indicate a 502 HTTP status, suggesting a potential server-side issue.
Could you please check if there are any known outages or issues on your end? Also, any insights into what might be causing this would be greatly appreciated.
Let me know if you need any additional information to investigate further.
Thanks in advance for your support!
a
Atlas
01/29/2025, 12:26 PMHeyhendricmartens Thank you for creating the ticket! A member of our team will reach out to you shortly.
v
Vapi
01/29/2025, 12:28 PMmessage has been deleted
Vapi
01/29/2025, 12:29 PMYou can continue this conversation by mentioning me in the message.
Vapi
01/29/2025, 12:29 PM@hendricmartens
Hello,
Thank you for reaching out to us with your concern. I understand that encountering a timeout error (11205) when Twilio attempts to connect to the VAPI servers can be quite frustrating. I will look into this matter for you.
Firstly, I will check our internal systems for any known outages or issues that might be affecting the connectivity. Additionally, I will review the server logs to identify any potential problems that could be causing the network connection failure indicated by the 502 HTTP status.
In the meantime, could you please provide me with any additional information that might help in the investigation? For instance, timestamps of when the issue occurred, or any specific patterns you've noticed could be very helpful.
Rest assured, we are here to help and will do our best to resolve this issue promptly. If it turns out to be a problem on our end, we will work diligently to fix it and keep you updated on our progress.
Thank you for your patience and cooperation.
h
hendricmartens
01/29/2025, 12:39 PMThanks for the quick response. In following is a screenshot of the twillio error containing the timestamp and the debug id. Our organization id is: e8d1087b-14c0-41fb-9fed-50cf3031c49e
https://cdn.discordapp.com/attachments/1334137548162728040/1334140887483023392/Screenshot_2025-01-29_at_13.20.32.png?ex=679b7306&is=679a2186&hm=a46d29112eac3d45bf0d46bd9d1080cc368f48a5db48451eb33680d2dd75c3ff&
s
Shubham Bajaj
01/30/2025, 11:27 AM@hendricmartens Yesterday we had database outage, and Supabase was temporarily unavailable. You may check the status at https://status.supabase.com/. Because of this you experienced timeout issues. We sincerely apologize for any inconvenience this may have caused.
Shubham Bajaj
01/30/2025, 11:28 AM@hendricmartens I suggest try to attempt making calls again, to ensure it's working for you. Do let me know how it goes for you.
Shubham Bajaj
02/03/2025, 5:07 AM@hendricmartens Because of no response closing this ticket.
2 Views