We are currently observing elevated error rates affecting calls that use the Soniox transcriber. Impacted calls may terminate unexpectedly with the ended reason call.in-progress.error-vapifault-soniox-transcriber-failed.

While we work to resolve this, we recommend switching to an alternative transcriber or configuring a transcriber fallback plan to ensure call continuity. You can set up fallbacks by following the guide here: https://docs.vapi.ai/customization/transcriber-fallback-plan

We ar...

We observed an elevated rate of API errors from 1:28pm to 1:39pm PDT. The errors have since resolved. We are closely monitoring API performance and investigating the root cause.

Incident Report, March 19, 2026

Impact: A service disruption affected inbound and outbound call reliability on the Daily and Weekly channel. Some calls failed to connect with transport-never-connected, worker-not-available, worker-died, and deepgram-transcriber-failed end reasons.

Timeline (all times PDT):

12:20 PM We detected elevated call failure rates on the Weekly production cluster.

12:22 PM We published a status page incident and began investigating.

**1...

Resolved — The issue causing degraded performance has been identified and mitigated as of 13:45 PDT. All services are operating normally. We will continue to monitor and provide an update if needed.

Resolved — The issue causing degraded performance has been identified and mitigated as of 8:22 AM. All services are operating normally. We will continue to monitor and provide an update if needed.

The issue has been resolved we're not seeing any further degradation

The issue has been resolved and all systems are operational.

The issue has been resolved and the voice is currently usable. We still recommend setting up fallbacks for any voices for the future to avoid call drops -
https://docs.vapi.ai/voice-fallback-plan

We have not seen the issue since ~3:50pm today. We have determined the root cause and are rolling out a fix to improve stability in the daily channel.

Incident Report — Daily Channel Call Failures (February 25, 2026)

Impact

Between 7:27 AM – 3:59 PM PST, approximately 19,527 calls failed on the Daily channel due to call worker failures.

All Daily channel users were impacted. The Weekly channel was not affected.

Timeline (all times in PST)

7:27 AM — Degraded call reliabilit...

Our provider has confirmed the issue is specific to accessing projects and seems to not include authentication. They are still resolving the issue from their end, but we are marking the issue as resolved.

If customers continue to see issues with authentication, please reach out to support@vapi.ai

Incident report:

Impact:

A service disruption affected call reliability on the Weekly channel. Some calls ended unexpectedly with worker-not-available or worker-died end reasons.

Timeline (all times PT):

• 8:07 AM - We detected a burst of call failures across the platform.
• 8:16 AM - Automated monitoring alert fired. We acknowledged and began investigating.
• 8:42 AM - We scoped the impact across affected accounts.
• 8:47 AM - The issue self-resolved. We ident...

The issue is resolved as of 10:05am PST.

Incident Report

Impact

Between 9:10–10:05 AM, 37,806 calls were dropped due to call worker failures. All Daily users were impacted.

Timeline (all times in PST)

9:02 AM — On-call engineer notices pods crashing in the Daily cluster.
9:11 AM — Black box probe alert fires; acknowledged by on-call engineer, triggering investigation.
9:27 AM — Issue escalates to the point of impacting all calls on Daily.
9:30 AM — Status page created to inform ...

Email authentication for the Vapi dashboard has been restored. Users should now be able to sign in normally using their email credentials.

The CDC ClickPipes issue was resolved, and we've confirmed calls made during and after the outage are now appearing in the Vapi dashboard. This issue has now been resolved.

Deepgram had an issue while upgrading their system, which caused 429 errors. They've fixed it and are implementing controls to prevent recurrence.

Errors have decreased and the incident has been resolved. We'll post an RCA soon.