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.

Google is still resolving capacity issues on their end, but we have put a mitigation in place to resolve this for gemini-2.5-flash. Please switch to this model when using Google, if you require another model reach out to support@vapi.ai.

We are continuing to monitor and work with the Google team to resolve.

We have pushed a fix and this issue should be resolved. The team will continue to monitor.

We experienced a temporary increase in call connection errors caused by worker unavailability. The issue has since been resolved. Impact was limited to the daily channel; the weekly channel was not affected.

We are seeing decreased success rate in calls on the daily channel. The team is investigating and we will post updates here.