DownForAI

Vapi status: API, auth, latency & outage reports

Vapi is operational right now. DownForAI checks Vapi every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 37 min ago·1 surface
Probe-monitoredLow confidence
📚 Docs →💳 Pricing →
100.0%
24h Uptime
145ms
p50 Network Latency
326ms
p95 Network Latency
0
Incidents (30d)

DownForAI monitors Vapi via a single endpoint — Vapi Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 145 ms; p95: 326 ms.

DownForAI has not recorded any Vapi agent runtime disruptions. The service is probed approximately every 75 minutes; no user reports have been received in the last 24 hours.

Data confidence: LowLast checked 37 min ago · 1 monitored surface · 1 with 24 h latency data

Current Status

Operational
Everything works normally
Checked by our probes · 163ms
Verified 36m ago
No major incident reported
No reports in the last 24h

Having issues?

Help other users by reporting if Vapi is not working for you.

0reports in the last 24 hours

Surface Health

Vapi WebOperational
HTTP 200p50 145ms36m ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Vapi

No confirmed provider-side issue detected
DownForAI currently sees Vapi as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Vapi in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Vapi is a developer platform for voice AI agents (phone and web calls) that orchestrates speech-to-text, LLM and text-to-speech providers, on usage-based plans, with its own status page. Incidents show as calls failing to connect, latency, or a specific provider failing inside calls.

What we monitor
Vapi API and dashboardAssistants and calls
Call pipelineTelephony, STT, LLM, TTS
Provider integrationsDeepgram, OpenAI, ElevenLabs and others
Ecosystem dependencies
Telephony carriersDeepgram, OpenAI, ElevenLabs and other providers
Operator notes
  • Vapi has its own status page; DownForAI probes vapi.ai only.

Fallback alternatives

What to use if this service is down

Vapi is down
Bland AI or Hume AI (monitored on DownForAI) run voice agents
Major migration

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Vapi statusEmbed this status badgeREADME · docs ▾
Markdown
[![Vapi status](https://downforai.com/api/badge/vapi-ai.svg)](https://downforai.com/vapi-ai)
HTML
<a href="https://downforai.com/vapi-ai"><img src="https://downforai.com/api/badge/vapi-ai.svg" alt="Vapi status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Vapi?

Let the community know and help others experiencing the same problem.