Incidents reported on status page for Vapi https://status.vapi.ai/ en https://status.vapi.ai/incident/994732 Thu, 06 Aug 2026 04:00:06 -0000 https://status.vapi.ai/incident/994732#430f2c806ee265270ae2947de626660b21c71bcd7ff08cc514eed09088c68635 We're upgrading our authentication database as part of ongoing reliability work on the Vapi platform. **What to expect** • Most of this window is prep and verification. The part customers actually notice should only last a few minutes. • During those few minutes, requests that create or change account-level resources may briefly fail. That includes starting new calls and making organization or subscription changes. • Signing in, API key authentication, and read requests are not affected and will keep working throughout. • Calls already in progress won't be interrupted. • Any request that fails is safe to retry. Standard client retries will go through once the window closes. • No data will be lost, and there's nothing you need to do. We'll post updates here as the work progresses. If you run into any issues after the window closes, email us at support@vapi.ai. https://status.vapi.ai/incident/996148 Tue, 04 Aug 2026 20:20:00 -0000 https://status.vapi.ai/incident/996148#c71159722eab5256985975070d4e0ee5073520d868038410dba99e552ca8e259 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. https://status.vapi.ai/ Tue, 04 Aug 2026 20:00:10 +0000 https://status.vapi.ai/#ad0388067913da97d277b7ef1b4128d9eef35145957f6b4a2c81772baf1c9e2d Vonage Outbound recovered https://status.vapi.ai/incident/996148 Tue, 04 Aug 2026 19:52:00 -0000 https://status.vapi.ai/incident/996148#8037d4786f1bd3f4c1ef197a41406eb75ff5de6c422d444712c561c42572c3e8 We are currently seeing recovery, we are actively monitoring the issue and will provide updates within the next 20 minutes. https://status.vapi.ai/ Tue, 04 Aug 2026 19:49:57 +0000 https://status.vapi.ai/#5440e93b84f1a4da03dd9ae5d488c5b818de39e8aa686d4b9d88e3588d645fbe Telnyx Inbound recovered https://status.vapi.ai/ Tue, 04 Aug 2026 19:49:48 +0000 https://status.vapi.ai/#3cc419efeae81b9d22e0c11aa1bf2089e127c564651bed85211b06319415759d Telnyx Outbound recovered https://status.vapi.ai/ Tue, 04 Aug 2026 19:46:46 +0000 https://status.vapi.ai/#9d5a9c9216630e8838c0ee93906873af93d1fef863e0098b01269895525bff34 Vapi Numbers Outbound recovered https://status.vapi.ai/ Tue, 04 Aug 2026 19:43:17 +0000 https://status.vapi.ai/#3a3e4ad9bf789dd14fb408a928288acfb9955d0d071532b3216a27f4ce4d7712 Vapi API recovered https://status.vapi.ai/incident/996148 Tue, 04 Aug 2026 19:41:00 -0000 https://status.vapi.ai/incident/996148#a9159aa197a1a0a9d0f7cb70a1a7e41e55df0071504ed3bbfa54ae14cbddd1fb We are experiencing API Degradation on the daily channel. The team is actively investigating. https://status.vapi.ai/ Tue, 04 Aug 2026 19:40:16 +0000 https://status.vapi.ai/#ad0388067913da97d277b7ef1b4128d9eef35145957f6b4a2c81772baf1c9e2d Vonage Outbound went down https://status.vapi.ai/ Tue, 04 Aug 2026 19:40:04 +0000 https://status.vapi.ai/#5440e93b84f1a4da03dd9ae5d488c5b818de39e8aa686d4b9d88e3588d645fbe Telnyx Inbound went down https://status.vapi.ai/ Tue, 04 Aug 2026 19:38:18 +0000 https://status.vapi.ai/#9d5a9c9216630e8838c0ee93906873af93d1fef863e0098b01269895525bff34 Vapi Numbers Outbound went down https://status.vapi.ai/ Tue, 04 Aug 2026 19:32:30 +0000 https://status.vapi.ai/#3a3e4ad9bf789dd14fb408a928288acfb9955d0d071532b3216a27f4ce4d7712 Vapi API went down https://status.vapi.ai/ Tue, 04 Aug 2026 19:30:18 +0000 https://status.vapi.ai/#3cc419efeae81b9d22e0c11aa1bf2089e127c564651bed85211b06319415759d Telnyx Outbound went down https://status.vapi.ai/ Sat, 01 Aug 2026 01:44:40 +0000 https://status.vapi.ai/#a6293707d4a00ea9af2df936d3ecb753a65630741c758c52001b8bf59641933d Cartesia recovered https://status.vapi.ai/ Sat, 01 Aug 2026 01:29:54 +0000 https://status.vapi.ai/#a6293707d4a00ea9af2df936d3ecb753a65630741c758c52001b8bf59641933d Cartesia went down https://status.vapi.ai/incident/973555 Mon, 27 Jul 2026 05:00:00 -0000 https://status.vapi.ai/incident/973555#e152ed5c063535bf2a1a67ba0c96be9934efe697228ae98d98891858b88b9b0e We will be performing a patch update on our SIP server. This maintenance requires a brief server restart and will be carried out during a low-traffic period to minimize any impact. We do not anticipate any significant disruption, and service will resume immediately after the restart. https://status.vapi.ai/incident/976712 Fri, 24 Jul 2026 11:44:00 -0000 https://status.vapi.ai/incident/976712#bdb5a5e45a4cfeade69c93b8ba758305fbf1b7c2342b1e48b51c6f189a6559b8 Between 10:55 and 11:10 UTC, some API requests and calls failed due to a network performance issue at our upstream network provider affecting US west. EU and Australia regions were not impacted. Service recovered at 11:10 UTC. No action is required. We're continuing to monitor. https://status.vapi.ai/ Fri, 24 Jul 2026 11:18:45 +0000 https://status.vapi.ai/#eec5805fbfeb7cf4f3f7ca777375ca15c820da4e7cff97d35fd9d01ccdb65c23 SIP Inbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:15:24 +0000 https://status.vapi.ai/#b708f1aa9ae4726996843805e5deed08bdac9e4d3a5b45590ef17a1c400d1031 Vapi Numbers Inbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:12:39 +0000 https://status.vapi.ai/#b970d9055d078d147351e75203af6f13c91e0703aea6f0037ae0643f477475bc SIP Outbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:12:30 +0000 https://status.vapi.ai/#73b4a99545a107a0d88a2fc38ed3d92376cedf42f35bd3a9ce16c5afa9a2acff Vonage Outbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:12:27 +0000 https://status.vapi.ai/#13d3621a4dbb980a4f3587184467ddeb20f5f95d5bdb0933abcd283585855b72 Vonage Inbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:12:12 +0000 https://status.vapi.ai/#efd5d5a54a3307beb9949fa9035f8096bdafca260f156bcb98fba13c95f4f3a3 Twilio Inbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:11:51 +0000 https://status.vapi.ai/#d6cafbb4ed89bd6fa72d614c319ed72e8d4f15acde1fc96c03fd16cfac5febfa Vapi Call Logs recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:11:25 +0000 https://status.vapi.ai/#f1d7af65835b7018360b57a51db4e41cb7d8863a1bd818f83b2f8e8bd131bfe6 Vapi API recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:11:23 +0000 https://status.vapi.ai/#59d5eea749994bd78bd33546e15cf2435d8dcf3ae379beacd49ae97776f193e1 Telnyx Outbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:11:11 +0000 https://status.vapi.ai/#287489cc0b0561b38ea33a1c7d88034ed6e0d1bad46f577d7f9501f3aee3f457 Telnyx Inbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:11:10 +0000 https://status.vapi.ai/#357389435af449f0ae410daae07144beeeb1dd83a34159b3241a73bdd02aa94e Twilio Outbound recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:10:57 +0000 https://status.vapi.ai/#df02f06b5731999748ce7c68ea214a08c90b046df6f173fd1d6db268c83e4833 Vapi SIP recovered https://status.vapi.ai/ Fri, 24 Jul 2026 11:07:50 +0000 https://status.vapi.ai/#b708f1aa9ae4726996843805e5deed08bdac9e4d3a5b45590ef17a1c400d1031 Vapi Numbers Inbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:58 +0000 https://status.vapi.ai/#d6cafbb4ed89bd6fa72d614c319ed72e8d4f15acde1fc96c03fd16cfac5febfa Vapi Call Logs went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:56 +0000 https://status.vapi.ai/#73b4a99545a107a0d88a2fc38ed3d92376cedf42f35bd3a9ce16c5afa9a2acff Vonage Outbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:22 +0000 https://status.vapi.ai/#13d3621a4dbb980a4f3587184467ddeb20f5f95d5bdb0933abcd283585855b72 Vonage Inbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:10 +0000 https://status.vapi.ai/#59d5eea749994bd78bd33546e15cf2435d8dcf3ae379beacd49ae97776f193e1 Telnyx Outbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:00 +0000 https://status.vapi.ai/#357389435af449f0ae410daae07144beeeb1dd83a34159b3241a73bdd02aa94e Twilio Outbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:04:00 +0000 https://status.vapi.ai/#287489cc0b0561b38ea33a1c7d88034ed6e0d1bad46f577d7f9501f3aee3f457 Telnyx Inbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:03:43 +0000 https://status.vapi.ai/#efd5d5a54a3307beb9949fa9035f8096bdafca260f156bcb98fba13c95f4f3a3 Twilio Inbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:02:53 +0000 https://status.vapi.ai/#b970d9055d078d147351e75203af6f13c91e0703aea6f0037ae0643f477475bc SIP Outbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:01:24 +0000 https://status.vapi.ai/#eec5805fbfeb7cf4f3f7ca777375ca15c820da4e7cff97d35fd9d01ccdb65c23 SIP Inbound went down https://status.vapi.ai/ Fri, 24 Jul 2026 11:00:59 +0000 https://status.vapi.ai/#df02f06b5731999748ce7c68ea214a08c90b046df6f173fd1d6db268c83e4833 Vapi SIP went down https://status.vapi.ai/ Fri, 24 Jul 2026 10:59:48 +0000 https://status.vapi.ai/#f1d7af65835b7018360b57a51db4e41cb7d8863a1bd818f83b2f8e8bd131bfe6 Vapi API went down https://status.vapi.ai/incident/965921 Thu, 16 Jul 2026 10:17:00 -0000 https://status.vapi.ai/incident/965921#8c88280b148ed0e3cc0995d8e66a61dc27dcae88dc6f04e538d26ac87b2b48cf We have engaged our fallback authentication provider restoring access back to the Vapi Dashboard. We will continue to monitor but at this time, we are observing no further issues. https://status.vapi.ai/incident/965921 Thu, 16 Jul 2026 10:00:00 -0000 https://status.vapi.ai/incident/965921#380185847d9fc68510e359877edff0383b7442ffe724b71c433c86205abd2bb4 We observed an increase in Dashboard Access degradation due to an outage with our downstream authentication provider. We are investigating the root cause and actively monitoring. https://status.vapi.ai/incident/947546 Wed, 08 Jul 2026 20:59:00 -0000 https://status.vapi.ai/incident/947546#594e87eb10534a0f11f3dd0328e973fb3f397426e7b9a572d10742f9c6caa682 We have identified the root cause of this issue and successfully implemented a fix. We will continue to monitor but at this time are observing no further issue. https://status.vapi.ai/incident/947546 Wed, 08 Jul 2026 20:22:00 -0000 https://status.vapi.ai/incident/947546#af8eb295b9e13204bc00d52a78211eb98e0f765dc777010350a4e63874c390ad We observed an increase in API error rates between 12:30 and 1PM PT. Service recovered after 1PM PT. We are investigating the root cause and actively monitoring API health. https://status.vapi.ai/incident/945421 Tue, 07 Jul 2026 07:06:00 -0000 https://status.vapi.ai/incident/945421#8e3744c18c30744e913335268b5020be5530a7ac04c5bd941a0a73d0cbcdadc7 We performed critical maintenance on our analytics service, during which the Analytics charts and Insights (Boards) in the Vapi Dashboard were temporarily unavailable or returned errors. Voice calls, call handling, and all APIs operated normally throughout, with no impact to your account settings or call data. The affected features are now fully restored and we're actively monitoring. We apologize for the disruption. https://status.vapi.ai/incident/945421 Tue, 07 Jul 2026 02:54:00 -0000 https://status.vapi.ai/incident/945421#5c25f2034b554db8ea07f3e6eddc1383f23d98aa2dd9dcd2e51abd880fcb7871 We are deploying a fix into production. We will provide a final update once the fix is merged and the issue has been resolved. https://status.vapi.ai/incident/945421 Tue, 07 Jul 2026 02:01:00 -0000 https://status.vapi.ai/incident/945421#ad6e244b4930277e6e6cc88cf8fddd4cd476f726f4543fe2187d4b71da8bc559 We are continuing to deploy a fix for the degraded performance affecting Boards. We will provide our next update by 7:45 PM PT. https://status.vapi.ai/incident/945421 Tue, 07 Jul 2026 01:14:00 -0000 https://status.vapi.ai/incident/945421#592b9c07a32cfecb01e5d4e6e4bfa8eaa304e821b1f54c2a2021a91d9247852a We have identified the root cause of the issue and are actively deploying a fix to restore normal performance to boards. https://status.vapi.ai/incident/945421 Tue, 07 Jul 2026 00:30:00 -0000 https://status.vapi.ai/incident/945421#21e5bef6a09364f3ea5fc91d48cd8b93a5aaee526069135fb4ed944618a1b69d We are aware of an issue that is impacting the ability for users to create and in some cases view Boards or Insights within the dashboard. This issue is only impacting viewing analytical data and is not impacting live Assistants, Squads, Calls or Chats. https://status.vapi.ai/incident/945104 Mon, 06 Jul 2026 18:15:00 -0000 https://status.vapi.ai/incident/945104#8a52bbc507486a1a4ff6987d58c725a18a5469ba3bd8c4abc9a623c2595fec60 We noticed a degradation in API success rate only on the daily channel from 11 A.M to 11:04 A.M. Success rate has since recovered and we are not seeing any further degradation - the team will continue to monitor the issue. https://status.vapi.ai/incident/941850 Thu, 02 Jul 2026 18:15:00 -0000 https://status.vapi.ai/incident/941850#f1de56e0ebbd5978daef43095d3ba3afeb7dcbb4836a91e97f70499bab696511 We observed an increase in API error rates between 11:00 and 11:04 am PT, affecting only the daily channel. Service levels recovered after 11:04 m PT. We are investigating the root cause and actively monitoring API health. https://status.vapi.ai/ Thu, 02 Jul 2026 18:10:16 +0000 https://status.vapi.ai/#eaec4fe9419d0b7ba3bf69eb4cb48e19263de86b309998bc1f248720fcfde923 Vapi Call Logs recovered https://status.vapi.ai/incident/941850 Thu, 02 Jul 2026 18:07:00 -0000 https://status.vapi.ai/incident/941850#ae24cfa8d580801bebcfceb317be4d054aadba787802125bc9c431f3383890ee We are aware of and are investigating degradation in API success rate in the daily channel. https://status.vapi.ai/ Thu, 02 Jul 2026 18:00:31 +0000 https://status.vapi.ai/#eaec4fe9419d0b7ba3bf69eb4cb48e19263de86b309998bc1f248720fcfde923 Vapi Call Logs went down https://status.vapi.ai/incident/936394 Sat, 27 Jun 2026 00:48:00 -0000 https://status.vapi.ai/incident/936394#810e2bdbe9008352accc6d508c69473411a38bddd98556c8ea2f51ccec90852e We have deployed a fix for this issue and are observing full resolution. All systems are fully operational. Our team will continue to monitor. https://status.vapi.ai/incident/936394 Fri, 26 Jun 2026 23:03:00 -0000 https://status.vapi.ai/incident/936394#159e6f3530ceecd95940560a42e4b55e929b55f95ab161de48f4b757ab2d9da4 We are continuing our work to deploy this fix across our services. Our next update will be once the fix is successfully deployed everywhere. https://status.vapi.ai/incident/936394 Fri, 26 Jun 2026 20:51:00 -0000 https://status.vapi.ai/incident/936394#7f46fc0695ba6093c386abb43043c6eabce1623e506af6c878bd1b90fb570e5b We have identified the root cause of this issue and are working to deploy a fix. https://status.vapi.ai/incident/936394 Fri, 26 Jun 2026 19:55:00 -0000 https://status.vapi.ai/incident/936394#2aa9525ebbd9fde4b700fa3e47e19024b8a34fb5b524256329ef7d1fce06e992 We are investigating reports of high latency when viewing logs within the dashboard. At this time we do not see any impact to call success rate, this issue appears isolated to accessing logs of calls once completed. https://status.vapi.ai/incident/933768 Wed, 24 Jun 2026 20:59:00 -0000 https://status.vapi.ai/incident/933768#f4819423ea0451891f486c669f825e9b00257caf9e6c61c4e7b659a10fde6269 We have deployed a fix for this issue and will continue to monitor. We have not seen any elevated error rate since 1:20PM PT. https://status.vapi.ai/incident/933768 Wed, 24 Jun 2026 20:41:00 -0000 https://status.vapi.ai/incident/933768#01f868c11c32546a1af78e3dce1903ab13c74f44fa3f29982a694b0608c6a542 We have observed recovery of this issue starting around 1:20PM PT. We identified the root cause of the issue and are working to implement a fix. https://status.vapi.ai/incident/933768 Wed, 24 Jun 2026 20:12:00 -0000 https://status.vapi.ai/incident/933768#b1b7898040897805eadcb6b8db4097ba4709a55436c9668766448a4e9a636bcd We are investigating reports of elevated failure rates affecting our API on weekly channel. Our team is actively working to confirm these reports and will provide an update within the next 30 minutes. https://status.vapi.ai/ Sat, 20 Jun 2026 21:19:14 +0000 https://status.vapi.ai/#f0df96d27716b83c7ef3358c0791eac5e6acb8e81d4e854cc138a1dc5a26505c Vapi API [Weekly] recovered https://status.vapi.ai/ Sat, 20 Jun 2026 21:12:54 +0000 https://status.vapi.ai/#f0df96d27716b83c7ef3358c0791eac5e6acb8e81d4e854cc138a1dc5a26505c Vapi API [Weekly] went down https://status.vapi.ai/incident/926178 Wed, 17 Jun 2026 01:47:00 -0000 https://status.vapi.ai/incident/926178#85d3aa232ce51d5242b88cc2f6971217e414c35792f618ce8df2f78b2be81c8b We have implemented a fix and observed full recovery. Failures were observed beginning 5:45pm and resolved as of 6:05pm. https://status.vapi.ai/incident/926178 Wed, 17 Jun 2026 01:15:00 -0000 https://status.vapi.ai/incident/926178#103922de53d377d641aa90915e04b7acc9d20f20ddcc81c171bd4fcaaeb0098d We are observing recovery in API success rates across both daily and weekly channels. https://status.vapi.ai/incident/926178 Wed, 17 Jun 2026 01:01:00 -0000 https://status.vapi.ai/incident/926178#db44a32e42e20600beabeaa326dc13acf4db55d659dd4300c10e8ea954eed11c We are observing elevated error rates across API endpoints in the daily and weekly channels. The team is actively investigating. https://status.vapi.ai/ Wed, 17 Jun 2026 01:00:17 +0000 https://status.vapi.ai/#032e8840028f0ccc3267efc34f91f5d2f1e6e4ecaac35411f195c4b7a85f6fc9 Vapi Call Logs recovered https://status.vapi.ai/ Wed, 17 Jun 2026 01:00:10 +0000 https://status.vapi.ai/#c0680ffc9adda34a0903389755af4ad9ab67baec027e4d1945b0f9d5426ee08f Vonage Outbound recovered https://status.vapi.ai/ Wed, 17 Jun 2026 00:50:45 +0000 https://status.vapi.ai/#032e8840028f0ccc3267efc34f91f5d2f1e6e4ecaac35411f195c4b7a85f6fc9 Vapi Call Logs went down https://status.vapi.ai/ Wed, 17 Jun 2026 00:50:40 +0000 https://status.vapi.ai/#c0680ffc9adda34a0903389755af4ad9ab67baec027e4d1945b0f9d5426ee08f Vonage Outbound went down https://status.vapi.ai/incident/925915 Tue, 16 Jun 2026 19:17:00 -0000 https://status.vapi.ai/incident/925915#00c314800e90d36950fada68bf816cefcb844ea4ad3877b0d3c6af09705ef3ee We observed an increase in API error rates between 12:05-12:10pm PT affecting the weekly channel. Service levels recovered after 12:10pm PT. We are investigating the root cause and actively monitoring API health. https://status.vapi.ai/ Tue, 16 Jun 2026 19:08:57 +0000 https://status.vapi.ai/#52789cd4dcf557d014535b68bd79eb9afc17e6afa3aaca8606433f79fd59c235 Vapi API [Weekly] recovered https://status.vapi.ai/ Tue, 16 Jun 2026 19:03:03 +0000 https://status.vapi.ai/#52789cd4dcf557d014535b68bd79eb9afc17e6afa3aaca8606433f79fd59c235 Vapi API [Weekly] went down https://status.vapi.ai/ Sat, 13 Jun 2026 13:20:17 +0000 https://status.vapi.ai/#7c43c306e7b43969d42fc6d939ee1e9b02522e316936607de7b85c1b1aca612e Vapi API [Weekly] recovered https://status.vapi.ai/ Sat, 13 Jun 2026 13:13:53 +0000 https://status.vapi.ai/#7c43c306e7b43969d42fc6d939ee1e9b02522e316936607de7b85c1b1aca612e Vapi API [Weekly] went down https://status.vapi.ai/incident/918243 Tue, 09 Jun 2026 03:00:42 -0000 https://status.vapi.ai/incident/918243#48d050d78312fb752a9f4dbd02b76f212cdec76b286fcd8f5fa50e18f7fba2e4 We will be performing a routine certificate update on our SIP server. This maintenance requires a brief server restart and will be carried out during a low-traffic period to minimize any impact. We do not expect any significant disruption, and service will resume immediately after the restart. https://status.vapi.ai/ Wed, 03 Jun 2026 19:35:05 +0000 https://status.vapi.ai/#ef9a1046d791f79699eb38480125e002106ebb62d97c5f957a3dad3a1dc47801 OpenAI recovered https://status.vapi.ai/ Wed, 03 Jun 2026 19:24:07 +0000 https://status.vapi.ai/#ef9a1046d791f79699eb38480125e002106ebb62d97c5f957a3dad3a1dc47801 OpenAI went down https://status.vapi.ai/incident/911982 Wed, 03 Jun 2026 13:31:00 -0000 https://status.vapi.ai/incident/911982#e708a1efcfc1a17ce288a3c0fc2332c716a440a40921cf9b77e261b482b00cde The incident has been resolved, and service restored as of 5:47am PDT. https://status.vapi.ai/incident/911982 Wed, 03 Jun 2026 13:03:00 -0000 https://status.vapi.ai/incident/911982#be03304b21231b2eb3e7cf4f89c34ec9e8db31b99af53a43828a5277bd90487c We implemented a fix and are seeing recovery as of 5:47am PDT. We will continue to monitor and update here. https://status.vapi.ai/incident/911982 Wed, 03 Jun 2026 12:40:00 -0000 https://status.vapi.ai/incident/911982#1b92b2133c933cca947293de77b3f5f88ed7fee6e6fce30f99afd56f7703309c We are seeing a high rate of call creation failures. We are investigating and will share updates here. https://status.vapi.ai/incident/911475 Tue, 02 Jun 2026 23:42:00 -0000 https://status.vapi.ai/incident/911475#3d4230dd7d761815986010b63d384691b2e1efc904b55ca1d101c2cdc6f10f6d Our team has identified the root cause and deployed a fix. The issue has been resolved, and all systems are operating normally. We will continue monitoring to ensure stability. https://status.vapi.ai/incident/911475 Tue, 02 Jun 2026 23:14:00 -0000 https://status.vapi.ai/incident/911475#f99e857be7d9f4452509dffadc3d3af6b4121763683a364dd28038629e15a908 If you are seeing issues, you may use https://dashboard-weekly.vapi.ai/ as an immediate workaround instead of https://dashboard.vapi.ai/ https://status.vapi.ai/incident/911475 Tue, 02 Jun 2026 23:11:00 -0000 https://status.vapi.ai/incident/911475#b54a9c18e5bb1d9f5c1c67eb931c61fae1001d0469f10516962b5bfbb3255815 We are investigating reports of errors loading the dashboard affecting customers on our Weekly channel. Our team is actively working to determine the root cause and will provide the next update within 30 minutes or sooner. https://status.vapi.ai/incident/901977 Fri, 29 May 2026 20:22:00 -0000 https://status.vapi.ai/incident/901977#6ca955afb85d1438ffcd967fb1a4b3901a89063a20df0c7b2481645fb848b568 # Vapi RCA - US Platform Outage, May 21, 2026 **RCA:** US Platform Outage (Database Connection Exhaustion) **Status:** Resolved **Primary Impact:** Voice calls and API requests failed; the dashboard was unavailable **Date:** May 21, 2026 **Customer-facing systems affected:** Calls, API, Chat, Dashboard, Logs **Severity:** Critical ### Executive Summary On May 21, 2026, the Vapi US platform was unavailable for approximately 4 hours and 7 minutes, beginning at 7:02 AM PT, with service restored by 11:09 AM. Calls began failing at 7:02 AM PT, and by 7:12 AM PT the platform had progressed to a full outage of voice calls and the dashboard. During the window, voice calls failed to connect or complete, API requests returned errors, and the dashboard was inaccessible. Customers served from our EU and AUS regions were not affected. The outage began with a configuration change our database provider applied at 6:44 AM PT to the audit logging module used by our databases. The telemetry/audit logging setting caused Postgres processes to block while writing log output (syslog) at the moment they accepted new connections. Two databases that every call and API request depends on stopped accepting traffic, so the platform could neither authorize requests nor record new calls. Service was restored after the provider disabled the affected logging and restarted the database, and we ramped traffic back in a controlled way to avoid a second failure. We marked the incident resolved at 11:49 AM PT after sustained monitoring confirmed stability. The changes below focus on removing the dependencies that let a database fault become a full outage. ### What You May Have Observed - Inbound and outbound voice calls failing to connect, or ending early - API requests returning server errors (HTTP 5xx) - Inability to access the Vapi dashboard - Scheduled and campaign calls not firing during the window - A brief period of partial recovery mid-incident, where some calls succeeded before failures resumed ### Timeline (PT) - **6:44 AM**: Our database provider applies a configuration change to audit logging. - **7:02 AM**: First monitors fire for API degradation; calls begin failing. - **7:18 AM**: On-call engineer acknowledges the page and begins investigating. - **7:38 AM**: The core infrastructure team jumped into a formal incident. - **7:43 AM**: Status page updated to report degradation. - **7:53 AM**: Status page updated to confirm a full outage of calls and dashboard. - **8:10 AM**: Production database identified as the source; database provider support engaged. - **8:16 AM**: Escalated with the provider for higher urgency. - **8:29 AM**: Status page confirms the production database as the cause. - **9:35 to 10:00 AM**: Brief recovery after a database restart, followed by renewed degradation as traffic resumed. - **10:03 AM**: Provider identifies root cause: database processes stuck writing audit logs while accepting connections, caused by a misconfigured project-wide telemetry setting. - **10:05 AM**: Affected logging disabled and the database endpoint restarted; the database returns to normal. - **10:05 to 11:09 AM**: Traffic ramped back gradually, weekly cluster first (restored 10:38 AM), then daily (restored 11:09 AM). - **11:49 AM**: Incident resolved. ### Root Cause **An audit-logging change exhausted the database connection pool** Vapi’s databases include audit logging. At 6:44 AM PT, our database provider changed where that audit output was written. A misconfiguration in the provider's project-wide telemetry settings caused Postgres processes to block while writing log output at the moment they accepted new connections. Connections accumulated in a waiting state until the pool was exhausted, and the affected databases could no longer accept traffic. **A hard dependency on two databases turned the problem into a full outage** Every API request and call passes through two of these databases: one authorizes the request at our API gateway, and the other records the call before it is queued for processing. Both were among the affected databases. With neither reachable, the platform could not authorize requests or create calls, so the failure was total rather than partial. A read replica was in place, but the provider's configuration change applied at the project level and affected both the primary and replica. **Resulting customer impact** For the duration of the window, calls failed to connect or complete and API requests returned errors. The dashboard, which also depends on these databases, did not load. Scheduled and campaign calls due to fire during the window did not run and were not retried automatically. Customers also would have noticed incidents before the Vapi status page was updated, due to the delay between on-call acknowledgment and creation of any status page. ### Resolution - Our database provider disabled the audit log collection on the affected databases and restarted the database endpoint, which restored their ability to accept connections. - To avoid a connection storm overwhelming the recovered databases, we brought internal services back up gradually rather than all at once, restoring the weekly cluster first and then the daily cluster. - We confirmed recovery through API success-rate, error-rate, and database latency monitoring before closing the incident. Our provider has since published and confirmed a fix to the affected audit log collectors. ### Prevention **Within the next week we are working towards:** - Add production monitoring for database query latency and connection-volume anomalies, so this signature is caught at onset rather than inferred from downstream symptoms. - Establish a faster, clearly defined escalation path with our database provider. Provider escalation and resolution took longer than it should have. - Implement a change management process with our database provider so changes that could impact availability are done in a more controlled manner. **Over the next quarter we are working towards:** - Introduce a read cache in front of authorization and configuration data, removing the hard dependency on that database so a future database fault degrades the platform rather than disabling it. - Migrate our critical databases to a platform that supports a regional hot standby, so we can fail over when a primary becomes unavailable. - Implement automatic status updates based on monitors, to ensure customers are made aware of incidents when we are. - Move call-record writes to an asynchronous path, removing the hard dependency on the call database for connecting a call. ### Customer Actions - No action is required to restore service. We are committed to earning your trust. As part of that, progress on the prevention items will be shared with you via your account team. https://status.vapi.ai/incident/907756 Fri, 29 May 2026 03:58:00 -0000 https://status.vapi.ai/incident/907756#22a16b71a89835776385ccfa98c5645b5542f6a95a92c0e91ee74ad056250bee We have identified the cause of the issue and reverted the change. The issue has been resolved, and all systems are operating normally. We will continue monitoring to ensure stability. https://status.vapi.ai/incident/907756 Fri, 29 May 2026 03:51:00 -0000 https://status.vapi.ai/incident/907756#b3ac414d3fde6833f4088e04ac0785b2ea4dabb4edefd0e1c2e45e3ba6edf297 We are investigating reports of degraded performance affecting the Vapi Dashboard. Calls do not appear to be impacted. Our team is actively working to determine the root cause and will provide the next update within 30 minutes. https://status.vapi.ai/incident/907173 Thu, 28 May 2026 11:08:00 -0000 https://status.vapi.ai/incident/907173#aec14e18b6e63c2b511012d90f6c7afd46014c3c8792748c884ca35256265776 The issue was caused by a brief DB hang that has been resolved, and all systems are operating normally. We will continue monitoring to ensure stability. https://status.vapi.ai/incident/907173 Thu, 28 May 2026 10:14:00 -0000 https://status.vapi.ai/incident/907173#cfead94652778cd287c1fd256a557ff2c8cfafd048bf449fbe387e03aa88f174 We're seeing an increased rate in call failures and are actively looking into it. https://status.vapi.ai/ Thu, 28 May 2026 09:49:46 +0000 https://status.vapi.ai/#bed10fa112aa05e8217c0e8bee936910862a3d530d6d7c5ecfa84bc19b215a3b Twilio Inbound recovered https://status.vapi.ai/ Thu, 28 May 2026 09:40:18 +0000 https://status.vapi.ai/#bed10fa112aa05e8217c0e8bee936910862a3d530d6d7c5ecfa84bc19b215a3b Twilio Inbound went down https://status.vapi.ai/incident/905860 Tue, 26 May 2026 19:55:00 -0000 https://status.vapi.ai/incident/905860#9a83bda61a044d7f2a170dca2c87ab6c99032e9164eaafcef05608d1dc24b7f8 The issue was caused by a brief API latency blip that has been resolved, and all systems are operating normally. We will continue monitoring to ensure stability. https://status.vapi.ai/incident/905860 Tue, 26 May 2026 19:17:00 -0000 https://status.vapi.ai/incident/905860#aa521e7b942f04f2e8fd6bfe8f26c472eaebc14f3132f4ee5a351fb2879c2567 We are investigating reports of degraded performance affecting calls. Our team is actively working to determine the root cause and will provide the next update in 45 minutes at the latest. https://status.vapi.ai/incident/901977 Fri, 22 May 2026 03:03:00 -0000 https://status.vapi.ai/incident/901977#7fc7a396a86f0f7be0cd4a61457ec1d1655323be5a7861c4185e04de8ec178ff # Incident Report: Database Outage (Log Collector Misconfiguration) ## What Happened Vapi experienced a large service outage causing voice calls to fail and the dashboard to become unavailable. This was caused by a failure in an audit log collector in the Vapi production database. The triggering event was an `apply_config` that our database provider executed at 6:44 AM PST. A misconfiguration in the project-wide telemetry settings caused Postgres processes to become stuck writing to syslog when accepting new connections, exhausting the connection pool and rendering the database unable to accept traffic, including from within the pod itself. We notified our provider's support line at 8:10 AM PST. The root cause was identified at 10:03 AM PST by our database provider. Mitigation was applied by disabling the OTEL connection and restarting the endpoint, after which the system returned to a normal state. A fix to the audit collectors was subsequently published and confirmed stable. ## Customer Impact - **Service availability:** Large outage. Vapi's voice services were unavailable during the incident window, affecting 100% of customers from 7:12 AM PT until 11:49 AM PT when the incident was marked as resolved. - The Vapi dashboard was also unavailable during that time. ## Timeline (PST) | Time | Event | |------|-------| | 6:44 AM | Our database provider executes an `apply_config` change, triggering the incident. | | 7:12 AM | Vapi begins to observe call degradation. | | 7:22 AM | The team begins its investigation. | | 7:43 AM | Vapi updates the status page to notify customers of observed degradation. | | 7:53 AM | Vapi updates the status page to confirm a full outage of both voice calls and the dashboard. | | 8:10 AM | Vapi suspects production database behavior as the source of the problem and notifies the database provider's support team. Initial investigation begins; a large spike in waiting-status connections is observed. | | 8:16 AM | Internal escalation with the database provider for increased urgency. | | 8:29 AM | Vapi confirms production database behavior as the source of the problem on the status page and continues to collaborate with the database provider on mitigation. | | 9:35–10:00 AM | A brief recovery is observed after restarting the database, but degradation reappears after services are scaled back up. | | 10:03 AM | Database provider identifies the root cause: Postgres processes stuck on syslog writes during connection acceptance, caused by a misconfigured project-wide `telemetry_setting` for log collectors. | | 10:03 AM+ | OTEL connection disabled; endpoint restarted; system returns to normal state. | | 10:38 AM | Vapi increases traffic back on the weekly environment and confirms that service is restored. | | 11:09 AM | Vapi increases traffic back on the daily environment, confirms service is restored, and moves to a monitoring stage. | | 11:49 AM | Vapi marks the incident as resolved. | https://status.vapi.ai/incident/901977 Thu, 21 May 2026 18:32:00 -0000 https://status.vapi.ai/incident/901977#44062674e3d0cbc5451015feee7c7fb3f8ec03ee220efb26d8a1448db4aee75e Service has returned to normal operating levels. Call success metrics have recovered and remained stable for 30 minutes across both daily and weekly channels, and all platform functionality has been restored. We’re continuing to monitor closely and will provide further updates if anything changes. We will update the status page with an incident report within 12 hours. Thank you for your patience. https://status.vapi.ai/incident/901977 Thu, 21 May 2026 18:09:00 -0000 https://status.vapi.ai/incident/901977#f05c9dd8a08e6a422e62e0de7b36eb56af35531bb3e6fa4ef8725564d406924d Services are recovering across both our weekly and daily clusters, and all metrics are trending positive. Our DB provider has identified and confirmed the root cause and we have applied an initial remediation. Our DB provider team remains actively engaged with us as we scale load back up. We are continuing to monitor closely and will provide updates as we have them. https://status.vapi.ai/incident/901977 Thu, 21 May 2026 18:06:00 -0000 https://status.vapi.ai/incident/901977#9e646ca8c56adf9e941e26f7db1a93098c1dfdb452cee157feedd656a5449973 Our weekly cluster is still showing recovery and calls are going through. We are still monitoring the situation. We have shifted our focus to our daily cluster. https://status.vapi.ai/ Thu, 21 May 2026 17:50:08 +0000 https://status.vapi.ai/#353ee547ca0cf2a652cc40244a7df358fb963d14dc726426a7af83a625e10452 Vonage Outbound recovered https://status.vapi.ai/incident/901977 Thu, 21 May 2026 17:41:00 -0000 https://status.vapi.ai/incident/901977#3e2a01d7d5ad93a2974f339eed96fe11a8ced64352df40ab2d5ce25e749b5eee Our weekly cluster has seen recovery over the last 20 minutes. We are still monitoring the situation as there is a possibility for calls to fail again. We are moving to fixing calls in our daily clusters now. We will post updates when we have new information to share or in 30 minutes. https://status.vapi.ai/ Thu, 21 May 2026 17:40:32 +0000 https://status.vapi.ai/#77bc8feb5225c3246180adffdd3e945123436fc3f07dc7482572a9d7e68cc28a Vapi Call Logs recovered https://status.vapi.ai/ Thu, 21 May 2026 17:30:22 +0000 https://status.vapi.ai/#353ee547ca0cf2a652cc40244a7df358fb963d14dc726426a7af83a625e10452 Vonage Outbound went down https://status.vapi.ai/ Thu, 21 May 2026 17:30:21 +0000 https://status.vapi.ai/#77bc8feb5225c3246180adffdd3e945123436fc3f07dc7482572a9d7e68cc28a Vapi Call Logs went down https://status.vapi.ai/ Thu, 21 May 2026 17:15:27 +0000 https://status.vapi.ai/#729dad46959dd2fcbdd5a6f01ea781d6a37a81ce0d47330f2012b4fb5f96937d Vapi Numbers Inbound recovered https://status.vapi.ai/incident/901977 Thu, 21 May 2026 17:13:00 -0000 https://status.vapi.ai/incident/901977#74f9b2943cab833d7c8d2888c89361402717e6b75f2b2788175094299ae3fd9e Our daily cluster is still experiencing a full outage. Weekly is seeing some recovery. https://status.vapi.ai/incident/901977 Thu, 21 May 2026 17:11:00 -0000 https://status.vapi.ai/incident/901977#357ef6ad5131e7c9eeeecef431ff58c193189b214ba84493a5f01b48920e9e5b We are still in a degraded state on weekly and working on fully resolving the issue. Our daily cluster is still out. https://status.vapi.ai/ Thu, 21 May 2026 17:10:09 +0000 https://status.vapi.ai/#2f78ff14f46b7a32964a18a0123aab6b49b4511a6a4b8e18290411e8f366008c Telnyx Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 17:07:26 +0000 https://status.vapi.ai/#310c3dea9d33d87094c9d459501328966be2e90e7fa1d025cf6594448a58527c Vapi API recovered https://status.vapi.ai/ Thu, 21 May 2026 17:06:31 +0000 https://status.vapi.ai/#729dad46959dd2fcbdd5a6f01ea781d6a37a81ce0d47330f2012b4fb5f96937d Vapi Numbers Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 17:06:10 +0000 https://status.vapi.ai/#49a5b81af34a49133b9c0f9898cbf52438baa0725d118a08a74628e162c94d70 Vapi SIP recovered https://status.vapi.ai/ Thu, 21 May 2026 17:02:20 +0000 https://status.vapi.ai/#310c3dea9d33d87094c9d459501328966be2e90e7fa1d025cf6594448a58527c Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 17:00:01 +0000 https://status.vapi.ai/#8e09c39b6211db70056122375bd5e682736a014ee2147f985a815132525a327d Telnyx Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:59:44 +0000 https://status.vapi.ai/#996b31d692628a0dd5d02c0622764c977829ef1567ac69854d1ed24a728fb85b Twilio Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:59:39 +0000 https://status.vapi.ai/#d732f7f0619d130f9b2a602b3f3a6cc0165018ff38db47a9e51f906a37a06fff Twilio Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:58:33 +0000 https://status.vapi.ai/#49a5b81af34a49133b9c0f9898cbf52438baa0725d118a08a74628e162c94d70 Vapi SIP went down https://status.vapi.ai/ Thu, 21 May 2026 16:50:21 +0000 https://status.vapi.ai/#e72c8cf6b10f11c0636a2f13a1fc15b5790bb451d151be951c2033346be3131d Vonage Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:48:39 +0000 https://status.vapi.ai/#78cddd0c2acecf06dc9b97be75837a6af3d8fb284a82200f26bca8cdf0905d39 SIP Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:45:17 +0000 https://status.vapi.ai/#e28366513478d32838e28dba2e529c8529a5c591d06e35ce2626721c1aca6a9e Vapi Numbers Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:43:16 +0000 https://status.vapi.ai/#f423c19b5fcb237d228148bf63bca8e5cb4daf2d6eb837008a4f84ac0d8787a9 Vapi API recovered https://status.vapi.ai/incident/901977 Thu, 21 May 2026 16:41:00 -0000 https://status.vapi.ai/incident/901977#a9c65e0ad3cbd819ca9deda4d6f065b3107618e6ab4275f47d7aa66355c9886e We are seeing some recovery in Voice Calls and Dashboard calls and are continuing to monitor the situation. We will post updates as we have news or in 30 minutes. https://status.vapi.ai/ Thu, 21 May 2026 16:39:36 +0000 https://status.vapi.ai/#8e09c39b6211db70056122375bd5e682736a014ee2147f985a815132525a327d Telnyx Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:39:35 +0000 https://status.vapi.ai/#996b31d692628a0dd5d02c0622764c977829ef1567ac69854d1ed24a728fb85b Twilio Outbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:39:19 +0000 https://status.vapi.ai/#d732f7f0619d130f9b2a602b3f3a6cc0165018ff38db47a9e51f906a37a06fff Twilio Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:38:44 +0000 https://status.vapi.ai/#78cddd0c2acecf06dc9b97be75837a6af3d8fb284a82200f26bca8cdf0905d39 SIP Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:38:26 +0000 https://status.vapi.ai/#78111767b33c8bcd57fa56df0f1bbdf69873044c3317cf4e3905d3b1577ff719 Vapi Numbers Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:38:09 +0000 https://status.vapi.ai/#b008ff3757069210b808c944b837fdcede801356361ca60ef654fd26de6fa988 Vapi API [Weekly] recovered https://status.vapi.ai/ Thu, 21 May 2026 16:30:18 +0000 https://status.vapi.ai/#e72c8cf6b10f11c0636a2f13a1fc15b5790bb451d151be951c2033346be3131d Vonage Outbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:30:07 +0000 https://status.vapi.ai/#f423c19b5fcb237d228148bf63bca8e5cb4daf2d6eb837008a4f84ac0d8787a9 Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 16:29:55 +0000 https://status.vapi.ai/#2f78ff14f46b7a32964a18a0123aab6b49b4511a6a4b8e18290411e8f366008c Telnyx Outbound went down https://status.vapi.ai/incident/901977 Thu, 21 May 2026 16:29:00 -0000 https://status.vapi.ai/incident/901977#b27cb903a68fceac436fc50e6a3de5c98bdac799b17d0c6bae2b84f7f801eb8e Our DB provider has escalated to the highest level. Their most senior architect is now directly involved in identifying the fix. We are collaborating closely on resolution. We will post an update as we have news or in 30 minutes. https://status.vapi.ai/ Thu, 21 May 2026 16:28:51 +0000 https://status.vapi.ai/#11360181ed83aecea9328b7f8c585ffa42e12b540738b083d0f776f34d0a3eb4 Vapi SIP recovered https://status.vapi.ai/ Thu, 21 May 2026 16:28:14 +0000 https://status.vapi.ai/#78111767b33c8bcd57fa56df0f1bbdf69873044c3317cf4e3905d3b1577ff719 Vapi Numbers Outbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:27:26 +0000 https://status.vapi.ai/#b008ff3757069210b808c944b837fdcede801356361ca60ef654fd26de6fa988 Vapi API [Weekly] went down https://status.vapi.ai/ Thu, 21 May 2026 16:25:27 +0000 https://status.vapi.ai/#e28366513478d32838e28dba2e529c8529a5c591d06e35ce2626721c1aca6a9e Vapi Numbers Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 16:22:51 +0000 https://status.vapi.ai/#11360181ed83aecea9328b7f8c585ffa42e12b540738b083d0f776f34d0a3eb4 Vapi SIP went down https://status.vapi.ai/ Thu, 21 May 2026 16:08:45 +0000 https://status.vapi.ai/#54dd9a26a240f25192201adfe9520f31cdeac31c867331b89ec161483497e63a SIP Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:05:28 +0000 https://status.vapi.ai/#ecd8c6e3b5c8c28af876461d229fbb25dfe023338001699f847168822003b198 Vapi Numbers Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 16:04:46 +0000 https://status.vapi.ai/#854f0f2ab4abe1236b9ed7a27a649ccc4bbe1bda1da7755b59473c135e4c6a70 Vapi API recovered https://status.vapi.ai/ Thu, 21 May 2026 16:00:02 +0000 https://status.vapi.ai/#c3cca7dc7c082a433a6043022a340c74b7996b2f70f6accd64538e10cde55fca Vonage Inbound recovered https://status.vapi.ai/incident/901977 Thu, 21 May 2026 15:59:00 -0000 https://status.vapi.ai/incident/901977#4d3a3033b97de54cb08f6f8a47e803639c9fb1003307ccf436fe3582a93d0d1f Our DB provider confirmed the config change which we have identified as the cause for our DB outage, which causes voice calls to drop and our dashboard to not load. We are collaborating with our provider on an eventual fix or workaround. They have escalated this issue to the highest level of urgency on their side. We will post an update as we have news or in 30 minutes. https://status.vapi.ai/ Thu, 21 May 2026 15:55:16 +0000 https://status.vapi.ai/#854f0f2ab4abe1236b9ed7a27a649ccc4bbe1bda1da7755b59473c135e4c6a70 Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 15:51:12 +0000 https://status.vapi.ai/#c3cca7dc7c082a433a6043022a340c74b7996b2f70f6accd64538e10cde55fca Vonage Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:51:05 +0000 https://status.vapi.ai/#4299d596a54bfe9e16c54254b538536906eb08c597a9c6ee25d2b021f7abd87c Vapi SIP recovered https://status.vapi.ai/ Thu, 21 May 2026 15:47:35 +0000 https://status.vapi.ai/#d239955a6cc76f1ac86ae48cf40adffa36985b62c722f6ec551a64abd2e243d3 Vapi API recovered https://status.vapi.ai/ Thu, 21 May 2026 15:46:18 +0000 https://status.vapi.ai/#ecd8c6e3b5c8c28af876461d229fbb25dfe023338001699f847168822003b198 Vapi Numbers Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:45:09 +0000 https://status.vapi.ai/#ae21ec8dfee3514f63db4a45866ce5c500c9e5835ace2dd9586a2342f405ac96 Vapi Call Logs recovered https://status.vapi.ai/ Thu, 21 May 2026 15:42:35 +0000 https://status.vapi.ai/#4299d596a54bfe9e16c54254b538536906eb08c597a9c6ee25d2b021f7abd87c Vapi SIP went down https://status.vapi.ai/ Thu, 21 May 2026 15:41:19 +0000 https://status.vapi.ai/#d239955a6cc76f1ac86ae48cf40adffa36985b62c722f6ec551a64abd2e243d3 Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 15:40:12 +0000 https://status.vapi.ai/#89916145b0f104e625d13baf8bb00bab8524ae7ce291fb0f6b8d44e19fe92fcb Vonage Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:39:45 +0000 https://status.vapi.ai/#2450361e017a7c907f7e7d8b5bdb59e0020eeb952e5704fbbcced904a67d654a Telnyx Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:38:52 +0000 https://status.vapi.ai/#a14c834cd578fa7d70652a6873f91875832595bc5441f0b2dcfec3f98bd83b00 SIP Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:35:25 +0000 https://status.vapi.ai/#81ab42c32c3c73b4ebe2f9dda013006dc86dddef5a9585a0e17c623d94f4d9b9 Vapi Numbers Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:33:35 +0000 https://status.vapi.ai/#545cc195214e455317cf84b6ac617a7409a7c5722fcc3c0604d8d4ee9616486f Vapi API recovered https://status.vapi.ai/ Thu, 21 May 2026 15:29:21 +0000 https://status.vapi.ai/#a14c834cd578fa7d70652a6873f91875832595bc5441f0b2dcfec3f98bd83b00 SIP Outbound went down https://status.vapi.ai/incident/901977 Thu, 21 May 2026 15:27:00 -0000 https://status.vapi.ai/incident/901977#98a8d6c344800b42cffd198fb2ef7061bfb51a020e9f2653cb2de3f24a07e77a We are still investigating a complete outage in Voice Calls. Our DB provider applied a configuration change at 6:44am which is causing our DB to be completely unavailable. We are working with them to get our DBs back up. We do not have an ETA or resolution yet, however our provider has escalated the issue internally. We will post an update as we learn more or in 30 minutes. https://status.vapi.ai/ Thu, 21 May 2026 15:25:47 +0000 https://status.vapi.ai/#545cc195214e455317cf84b6ac617a7409a7c5722fcc3c0604d8d4ee9616486f Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 15:23:47 +0000 https://status.vapi.ai/#b596b203ab7ac0c2a74cf3d4a30af8da2357c59ddcff56c917baaa7927be4cbe Vapi API recovered https://status.vapi.ai/ Thu, 21 May 2026 15:23:32 +0000 https://status.vapi.ai/#e3f08fe3d249ad1e94b28a43e3e498a91305069d447a0639f480b43daed72f06 Vapi SIP recovered https://status.vapi.ai/ Thu, 21 May 2026 15:19:58 +0000 https://status.vapi.ai/#67c838033001ed0f5c1ec799e3db8c4d28b9aa5b7f715bedeedb2335ca5c699a Vonage Inbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:19:47 +0000 https://status.vapi.ai/#21822646adc32aa8510f507f3b547f68c30388802d16930b82992a5f8e872bd6 Twilio Outbound recovered https://status.vapi.ai/ Thu, 21 May 2026 15:19:04 +0000 https://status.vapi.ai/#54dd9a26a240f25192201adfe9520f31cdeac31c867331b89ec161483497e63a SIP Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:16:25 +0000 https://status.vapi.ai/#81ab42c32c3c73b4ebe2f9dda013006dc86dddef5a9585a0e17c623d94f4d9b9 Vapi Numbers Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:13:04 +0000 https://status.vapi.ai/#67c838033001ed0f5c1ec799e3db8c4d28b9aa5b7f715bedeedb2335ca5c699a Vonage Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:12:36 +0000 https://status.vapi.ai/#e3f08fe3d249ad1e94b28a43e3e498a91305069d447a0639f480b43daed72f06 Vapi SIP went down https://status.vapi.ai/ Thu, 21 May 2026 15:11:31 +0000 https://status.vapi.ai/#ae21ec8dfee3514f63db4a45866ce5c500c9e5835ace2dd9586a2342f405ac96 Vapi Call Logs went down https://status.vapi.ai/ Thu, 21 May 2026 15:11:19 +0000 https://status.vapi.ai/#b596b203ab7ac0c2a74cf3d4a30af8da2357c59ddcff56c917baaa7927be4cbe Vapi API went down https://status.vapi.ai/ Thu, 21 May 2026 15:11:07 +0000 https://status.vapi.ai/#89916145b0f104e625d13baf8bb00bab8524ae7ce291fb0f6b8d44e19fe92fcb Vonage Outbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:10:44 +0000 https://status.vapi.ai/#2450361e017a7c907f7e7d8b5bdb59e0020eeb952e5704fbbcced904a67d654a Telnyx Inbound went down https://status.vapi.ai/ Thu, 21 May 2026 15:10:36 +0000 https://status.vapi.ai/#21822646adc32aa8510f507f3b547f68c30388802d16930b82992a5f8e872bd6 Twilio Outbound went down https://status.vapi.ai/incident/901977 Thu, 21 May 2026 13:55:00 -0000 https://status.vapi.ai/incident/901977#f8cb2d0811765f6efcc178134dad27ff9150a1d488382ef286927d953228693a We are investigating an incident causing voice calls dropped. We will publish updates as we get more information or in 30 minutes. https://status.vapi.ai/incident/896802 Fri, 15 May 2026 16:30:00 -0000 https://status.vapi.ai/incident/896802#4b2cf71d77f12b1dad14e3a76612656c3bd4e26d1ea24e74e51a715c1d53e4cc The incident has been resolved and platform functionality has been fully restored. We will continue monitoring and will publish additional details if necessary. https://status.vapi.ai/incident/896802 Fri, 15 May 2026 15:50:00 -0000 https://status.vapi.ai/incident/896802#63c63b1fef11ce64c537c08871590fceb93058d92a511fb0bb1da0e0d10644b9 We are seeing SIP issues affecting some customers and are investigating. https://status.vapi.ai/incident/896603 Fri, 15 May 2026 09:40:00 -0000 https://status.vapi.ai/incident/896603#aaeead6c15b0e6cf3a01c9d1f79a00354a9228a35ab459da32e3b0838d816608 We have noticed a higher-than-usual rate of tool calls in the daily cluster and are currently investigating the issue. https://status.vapi.ai/ Thu, 14 May 2026 18:17:43 +0000 https://status.vapi.ai/#92df35ea25c90cb90430667ce542e3d0961444417a954856ebc7f92029c6d4e6 Vapi Docs recovered https://status.vapi.ai/ Thu, 14 May 2026 16:07:14 +0000 https://status.vapi.ai/#92df35ea25c90cb90430667ce542e3d0961444417a954856ebc7f92029c6d4e6 Vapi Docs went down https://status.vapi.ai/ Thu, 14 May 2026 16:05:40 +0000 https://status.vapi.ai/#4849883629d292345ec7c1a240d860db7959f672d963a8cddfec2d3f3f40dc4c Vapi Docs recovered https://status.vapi.ai/ Thu, 14 May 2026 15:52:39 +0000 https://status.vapi.ai/#4849883629d292345ec7c1a240d860db7959f672d963a8cddfec2d3f3f40dc4c Vapi Docs went down https://status.vapi.ai/ Thu, 14 May 2026 15:49:39 +0000 https://status.vapi.ai/#9bd208d9d3f2ccc81cea050693563a2bf88ebc379c5e77adb905fc5638d79624 Vapi Docs recovered https://status.vapi.ai/ Thu, 14 May 2026 15:39:17 +0000 https://status.vapi.ai/#9bd208d9d3f2ccc81cea050693563a2bf88ebc379c5e77adb905fc5638d79624 Vapi Docs went down https://status.vapi.ai/incident/894167 Tue, 12 May 2026 17:03:00 -0000 https://status.vapi.ai/incident/894167#5d1ad18ddca38885c34c28a75a9500b6153384d09dd28cc187846204ab0cee26 This incident has been resolved. All systems are operating normally https://status.vapi.ai/incident/894167 Tue, 12 May 2026 16:36:00 -0000 https://status.vapi.ai/incident/894167#cbf09e1c09f6921672735ab5044314a900e263ab7a2b3e376bcc4865181436e1 The team has identified the issue, scaled the offending service accordingly, and we're starting to see a recovery. We will continue monitoring the situation as it improves. https://status.vapi.ai/incident/894167 Tue, 12 May 2026 15:53:00 -0000 https://status.vapi.ai/incident/894167#db22463265fe3788be0cdbd11b2cb82dd65ed59d879679fb8e2bc542e985696e The team is still actively looking into the issue and working on a fix. https://status.vapi.ai/incident/894167 Tue, 12 May 2026 15:18:00 -0000 https://status.vapi.ai/incident/894167#ec50b2c21912686da9cca0fbdce616872161d856785f7db1eb353f3046149bca We're seeing an increased rate in call failures and are actively looking into it. https://status.vapi.ai/incident/888152 Tue, 05 May 2026 14:44:00 -0000 https://status.vapi.ai/incident/888152#d8e442a8ed0005442498ab22d4651b680bfb582eb77faef1eb077c0297e23bd5 Chat assistants on the weekly update channel were returning empty responses after tool calls, causing conversations to stall or end unexpectedly. We have rolled back the weekly update channel to a stable version for now to mitigate this. Note: It impacts only chat endpoints. https://status.vapi.ai/incident/876010 Mon, 20 Apr 2026 22:12:00 -0000 https://status.vapi.ai/incident/876010#59f00261b0c32e94df074648a3dab5db108dd6ccb724afa222a50071d6bd057f Our documentation provider is experiencing an outage. We’re in touch with the team and will provide communication when services are back up https://status.vapi.ai/incident/873215 Thu, 16 Apr 2026 17:00:00 -0000 https://status.vapi.ai/incident/873215#18b409e2669990d474f29284b11efe38d57215d75ca822ea73189bcb020481ea We have now resolved this incident. Between ~7:30AM PT and ~9:30AM PT, a new query pattern caused database slowness that increased API latency and led to dropped inbound calls with certain providers. We mitigated by rolling back the deployment and are following up with a deeper review of the query change. https://status.vapi.ai/incident/873215 Thu, 16 Apr 2026 15:35:00 -0000 https://status.vapi.ai/incident/873215#2abf856bd8639124beef2926d54f8a6253d6fef620cccaeefce38244d6940d4e We are observing systems recover and performance is returning to normal. Some users may still see brief residual impact as systems stabilize. https://status.vapi.ai/incident/873215 Thu, 16 Apr 2026 14:45:00 -0000 https://status.vapi.ai/incident/873215#f8b4561bbbd5cacd6e39596af2c93a990b757cd4b12e82eed50cd45e67a0a986 We are investigating reports of degraded performance affecting a subset of calls. Our team is actively working to determine the root cause and will provide updates as we learn more. https://status.vapi.ai/incident/871401 Tue, 14 Apr 2026 15:27:00 -0000 https://status.vapi.ai/incident/871401#0af584e7d1c5175d618d42df5189ca155afd2b44082730b06ca589e879763bde The issue has been resolved. After applying the remediation, we monitored the affected systems and confirmed stable operation. All services are functioning normally. https://status.vapi.ai/incident/871401 Tue, 14 Apr 2026 15:12:00 -0000 https://status.vapi.ai/incident/871401#85fb57417c21dde8daca9b278f9ea5fec0eb476b59e05d4eb4bd5ccb06a09cdd We identified and applied a remediation for the issue. The change has been deployed and we are actively monitoring to confirm full resolution. We will provide an update within 30 minutes or once we've confirmed stability. https://status.vapi.ai/incident/871401 Tue, 14 Apr 2026 14:57:00 -0000 https://status.vapi.ai/incident/871401#c0d2308d61ca58168b0d729dc5d0122e5bdfa8d8464213adc3220f08840f44bc Our engineering team continues to actively work on restoring SIP services. We are still assessing the full scope of the issue and working toward a resolution. https://status.vapi.ai/incident/871401 Tue, 14 Apr 2026 14:25:00 -0000 https://status.vapi.ai/incident/871401#ffd6ce58cc26cb5a15260b97207af798d8ce8dae659c694d0f47d4771bdc911e Upon further investigation, the impact to our SIP infrastructure is significantly greater than initially assessed. All SIP Calls services are currently experiencing full downtime, affecting inbound and outbound calls, transfers, and all in-call functionality. Our engineering team is fully engaged and working urgently to restore services. https://status.vapi.ai/incident/871401 Tue, 14 Apr 2026 13:32:00 -0000 https://status.vapi.ai/incident/871401#320c111ddeb909721d8f0e0a899c6b1b518fecf51618f57480d0cba0c4155386 We are currently experiencing degradation in our SIP infrastructure, resulting in in-call failures including call transfers, increased latency, and other related issues. Our team is actively investigating and working to resolve the problem. We will provide updates as more information becomes available. https://status.vapi.ai/incident/869144 Tue, 14 Apr 2026 04:00:00 -0000 https://status.vapi.ai/incident/869144#d653a57238554929b87bb81e4fce4377daadd71128c6bf1f5cd08b378072e0ab We'll be applying the latest patches and security fixes to our SIP SBC node. This is a routine procedure and should result in no more than a few seconds of downtime. https://status.vapi.ai/incident/869141 Sat, 11 Apr 2026 04:00:00 -0000 https://status.vapi.ai/incident/869141#d261f9be01667c0dc6904c7c245f3ac71ab177e0b4fb3890fd41ca951ebd888e We'll be applying the latest patches and security fixes to our SIP SBC node. This is a routine procedure and should result in no more than a few seconds of downtime. https://status.vapi.ai/incident/863336 Thu, 02 Apr 2026 11:30:00 -0000 https://status.vapi.ai/incident/863336#53cea7f2ac152d5b4664a9828855408247be9adb98db7ecf0e76abace2e4d320 We are currently observing elevated error rates affecting calls that use the Soniox transcriber. Impacted calls may terminate unexpectedly with the ended reason call.in-progress.error-vapifault-soniox-transcriber-failed. While we work to resolve this, we recommend switching to an alternative transcriber or configuring a transcriber fallback plan to ensure call continuity. You can set up fallbacks by following the guide here: https://docs.vapi.ai/customization/transcriber-fallback-plan We are actively monitoring the situation and will provide updates as more information becomes available. https://status.vapi.ai/incident/857606 Wed, 25 Mar 2026 20:53:00 -0000 https://status.vapi.ai/incident/857606#02cd21ac0ff66a6fbe37fc1f54779115dd562adbe292a497438d75d607804d2a We observed an elevated rate of API errors from 1:28pm to 1:39pm PDT. The errors have since resolved. We are closely monitoring API performance and investigating the root cause. https://status.vapi.ai/incident/853214 Sat, 21 Mar 2026 05:46:00 -0000 https://status.vapi.ai/incident/853214#1ec488020290792118f0b7a2ae7ed9c9e3f45afd391fecdba457cb0754119c0f **Incident Report, March 19, 2026** **Impact:** A service disruption affected inbound and outbound call reliability on the Daily and Weekly channel. Some calls failed to connect with `transport-never-connected`, `worker-not-available`, `worker-died`, and `deepgram-transcriber-failed` end reasons. **Timeline (all times PDT):** **12:20 PM** We detected elevated call failure rates on the Weekly production cluster. **12:22 PM** We published a status page incident and began investigating. **12:25 PM** We identified the trigger as an unanticipated surge in call volume that exceeded our provisioned cluster capacity and downstream rate limits with a model provider. **12:30 PM** We applied traffic controls and began working with the model provider to increase capacity. Call failures began declining. **1:40 PM** Call success rates returned to normal and held stable. First incident window closed. **~4:00 PM** A separate traffic spike re-triggered infrastructure constraints, leading to elevated failures. We began investigating immediately. **4:00 PM to 4:40 PM** We rebalanced traffic and migrated affected workloads to dedicated infrastructure to restore headroom on shared clusters. **4:50 PM** All mitigations took effect. Call success rates returned to normal. **4:50 PM to 8:10 PM** We continued active monitoring. No further failures observed. **8:10 PM** Second incident window closed. **Immediate Action Items:** Improve workload isolation and per-account capacity guardrails to prevent resource contention from cascading across the platform. **Note:** A full root cause analysis is underway and will be available upon request. We sincerely apologize for the disruption and thank you for your patience. https://status.vapi.ai/incident/853214 Fri, 20 Mar 2026 04:23:00 -0000 https://status.vapi.ai/incident/853214#5df2c9f8e885c73cda7da0ac38204d30539512f762dc54edc94ac23fede085f0 The incident has been resolved and services have been stable since 4:50pm PT. We will continue monitoring and will publish additional details if necessary. https://status.vapi.ai/incident/853214 Fri, 20 Mar 2026 03:09:00 -0000 https://status.vapi.ai/incident/853214#984c2c2ace24e6eb3834f91fe9062c6b16f798379f2d04db5f108a968d1c679f Our earlier mitigation is working and services have been stable since 4:50 PM. We have identified a potential root cause and are working on a permanent fix. We will share further updates once we deploy and validate the fix. https://status.vapi.ai/incident/853214 Fri, 20 Mar 2026 00:22:00 -0000 https://status.vapi.ai/incident/853214#2e4255ec6176ab936ad0884cb095c615f04ec928221d8c4b249268849a2d900d The immediate mitigation we deployed is working and we are seeing call success rates continuing to recover. We are still investigating root cause and closely monitoring service performance. https://status.vapi.ai/incident/853214 Thu, 19 Mar 2026 23:50:00 -0000 https://status.vapi.ai/incident/853214#f0fc82ad196c936cce266a8db767d28628a3f7c8d4b79943f80942e52bc506e1 We're seeing improved call success rates, but we're still monitoring the situation. https://status.vapi.ai/incident/853214 Thu, 19 Mar 2026 23:17:00 -0000 https://status.vapi.ai/incident/853214#c3784d0d08086ea8f46b1fb51f1e997a8a5d9d0f6acd7c19a883b1590df52232 We're seeing elevated call failures on weekly, and the team is actively looking into it. https://status.vapi.ai/incident/853120 Thu, 19 Mar 2026 20:40:00 -0000 https://status.vapi.ai/incident/853120#354d58eb21545626600e9462990f349adf1b427b908b28653ed0ed2eaa87c7d2 Resolved — The issue causing degraded performance has been identified and mitigated as of 13:45 PDT. All services are operating normally. We will continue to monitor and provide an update if needed. https://status.vapi.ai/incident/853120 Thu, 19 Mar 2026 20:22:00 -0000 https://status.vapi.ai/incident/853120#4be5c7d28bd73a2af59638b6c59bfaa6b5db5410dd132575f10e3407a2a4bd0b We've partnered with Deepgram to apply a mitigation and are actively monitoring error rates. For an immediate workaround, affected users can switch to Deepgram Nova 3 or use a non-Deepgram transcriber. https://status.vapi.ai/incident/853120 Thu, 19 Mar 2026 19:51:00 -0000 https://status.vapi.ai/incident/853120#6367ee004b95c060207e4312a59ca11da57896a0717d13c8512049eaec2cf283 We are seeing worker-not-available error rates going down in the weekly channel. We are also actively working with Deepgram to mitigate transcriber-failed errors in daily and weekly cluster. https://status.vapi.ai/incident/853120 Thu, 19 Mar 2026 19:32:00 -0000 https://status.vapi.ai/incident/853120#9d75a7851f747e2701bca61fa79cbadb0a61c6564b03cf09b82e5ae7c099a689 The root cause for worker-not-available failures has been identified and we are actively deploying fixes to restore normal service. Some users may still experience failures or degraded performance while mitigation is in progress and fixes roll out. https://status.vapi.ai/incident/853120 Thu, 19 Mar 2026 19:21:00 -0000 https://status.vapi.ai/incident/853120#e70e2fb4dfabdcb8c139bba4564db00499e0f425dfa6ac755f634e4b564cfc20 We are aware of elevated call failures rates on the weekly cluster with worker-not-available ended reason, and deepgram-transcriber-unavailable in both daily and weekly channels. Our team is actively investigating the issue. https://status.vapi.ai/incident/846049 Thu, 19 Mar 2026 18:51:00 -0000 https://status.vapi.ai/incident/846049#b51781609f443eb200d1af8b7e96afaf5ba26bc2ad64c6e661bcbec2e0bf33a6 The issue has been resolved we're not seeing any further degradation https://status.vapi.ai/incident/851649 Thu, 19 Mar 2026 04:30:00 -0000 https://status.vapi.ai/incident/851649#5eb65de955ff90a46b3914711615e3ab1d042fe6d125c5169a68fc013139a7a3 We need to apply updates to our SIP server, which will require a restart. During this time, there may be a brief service disruption. The activity is low risk and should be completed within 15 seconds. https://status.vapi.ai/incident/847828 Thu, 12 Mar 2026 16:22:00 -0000 https://status.vapi.ai/incident/847828#bbdb7cf035399a9373ccd33f319621f0a0fd0012ed3b5437f80274a507f50b13 Resolved — The issue causing degraded performance has been identified and mitigated as of 8:22 AM. All services are operating normally. We will continue to monitor and provide an update if needed. https://status.vapi.ai/incident/847828 Thu, 12 Mar 2026 15:23:00 -0000 https://status.vapi.ai/incident/847828#6d3aecc1793582c0fc4442a8940e129c8ed340d0abb259d20e930f09d40b7794 High failure rate in connecting calls and API in the daily channel. Team is working on resolving it. https://status.vapi.ai/incident/845585 Thu, 12 Mar 2026 04:30:00 -0000 https://status.vapi.ai/incident/845585#96529491b2f49a27d31943239c6a118c3735014a590de90c446a6a6fdbeba103 Our SIP service TLS certificate is approaching its expiration date and needs to be renewed. To apply the updated certificate, a brief restart of the SIP service will be required. No prolonged disruption to the service is expected. https://status.vapi.ai/incident/846049 Tue, 10 Mar 2026 12:46:00 -0000 https://status.vapi.ai/incident/846049#32f9f2185d9f6e3c552d7057038d5964864cc8b820fc504d5ffebd57b1c63dd1 We're noticing a small percentage of calls using GPT 5.2 fail with an internal error during inference from OpenAI's side. We've reached out to the team and are closely monitoring the situation. In the meantime, we recommend switching to another model as we're seeing the degradation only on 5.2 currently. https://status.vapi.ai/incident/840264 Wed, 04 Mar 2026 16:17:00 -0000 https://status.vapi.ai/incident/840264#304cb5d51fc9af638fdece66d154f08819643cb862a108bf47236509ad7e044a The issue has been resolved and all systems are operational. https://status.vapi.ai/incident/839609 Wed, 04 Mar 2026 16:04:00 -0000 https://status.vapi.ai/incident/839609#24325fe434d524f2b351e087db0c12f1593c5aa2c7ce1182435018024c50a024 The issue has been resolved and the voice is currently usable. We still recommend setting up fallbacks for any voices for the future to avoid call drops - https://docs.vapi.ai/voice-fallback-plan https://status.vapi.ai/incident/840264 Wed, 04 Mar 2026 16:03:00 -0000 https://status.vapi.ai/incident/840264#b7b23cbc3a05789d4cb49c2c7d50e0929efaef9c70e6513785313f6b5b64217e We're noticing some call degradation primarily on the Daily channel. We are monitoring the situation and will update as we know more. https://status.vapi.ai/incident/839609 Wed, 04 Mar 2026 02:31:00 -0000 https://status.vapi.ai/incident/839609#e5fb4ac499f5cf6aa787fb226f77ed5b833b28fce31cdac86467b956ffd456c4 We're noticing issues with calls using the Vapi voice "Emma". If you are using this voice, we recommend switching to another voice while this is resolved, and add voice fallbacks to prevent complete failures - https://docs.vapi.ai/voice-fallback-plan No other voices are currently impacted. We will update the status page as we know more. https://status.vapi.ai/incident/832329 Thu, 26 Feb 2026 17:08:00 -0000 https://status.vapi.ai/incident/832329#36f7f43f7d538fe3528a574a3e3b6ce6c5848d69be677bb1ba9475cc87d56373 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 https://status.vapi.ai/incident/833083 Thu, 26 Feb 2026 01:59:00 -0000 https://status.vapi.ai/incident/833083#d960f75e523f7589e67724f439f653dacba6ca2842c93f61339741927cfb449a We have not seen the issue since ~3:50pm today. We have determined the root cause and are rolling out a fix to improve stability in the `daily` channel. # Incident Report — Daily Channel Call Failures (February 25, 2026) ## Impact Between 7:27 AM – 3:59 PM PST, approximately 19,527 calls failed on the Daily channel due to call worker failures. All Daily channel users were impacted. The Weekly channel was not affected. ## Timeline (all times in PST) **7:27 AM** — Degraded call reliability detected on the Daily channel. Status page updated and investigation begins immediately. **8:33 AM** — Issue escalated. Team recommends affected customers switch to the Weekly channel while investigation continues. Status page updated. **9:04 AM** — Team begins proactive outreach to guide affected customers to the Weekly channel. **10:55 AM** — Additional call failures observed on Daily after a brief period of stability. Investigation continues. **11:00 AM** — Rolled back previous deployment. Did not observe any significant improvement. **1:30 PM** — Continued investigating the issue. **3:59 PM** — No further issues observed. **6:00 PM** — Released a fix to improve stability in the Daily channel. Incident resolved. ## What Went Well - The issue was detected and acknowledged quickly. - A dedicated incident response was organized promptly to focus investigation. - Teams were notified early and guided affected customers to switch to the Weekly channel. ## Action Items - Isolate background operations from call handling - Strengthen deployment validation - Improve resilience under load - Expand monitoring and alerting ## Note This report is intended as a summary of the incident timeline, impact, and immediate action items. A deeper root cause analysis is available upon request. This issue impacted the Daily channel only. Customers desiring increased stability (at the cost of delayed access to features) can switch to the Weekly channel by navigating to **Organization Settings** on the Vapi Dashboard and changing the Channel to **"weekly"**. https://status.vapi.ai/incident/833083 Wed, 25 Feb 2026 19:12:00 -0000 https://status.vapi.ai/incident/833083#1a5adba1beeb5e73a07bdce1f5663eff2720adbed947530bcedc4ed7736bbc74 We are seeing intermittent failures related to the earlier incident, slightly higher than normal amounts. The team is investigating and will share additional updates here. Degradation is still limited to `daily` channel. If you are seeing instability we suggest switching to the `weekly` channel (in Organization Settings → Channel). https://status.vapi.ai/incident/832374 Wed, 25 Feb 2026 17:50:00 -0000 https://status.vapi.ai/incident/832374#8e267946a34af6f45ad3da3cb4f68356a389140cf2268817d17ce1e9caa314eb Incident report: **Impact:** A service disruption affected call reliability on the Weekly channel. Some calls ended unexpectedly with `worker-not-available` or `worker-died` end reasons. **Timeline (all times PT):** - **8:07 AM** - We detected a burst of call failures across the platform. - **8:16 AM** - Automated monitoring alert fired. We acknowledged and began investigating. - **8:42 AM** - We scoped the impact across affected accounts. - **8:47 AM** - The issue self-resolved. We identified the root cause as resource contention in our call processing infrastructure during a traffic spike. - **9:18 AM** - We completed an initial root cause analysis and identified an underlying bottleneck in our call queue infrastructure. - **11:13 AM** - A related issue resurfaced due to cascading effects from the earlier contention. We began investigating immediately. - **11:25 AM** - We published a status page to notify customers. - **11:38 AM** - We confirmed the root cause as CPU contention between infrastructure components. - **11:39 AM** - We applied a mitigation. Call queue metrics began recovering. - **11:45 AM** - We updated the status page with the identified cause and fix. - **11:46 AM** - Error rates began declining. We continued active monitoring. - **1:11 PM** - We declared resolution on the status page. - **~1:35 PM** - A brief secondary spike occurred during an infrastructure resource adjustment. We responded immediately. - **3:21 PM** - All systems fully stabilized. **Action Items** Enforce resource limits across processing components and improve infrastructure isolation for critical call processing. **Note** A full root cause analysis is underway and will be available upon request. We sincerely apologize for the disruption and thank you for your patience. https://status.vapi.ai/incident/833083 Wed, 25 Feb 2026 16:56:00 -0000 https://status.vapi.ai/incident/833083#1581c620ecea317f3dad3478cc375f953d024e372ba2cef8333d7a8c42b4a62b The issue is resolved, the team is monitoring and continuing to work on a fix for the recurrent issue. https://status.vapi.ai/incident/833083 Wed, 25 Feb 2026 16:33:00 -0000 https://status.vapi.ai/incident/833083#fc5b0fab6c02d12414def1de60ce44389a0007be9513e7521604d443a3cc577e We have identified the root cause. We did see the issue spike up again during investigation. The team is working on a fix and will update here. In the meantime we suggest customers switch to the Weekly channel for more stability. https://status.vapi.ai/incident/833083 Wed, 25 Feb 2026 15:27:00 -0000 https://status.vapi.ai/incident/833083#f62b1936cb663db3ba58659aaf2c3dc2e5630af799c889069acc801ab575ddcd We are seeing calls being dropped on the Daily channel with ended reason "call.in-progress.error-vapifault-worker-died". The team is looking into it and will update here. https://status.vapi.ai/incident/832374 Tue, 24 Feb 2026 23:21:00 -0000 https://status.vapi.ai/incident/832374#ceb6c6a12d670f0ec7193715c3cb5731871986445cdb889796a4aa6d8b7e0c9b At ~1:35pm roughly 211 more calls dropped on the Weekly cluster. The team is investigating the matter, but we do not see any on-going degradation of service after 2pm PT. We will share an incident report update with the full timeline and action items today. Internally, we are working on a more in-depth root cause analysis to understand deeply why our systems failed and what action we will take to make our platform more stable. https://status.vapi.ai/incident/832374 Tue, 24 Feb 2026 21:11:00 -0000 https://status.vapi.ai/incident/832374#32b7013c6688aafc7434a3e867c28fb90fe36dffe3745e0f8ab35fc032c4f547 The issue is now resolved. https://status.vapi.ai/incident/832374 Tue, 24 Feb 2026 19:45:00 -0000 https://status.vapi.ai/incident/832374#03898747a6fa255fd793c56979fea7bd58014cdce7bc91a2873ae17075801b7a We identified an issue causing a small number of calls to terminate unexpectedly with worker-not-available or worker-died end reasons. A fix has been deployed and error rates are declining. We are continuing to monitor and will provide another update once fully resolved. https://status.vapi.ai/incident/832374 Tue, 24 Feb 2026 19:25:00 -0000 https://status.vapi.ai/incident/832374#64342ce7a0687591132a1a09cd3951b0e61f4c94edde46c2cbfd7d1d52647716 We are seeing calls degraded on Weekly channel. The team is looking into the issue and will share updates here. https://status.vapi.ai/incident/832329 Tue, 24 Feb 2026 18:33:00 -0000 https://status.vapi.ai/incident/832329#f7781f1316a8cfeb7b5ff1c61972a51f46cb2f42f02dde0b8de37353b52a1ae0 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. https://status.vapi.ai/incident/831494 Mon, 23 Feb 2026 18:09:00 -0000 https://status.vapi.ai/incident/831494#97e4497eef8d8ef214551be8396ecedd837e217acd54f5ffbe4a14fb0d85ff8c The issue is resolved as of 10:05am PST. ## Incident Report ### Impact Between 9:10–10:05 AM, 37,806 calls were dropped due to call worker failures. All Daily users were impacted. ### Timeline (all times in PST) 9:02 AM — On-call engineer notices pods crashing in the Daily cluster. 9:11 AM — Black box probe alert fires; acknowledged by on-call engineer, triggering investigation. 9:27 AM — Issue escalates to the point of impacting all calls on Daily. 9:30 AM — Status page created to inform users of impact and request they switch to the Weekly channel. 9:34 AM — Incident team assembles. 9:37 AM — Rollback to previous deployment is initiated. Due to a large backlog of unprocessed jobs, rollback is delayed waiting for an excessive number of pods to become ready. 10:05 AM — Forceful cutover is initiated and service is restored. ### What Went Well Monitoring detected the issue before it became widespread. On-call engineer assembled the incident team quickly. ### Action Items Improve emergency rollback procedure to bypass or relax pod readiness checks during incidents, enabling faster cutover. Continue ongoing observability improvements to reduce MTTD. ### Note A full root cause analysis is underway and available upon request. This report is intended as a summary of the incident timeline, impact, and immediate action items. Note that this issue impacted the Daily cluster only. Customers desiring increased stability (at the cost of delayed access to features) should switch to the Weekly channel by navigating to Organization Settings on the Vapi Dashboard and changing the Channel to "weekly". https://status.vapi.ai/incident/831494 Mon, 23 Feb 2026 17:52:00 -0000 https://status.vapi.ai/incident/831494#fe035841c0c82a76f7b2307589267f66acb9ed1d9b77e3d32179117275bf7072 We are rolling back to an earlier deployment. We are seeing calls getting picked up, but will update here once resolved. https://status.vapi.ai/incident/831494 Mon, 23 Feb 2026 17:30:00 -0000 https://status.vapi.ai/incident/831494#ce1095467be60eeac14672bc65dc9e49591a4529b17dc6e2fa3d127a6bd34040 We are seeing decreased success rate in calls on the `daily` channel. The team is investigating and we will post updates here. In the meantime, we highly recommend switching to `weekly` channel to mitigate service disruption. https://status.vapi.ai/incident/824613 Fri, 13 Feb 2026 05:05:00 -0000 https://status.vapi.ai/incident/824613#d610e560fa7d0de92472bd39ffebd97bb0b6fea02d19a1babf0e1094b0deb4bf Email authentication for the Vapi dashboard has been restored. Users should now be able to sign in normally using their email credentials. https://status.vapi.ai/incident/824340 Fri, 13 Feb 2026 05:00:00 -0000 https://status.vapi.ai/incident/824340#e504e837a95a52478df28644d57756e643ff39c8a39b4d3302acf3a6ea718780 We need to apply patches to our SIP server, which will require a restart. During this time, there may be a brief service disruption. The activity is low risk and should be completed within seconds. https://status.vapi.ai/incident/824613 Thu, 12 Feb 2026 20:57:00 -0000 https://status.vapi.ai/incident/824613#f2afb93f781803ba0437713b5d4f2e72bec00afc2c264301ba182ae581740e05 email authentication for the vapi dashboard was experiencing issues. users were unable to sign in using their email credentials. https://status.vapi.ai/incident/824251 Thu, 12 Feb 2026 18:58:00 -0000 https://status.vapi.ai/incident/824251#6b005e5beb99fe0f74232cb1cae9123e72f6225667eadca42ef189b139fd94c7 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. https://status.vapi.ai/incident/824251 Thu, 12 Feb 2026 17:34:00 -0000 https://status.vapi.ai/incident/824251#9f24ef212b23cf6396e2945d3f7ecf4245fa95e2d9d7580dce8d6a7ffe5a960b We've identified that the issue is related to the ongoing CDC ClickPipes outage (see: https://status.clickhouse.com/incidents/01KH9BE0WY28P4Z48DQ7FPS4DQ). https://status.vapi.ai/incident/824251 Thu, 12 Feb 2026 17:08:00 -0000 https://status.vapi.ai/incident/824251#a825500f248fdbef453185ec55566b4ef68a84d5ce8c706761623933b206476b 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. https://status.vapi.ai/incident/823436 Wed, 11 Feb 2026 20:30:00 -0000 https://status.vapi.ai/incident/823436#7fa639d7dcc346e24911264e028e1706fcbfdab8baf94ab91ad3c5dd0845982a Deepgram had an issue while upgrading their system, which caused 429 errors. They've fixed it and are implementing controls to prevent recurrence. https://status.vapi.ai/incident/823436 Wed, 11 Feb 2026 17:10:00 -0000 https://status.vapi.ai/incident/823436#bb0adf31170a7409804b1c6dd76049ee5c8e2abf77351d00e49d2c70e8bb3e4a We are currently observing elevated error rates affecting calls that use the Deepgram transcriber. Impacted calls may terminate unexpectedly with the ended reason call.in-progress.error-vapifault-deepgram-transcriber-failed. While we work to resolve this, we recommend switching to an alternative transcriber or configuring a transcriber fallback plan to ensure call continuity. You can set up fallbacks by following the guide here: https://docs.vapi.ai/customization/transcriber-fallback-plan We are actively monitoring the situation and will provide updates as more information becomes available. https://status.vapi.ai/incident/818473 Wed, 04 Feb 2026 14:32:00 -0000 https://status.vapi.ai/incident/818473#b540297f3bc5d5acd82f36307eb99e7678f8201473b4cc9eda2e225e9d8e3227 Errors have decreased and the incident has been resolved. We'll post an RCA soon. https://status.vapi.ai/incident/818473 Wed, 04 Feb 2026 14:24:00 -0000 https://status.vapi.ai/incident/818473#3c3c4863a153751720f5351c4a5f28e371de18867f694ccc9cb589d036f3387e We've identified the issue and have deployed a potential fix - we will continue to monitor the situation. https://status.vapi.ai/incident/818473 Wed, 04 Feb 2026 14:14:00 -0000 https://status.vapi.ai/incident/818473#8b1f594e61d0bea32dd6a0604036bc2f65c472dd45b707e248c36ebdc255a6d2 The incident has been mitigated. Between 5:00 AM PT and 6:12 AM PT, API and call execution experienced reduced success rates. Services has been fully restored and is operating normally. https://status.vapi.ai/incident/809181 Tue, 03 Feb 2026 21:16:00 -0000 https://status.vapi.ai/incident/809181#12f78c93de9b6020aff066baa19f8ddee40fe3d849600f8545597b73246ea05b Google is still resolving capacity issues on their end, but we have put a mitigation in place to resolve this for gemini-2.5-flash. Please switch to this model when using Google, if you require another model reach out to support@vapi.ai. We are continuing to monitor and work with the Google team to resolve. https://status.vapi.ai/incident/809181 Tue, 27 Jan 2026 17:47:00 -0000 https://status.vapi.ai/incident/809181#a49460a22f262ced6d88d0ba3af864e1f72792199668c7cab2637d912cfadec3 We are still seeing rate limiting issues for Google LLMs and are looking into another fix we can implement to mitigate it. This is likely caused by regional exhaustion of Google Vertex AI resources rather than us hitting an org-level quota. https://status.vapi.ai/incident/809181 Tue, 27 Jan 2026 06:50:00 -0000 https://status.vapi.ai/incident/809181#f56b91a3bbf655bc3dcdafa59098dbe23eff71cad9b7bcae66dde1ff8b231f06 Google has confirmed the underlying issue is resolved. We’re continuing to deploy a mitigation to ensure this doesn’t impact customers if it recurs. https://status.vapi.ai/incident/809181 Mon, 26 Jan 2026 04:03:00 -0000 https://status.vapi.ai/incident/809181#e4dba0203117f84a3cf043fa34b68ca373b2cc19d6ad58c5057f03725702c653 Google has not resolved the issue on their side, we have requested an updated timeline. Our team is working on implementing fallbacks for the services impacted by the Google degradation (the query tool). https://status.vapi.ai/incident/809181 Thu, 22 Jan 2026 18:47:00 -0000 https://status.vapi.ai/incident/809181#c6f70425a0d63b0535a64d8ba015ccedea5015a9d398758a4ddcb0dcb35deafd Google is again reporting issues with the Vertex AI API that is impacting both our default and fallback Gemini clients. Consider using a different model. We are working with the provider to resolve this and will update here.