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.