Vapi outage history

We hold 40 Vapi incidents from Vapi's status page, the newest from Nov 21, 2026. 35 of the 40 listed carry Vapi's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 7h 19m since the last recorded problem.
Operational · 24h
78.82%
3 incidents · ≈5h 5m degraded
288 checks
Operational · 7d
96.87%
4 incidents · ≈5h 5m degraded
2015 checks
Operational · 30d
93.29%
7 incidents · ≈1d 23h degraded
8638 checks
Operational · since Jun 22, 2026
95.40%
36 incidents · ≈1h 0m down · ≈6d 4h degraded
41553 checks

% of our checks that found Vapi fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Vapi fails

Since Jun 27, 2026, Vapi's status page has marked 21 Vapi components as impaired, across 2,254 of our five-minute readings. Vapi Dashboard accounts for the most: 631 readings (about 53 hours) on 10 days, 11 of them marked as an outage rather than degraded, most recently on Nov 11, 2026. Next is Vapi API, with 517 readings on 8 days. We hold 40 Vapi incidents from Vapi's status page, the earliest from Apr 11, 2026. Of the 36 that Vapi closed with an end time, the median lasted 29 minutes.

ComponentOutageDegradedMaint.DaysLast
Vapi Dashboard116201910Nov 11, 2026
Vapi API28489528Oct 14, 2026
Vapi SIP24256406Nov 14, 2026
Vapi Numbers Outbound3272134Oct 12, 2026
Vapi Numbers Inbound227283Sep 30, 2026
Deepgram—61—1Nov 18, 2026
SIP Outbound2514495Nov 14, 2026
ElevenLabs—39—1Nov 18, 2026

Incidents by month: May 2026: 1 · Jun 2026: 2 · Aug 2026: 5 · Sep 2026: 8 · Oct 2026: 16 · Nov 2026: 6

Counts are five-minute readings of Vapi's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 6

October 2026 · 16

September 2026 · 8

August 2026 · 5

June 2026 · 2

May 2026 · 1

April 2026 · 2

Incidents and their updates are Vapi's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Vapi.