Calls are degraded on Daily channel

What to do

• Check whether your product depends on Vapi. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10h 32m it lasted.

  Anything that failed between 2026-02-25 15:27 UTC and 2026-02-26 01:59 UTC may need a replay.

• Subscribe to Vapi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vapi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vapi 5

1. updateFeb 25, 2026, 3:27 PM UTC

   We are seeing calls being dropped on the Daily channel with ended reason "call.in-progress.error-vapifault-worker-died". The team is looking into it and will update here.

   provider

2. updateFeb 25, 2026, 4:33 PM UTC

   We have identified the root cause. We did see the issue spike up again during investigation. The team is working on a fix and will update here. In the meantime we suggest customers switch to the Weekly channel for more stability.

   provider

3. updateFeb 25, 2026, 4:56 PM UTC

   The issue is resolved, the team is monitoring and continuing to work on a fix for the recurrent issue.

   provider

4. updateFeb 25, 2026, 7:12 PM UTC

   We are seeing intermittent failures related to the earlier incident, slightly higher than normal amounts. The team is investigating and will share additional updates here. Degradation is still limited to `daily` channel. If you are seeing instability we suggest switching to the `weekly` channel (in Organization Settings → Channel).

   provider

5. resolvedFeb 26, 2026, 1:59 AM UTC

   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 reliability detected on the Daily channel. Status page updated and investigation begins immediately. **8:33 AM** — Issue escalated. Team recommends affected customers switch to the Weekly channel while investigation continues. Status page updated. **9:04 AM** — Team begins proactive outreach to guide affected customers to the Weekly channel. **10:55 AM** — Additional call failures observed on Daily after a brief period of stability. Investigation continues. **11:00 AM** — Rolled back previous deployment. Did not observe any significant improvement. **1:30 PM** — Continued investigating the issue. **3:59 PM** — No further issues observed. **6:00 PM** — Released a fix to improve stability in the Daily channel. Incident resolved. ## What Went Well - The issue was detected and acknowledged quickly. - A dedicated incident response was organized promptly to focus investigation. - Teams were notified early and guided affected customers to switch to the Weekly channel. ## Action Items - Isolate background operations from call handling - Strengthen deployment validation - Improve resilience under load - Expand monitoring and alerting ## Note This report is intended as a summary of the incident timeline, impact, and immediate action items. A deeper root cause analysis is available upon request. This issue impacted the Daily channel only. Customers desiring increased stability (at the cost of delayed access to features) can switch to the Weekly channel by navigating to **Organization Settings** on the Vapi Dashboard and changing the Channel to **"weekly"**.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.