- Level
- confirmed
- Worst impact
- Degraded
- Regions
- in
What to do
Check whether you use Vapi in in. 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 1d 22h it lasted.
Anything that failed between 2026-02-24 18:33 UTC and 2026-02-26 17:08 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 2
- update
Our auth service provider is reporting a degradation specifically in India. Some customers in that region will see issues with login. See our providers status page for live updates: https://status.supabase.com/incidents/xmgq69x4brfk.
provider
- resolved
Our provider has confirmed the issue is specific to accessing projects and seems to not include authentication. They are still resolving the issue from their end, but we are marking the issue as resolved. If customers continue to see issues with authentication, please reach out to support@vapi.ai
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-b812c6e682
Is Vapi still down?
No, this incident was resolved 2026-02-26 17:08 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
1d 22h, from 2026-02-24 18:33 UTC to 2026-02-26 17:08 UTC, by the times Vapi posted.
What was affected?
Vapi named in in.
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.