- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 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 1h 50m it lasted.
Anything that failed between 2026-02-12 17:08 UTC and 2026-02-12 18:58 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 3
- update
We are currently observing that recent call logs are not showing up on the Vapi dashboard since around 7:30am PST. Calls are still being placed. We are actively monitoring the situation and will provide updates as more information becomes available.
provider
- update
We've identified that the issue is related to the ongoing CDC ClickPipes outage (see: https://status.clickhouse.com/incidents/01KH9BE0WY28P4Z48DQ7FPS4DQ).
provider
- resolved
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.
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-3f8f6d5e18
Is Vapi still down?
No, this incident was resolved 2026-02-12 18:58 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
1h 50m, from 2026-02-12 17:08 UTC to 2026-02-12 18:58 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.