Vapi Outage History

Vapi experienced degraded performance affecting a subset of inbound calls for 2.1 hours. The service disruption was classified as minor and impacted call quality for some users. The incident has been resolved after investigation and remediation by the technical team.

Vapi experienced a major SIP infrastructure outage lasting 1.3 hours that caused in-call failures including problems with call transfers and increased latency. The degradation affected the core calling functionality of the service. The technical team actively investigated and resolved the infrastructure issues.

Vapi experienced elevated error rates with the Soniox transcriber service, causing affected calls to terminate unexpectedly with transcriber failure errors. The incident was classified as minor and lasted 6.1 hours before being resolved.

Vapi experienced elevated call failure rates for 5.2 hours, classified as a minor incident. The service disruption affected call connectivity and reliability during this period. The team actively investigated and resolved the issue.

Vapi experienced elevated call failure rates on their weekly cluster, causing increased errors in daily and weekly channels. The service disruption lasted 1.4 hours while the team actively investigated and resolved the issue.

Vapi experienced degraded performance affecting calls and dashboard functionality. The issue was identified and mitigated at 8:22 AM, restoring normal service operations. The incident lasted approximately 158.5 hours and has been resolved with continued monitoring in place.

A small percentage of calls using GPT 5.2 on Vapi experienced failures due to internal inference errors from OpenAI's side. The issue affected only the GPT 5.2 model while other models remained functional. The incident lasted 222 hours with users advised to switch to alternative models during the outage period.

Vapi experienced call degradation issues specifically affecting the Daily channel for 20 minutes. The service disruption impacted call quality for users on that channel. The incident was monitored and resolved as a minor service issue.

Vapi's "Emma" voice experienced service issues that prevented calls from functioning properly with this specific voice option. The incident affected users who had configured their calls to use the "Emma" voice, potentially causing call failures. The issue was resolved after 13.8 hours, with Vapi recommending users switch to alternative voices and implement voice fallbacks during the outage.

Vapi experienced degraded call quality on the Daily channel, with calls being dropped due to worker process failures (error: "call.in-progress.error-vapifault-worker-died"). The incident lasted approximately 5 days while the team investigated and resolved the underlying worker stability issues.