Error inbound call vapifault-transport-never-conne...
# support
s
When I try to call my VAPI assistant, the call gets answered, but the AI doesn’t say anything, and the call ends. In the call logs, the ended reason is vapifault-transport-never-connected. Could you help me troubleshoot this? Callids be703d44-ff89-47a0-b29e-e1b0b92d35b9 067375ab-e2b0-4933-ab0b-2caad307c5ea 4f524251-2fdf-4b0b-bf72-5471027911c7 e2937885-082d-45f7-a6ad-690023ec1e2b 7125cd2a-9061-4133-afa8-7ab24613d6cb
f
+1
c
Was just about to post the same, getting vapifault-transport-never-connected error on all calls on different accounts. Service is down.
l
Same
I am the only one that when I create a new assistant it works for a couple of calls and then gets this error ?
c
For us we are seeing the error on about 95% of calls, one of us managed to get through, but right now all calls around seeing the same error
s
@Vapi @Vapi Support Bot @Vapi Incident @Shubham Bajaj
c
Looks like its been acknowledged - https://status.vapi.ai/incident/525770?mp=true
s
My web calls are working but just after about 20 sec after hitting 'talk with assistant' button
a
Same for us
10+ calls missed. ee222b68-d7ed-4420-9c85-76528f834111 in case VAPI needs more examples
s
Is this Twilio specific and/or is there estimated time for mitigation? How can I subscribe to status updates
c
For me it's working well now. Will continue to test
s
Same here. 🙏
s
Hey @Syegi @Chris @Sooz @Achal @Loler2006 @flake9, can you guys try now the issue has been resolved