- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 100
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 1d 6h it lasted.
Anything that failed between 2026-03-19 23:17 UTC and 2026-03-21 05:46 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 6
- update
We're seeing elevated call failures on weekly, and the team is actively looking into it.
provider
- update
We're seeing improved call success rates, but we're still monitoring the situation.
provider
- update
The immediate mitigation we deployed is working and we are seeing call success rates continuing to recover. We are still investigating root cause and closely monitoring service performance.
provider
- update
Our earlier mitigation is working and services have been stable since 4:50 PM. We have identified a potential root cause and are working on a permanent fix. We will share further updates once we deploy and validate the fix.
provider
- update
The incident has been resolved and services have been stable since 4:50pm PT. We will continue monitoring and will publish additional details if necessary.
provider
- resolved
**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. **12:25 PM** We identified the trigger as an unanticipated surge in call volume that exceeded our provisioned cluster capacity and downstream rate limits with a model provider. **12:30 PM** We applied traffic controls and began working with the model provider to increase capacity. Call failures began declining. **1:40 PM** Call success rates returned to normal and held stable. First incident window closed. **~4:00 PM** A separate traffic spike re-triggered infrastructure constraints, leading to elevated failures. We began investigating immediately. **4:00 PM to 4:40 PM** We rebalanced traffic and migrated affected workloads to dedicated infrastructure to restore headroom on shared clusters. **4:50 PM** All mitigations took effect. Call success rates returned to normal. **4:50 PM to 8:10 PM** We continued active monitoring. No further failures observed. **8:10 PM** Second incident window closed. **Immediate Action Items:** Improve workload isolation and per-account capacity guardrails to prevent resource contention from cascading across the platform. **Note:** A full root cause analysis is underway and will be available upon request. We sincerely apologize for the disruption and thank you for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ce9e0c831d
Is Vapi still down?
No, this incident was resolved 2026-03-21 05:46 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
1d 6h, from 2026-03-19 23:17 UTC to 2026-03-21 05:46 UTC, by the times Vapi posted.
What caused it?
Vapi hasn't published a root cause. If it does, it shows here.
Where does this come from?
Vapi's official status page, https://status.vapi.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.