Incident Report providerfault-transport-never-conn...
# support
j
At approximately 18:10 (UTC+2), we began experiencing a significant issue affecting call operations. Ongoing calls began dropping unexpectedly, triggering call.in-progress.error-providerfault-transport-never-connected errors on our side. Simultaneously, we observed a surge in warning logs originating from our systems. Upon investigation with our telephony provider and according to our logs and webhook traces from VAPI, the calls were not being picked up and failed to be transferred correctly. All test calls initiated during the incident window were cut off mid-call. We have verified that no configuration changes were made on our side. The VAPI integration is currently operating under a static weekly configuration, which remained unchanged during the incident. Service stability resumed around 18:25 (UTC+2), marking a total disruption period of approximately 15 minutes. This incident caused a temporary service degradation without any failover or fallback taking effect.
v
Thank you for sharing this detailed incident report. It sounds like you experienced a significant disruption in call operations, with calls dropping and specific errors occurring over a 15-minute period. It's helpful to know that your configuration remained unchanged and that service stability was restored after the incident window. If you have any further updates or need to share more details, feel free to do so.
s
@jb can you share the call_ids?
j
61dd4ab5-dbd9-412b-bcf0-261a055e6ccc
s
do you have more call_ids?
j
yes
b4d7fecc-a9ed-4b83-b0f4-2b94fcf6ef0a
s
🟢 16:14:16:934 Call b4d7fecc-a9ed-4b83-b0f4-2b94fcf6ef0a Done. (call.in-progress.error-providerfault-transport-never-connected) 🟡 16:14:12:738 Live Call Manager Ending With Error...(call.in-progress.error-providerfault-transport-never-connected) After initiating the call, we wait for X number of seconds for your telephony to connect with us or respond to initiate the call, but they didn't connect in the required time, which is why these calls ended up like this. So you have to check with your telephony. https://cdn.discordapp.com/attachments/1372254842122272923/1372263588038967376/image.png?ex=6826238e&is=6824d20e&hm=c93f7aa399f2ed1281a48b218553d1d986509c8e0ee162e1b815657ce970f7d1&
j
Okay, thank you very much for the investigation. I’ll double-check with them. Thanks again!