Vapi

Affected: Vapi Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. downtime 2026-10-16 14:12 UTC

   Vapi dashboard is currently not loading. We are investigating the incident and affected services.

2. downtime 2026-10-16 14:35 UTC

   We have identified the impact is specific to API on Daily. Call creation is a separate service which is not impacted.

3. degraded 2026-10-16 14:41 UTC

   We've found the root cause and starting to see recovery. Daily API success rate is increasing and dashboard is loading. We will continue to monitor.

4. resolved 2026-10-16 15:01 UTC

   The issue is resolved and all services have returned to normal.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi Docs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with Actions, Pull Requests and Issues.

1. downtime 2026-10-12 17:54 UTC

   Our documentation is unavailable due to an upstream outage, we're tracking status closely ([Fern](https://status.buildwithfern.com/) -> [Vercel](https://www.vercel-status.com/) -> [GitHub](https://www.githubstatus.com/)) and will notify once service is restored

2. resolved 2026-10-12 18:03 UTC

   The issue has been resolved upstream and documentation is available once again, we'll continue monitoring to ensure stability.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi SIP

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. degraded 2026-10-08 18:27 UTC

   We're seeing failures when creating BYO SIP trunks. Existing trunks and calls on them aren't affected. Our team is actively investigating and we'll post an update as soon as we have more information.

2. degraded 2026-10-08 18:57 UTC

   We're continuing to investigate failures when creating BYO SIP trunks. Next update within 30 minutes, or sooner if the status changes.

3. degraded 2026-10-08 20:08 UTC

   Cause Identified: applying a vendor software update to re-enable the functionality. The patch will be deployed during the dedicated maintenance window 21:00–21:15 PT on October 8 (04:00–04:15 UTC on October 9).

4. resolved 2026-10-09 14:47 UTC

   BYO SIP registration has been re-enabled during scheduled maintenanc and we were able to successfully place outbound calls

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi SIP, SIP Outbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. degraded 2026-10-06 21:04 UTC

   Outbound SIP Server downtime from 1:55 to 2:07, impacting outbound calls and call transfers. Currently seeing recovery, and the team is monitoring closely.

2. resolved 2026-10-06 21:29 UTC

   The root cause has been identified, and the issue has been resolved, with downtime experienced between 1:55 and ending at 2:07

3. resolved 2026-10-07 00:09 UTC

   There will be reactive maintenance on SIP outbound dialing infrastructure, US region Status: Scheduled What is affected: Our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing, as part of remediating the root cause of today's incident....

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi SIP, SIP Outbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. downtime 2026-10-02 12:12 UTC

   Calls currently failing for SIP and Vapi member outbound. We are investigating root cause and will update shortly.

2. degraded 2026-10-02 12:23 UTC

   We have identified the root cause of the issue and the services are recovering. We are monitoring and will update shortly.

3. resolved 2026-10-02 12:33 UTC

   The issue has been resolved and calls are completing as expected.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi Numbers Inbound, Vapi Numbers Outbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. degraded 2026-09-29 17:16 UTC

   We're aware of an issue provisioning new Vapi phone numbers - the team is actively looking into it. Calls to existing numbers and importing numbers from other providers are NOT impacted.

2. degraded 2026-09-29 18:55 UTC

   The team has identified the cause and are actively working on a fix. Creating new Vapi phone numbers remains unavailable; while existing numbers and imported numbers are unaffected.

3. degraded 2026-09-29 21:05 UTC

   We are currently working with our upstream provider to restore new number provisioning. Creating new Vapi phone numbers remains unavailable; existing numbers and imported numbers are unaffected. Next update within the hour or as soon as provisioning is restored.

4. degraded 2026-09-29 22:18 UTC

   No change - we are still awaiting confirmation from our upstream provider to restore new number provisioning. Creating new Vapi phone numbers remains unavailable; existing numbers and imported numbers are unaffected. We will post another update as soon as we have news.

5. resolved 2026-09-30 16:01 UTC

   New number provisioning has been restored as of 3:00 AM PT today. Creating Vapi phone numbers is working normally again. Thank you for your patience.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi Auth, Vapi Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. degraded 2026-09-18 23:00 UTC

   Our dashboard login provider's service is degraded. Our API remains functional.

2. resolved 2026-09-18 23:10 UTC

   Our login provider has recovered and the Vapi dashboard is fully operational again.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi Chat

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-13 18:00 UTC

   On Sunday, September 13, 2026, from 8:24 a.m. to 10:55 a.m. Pacific Time, Vapi Chat experienced a service disruption on both daily and weekly channels. During this period, requests to `/session` and `/session/{id}` timed out or returned HTTP 504 (Gateway Timeout) and 500...

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi API, Vapi API [Weekly], Vapi SIP, Vapi Dashboard, SIP Outbound

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. downtime 2026-08-19 18:16 UTC

   We're seeing an increased rate of call failures and the team is actively investigating

2. downtime 2026-08-19 18:36 UTC

   We are confirming that calls are not connecting in the US. Our team is still investigating. Next update in 30 min or sooner.

3. downtime 2026-08-19 19:01 UTC

   Calls are still failing to connect. Our team has a working hypothesis and we will post as soon as we can confirm the root cause. Next update will be in 30 min or earlier.

4. degraded 2026-08-19 19:26 UTC

   We have rolled out a mitigation measure and are seeing improvements in call success rate.

5. degraded 2026-08-19 19:55 UTC

   Some customers are reporting concurrency limits issues. We are resetting all limits to zero for all subscriptions. This change will propagate over the next few minutes.

6. degraded 2026-08-19 20:02 UTC

   We are seeing recovery on all affected services and have moved to monitoring status.

7. resolved 2026-08-19 20:19 UTC

   The incident is resolved.

8. resolved 2026-08-20 17:20 UTC

   Incident Report available at https://drive.google.com/file/d/1ORxSZb8NYgVlmPoqnUEdTmlIua3NSl_k/view

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-12 11:50 UTC

   We are investigating an issue affecting webhook behavior for a subset of web calls. Calls using private credentials and dashboard call flows are unaffected. We are deploying a fix and will provide another update once validation is complete.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi Docs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. downtime 2026-08-05 19:55 UTC

   Our documentation hosting provider is currently experiencing an issue which is impacting the availability of Vapi documentation and MCP server. In the meantime you may directly view our documentation repo here: https://github.com/VapiAI/docs At this time there is no evidence of...

2. resolved 2026-08-05 20:30 UTC

   Our documentation vendor has resolved their issue and Vapi documentation is now fully available.

Excerpts are shortened. Read the full incident on Vapi's status page.

Affected: Vapi API, Vapi Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. degraded 2026-08-04 19:41 UTC

   We are experiencing API Degradation on the daily channel. The team is actively investigating.

2. degraded 2026-08-04 19:52 UTC

   We are currently seeing recovery, we are actively monitoring the issue and will provide updates within the next 20 minutes.

3. resolved 2026-08-04 20:20 UTC

   We have identified the root cause of this issue and implemented a fix. We've seen a full recovery across our systems and are continuing to monitor for any regressions.

Excerpts are shortened. Read the full incident on Vapi's status page.