I have tried calling with Deepgram Nova 3, Speechmatics Enhanced and Azure and all of them fails. Calls ID: 019b2908-152a-7551-8367-75084c5ac310 019b2907-a3de-7dd2-ad7c-1e1b9996a3f7 019b2900-09e7-7ff2-be24-608bbc98ffaa

Action Step: Go to your [Vapi dashboard](https://dashboard.vapi.ai/), navigate to

Observe > Call Logs

, and enter one of your Call IDs to review the call transcript and error details. This will help pinpoint where the STT process is failing and provide specific error messages for further troubleshooting. Tip: Check the provider status pages if you see errors related to service outages. More details: [Vapi Debugging Guide](https://docs.vapi.ai/debugging) Source: - [Vapi Debugging Guide](https://docs.vapi.ai/debugging)

I already provided this. Please, check it out because it is happening even on the weekly cluster

@Geremayaa did it getting resolved, even we are facing the same issue

Nop, it is still failing

sad, I don't know why no one is even looking into such a major issue

We noticed you have API keys for all three of those providers and it could be failing on your keys specifically. To test it, remove your deepgram API key then run a test call.

callID: 019b3596-149f-7cce-851c-e1d32fa7eb0b, can you look into this @Kyle ? we are using vapi itself w/o API Keys for internal transcriber. still all the transcriptions are half made

And why may be them failing in different providers at the same time? This must be something on vapi side right?