Hi Vapi team, We're experiencing widespread inbound call failures across multiple error types. Below is a sample of call IDs from the last 12 hours alone - the actual volume of failures is significantly higher: `vapifault-worker-not-available`: -

019c959f-beaa-7eef-845d-36616d4570d0

-

019c9624-edcd-7ddf-b81b-b2c5f311a423

-

019c95a0-1e16-7cc7-9c43-abb0e063dcb5

-

019c959f-d060-7ffb-8c56-f7040eb4b29c

-

019c959f-bf18-7aae-9282-622573fa4b19

-

019c959f-4051-788c-a936-b98ddb335cd4

-

019c959f-3d21-7440-bf77-0e984a6861e6

`vapifault-worker-died`: -

019c96a9-879e-7005-867a-e94ef08089ca

-

019c9592-ecaf-7ee0-8502-98959fc9d586

-

019c955a-d88d-7ee0-84b6-b6e63e814d57

-

019c9558-8bcf-7cca-980e-7a827872a583

`vapifault-transport-never-connected`: -

019c966c-37ba-7996-9ca0-8851d531cb54

`caller-hungup-before-call-connect`: -

019c955d-6d63-7aae-921f-a6281add8436

sip-completed-call

(successful call for reference): -

019c955b-2a52-7bbb-bd05-55bde822b611

Key details: - Call type: Inbound only - The above 13 call IDs are just a sample from the past ~12 hours. The total number of failures is much higher and ongoing. - The vast majority are worker-related infrastructure failures (

worker-not-available

+

worker-died

) - The

caller-hungup-before-connect

errors appear to be a downstream effect of slow worker availability causing long connect times cc @Vapi

Thank you for sharing these detailed call IDs and error types. I understand how critical and urgent these widespread inbound call failures are, especially given the high volume and the impact on your production environment. Your breakdown of the error types and the observation about worker-related infrastructure issues and downstream effects is very clear and helpful. At this time, I do not have additional information to provide regarding the root cause or resolution steps. If there are any updates or further details available, I will share them as soon as possible.

Please refer to: [https://status.vapi.ai/incident/833083](https://status.vapi.ai/incident/833083). This should be resolved now.

Hey @Shaunak thank you for your quick response. Will monitor this and get back to you in case we still face this issue. Thank you!

The worker-not-available and worker-died errors indicate worker capacity or stability issues on the inbound call infrastructure. The transport-never-connected and caller-hungup-before-call-connect errors are likely downstream effects caused by delayed worker assignment.

Do you use any type of active monitoring against your bots setup? Or it's just the Christmas tree directly on your reported monitoring prod dashboard all client facing?