Incident Report: Database Outage (Log Collector Misconfiguration)

What Happened

Vapi experienced a large service outage causing voice calls to fail and the dashboard to become unavailable. This was caused by a failure in an audit log collector in the Vapi production database. The triggering event was an apply_config that our database provider executed at 6:44 AM PST. A misconfiguration in the project-wide telemetry settings caused Postgres processes to become stuck writing to syslog ...

The incident has been resolved and platform functionality has been fully restored. We will continue monitoring and will publish additional details if necessary.

We have noticed a higher-than-usual rate of tool calls in the daily cluster and are currently investigating the issue.

This incident has been resolved. All systems are operating normally

Chat assistants on the weekly update channel were returning empty responses after tool calls, causing conversations to stall or end unexpectedly.

We have rolled back the weekly update channel to a stable version for now to mitigate this.

Note: It impacts only chat endpoints.

Our documentation provider is experiencing an outage. We’re in touch with the team and will provide communication when services are back up

We have now resolved this incident. Between ~7:30AM PT and ~9:30AM PT, a new query pattern caused database slowness that increased API latency and led to dropped inbound calls with certain providers. We mitigated by rolling back the deployment and are following up with a deeper review of the query change.

The issue has been resolved. After applying the remediation, we monitored the affected systems and confirmed stable operation. All services are functioning normally.

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