Status updates | Vapi

Dashboard login is unavailable

Fri, 18 Sep 2026 23:10:00 -0000

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

Dashboard login is unavailable

Fri, 18 Sep 2026 23:00:00 -0000

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

Scheduled maintenance: SIP US Maintenance

Tue, 15 Sep 2026 17:15:23 -0000

We are performing maintenance on our SIP infrastructure to improve monitoring and stability. This will result in ~1min downtime. Who is affected: Calls using Vapi numbers, SIP (sip.vapi.ai), or a BYO SIP trunk will be unable to connect during the maintenance. Who is not affected: Calls using a native Twilio, Telnyx, or Vonage number connected directly, web callers, or users in the Vapi EU or AUS regions. When: September 20, 2026, 10:00pm to 10:10pm PT What to expect: SIP calls will fail to connect for about 1 minute at 10:00pm PT and return the standard error response. We will then validate for the rest of the window while calls connect normally. Action needed: If one minute of failed calls is a concern, route through an alternate transport such as Twilio for the window. We will update this page when calls are connecting again and when the work is complete.

[Resolved] Vapi Chat service disruption

Sun, 13 Sep 2026 18:00:00 -0000

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 (Internal Server Error) responses, affecting chat session creation, retrieval, and management. Service was restored at 10:55 a.m. Pacific Time. All other services, including voice calls, were unaffected on both channels.

Maintenance: EU SIP Maintenance

Thu, 03 Sep 2026 23:08:02 -0000

We're performing routine maintenance on our telephony infrastructure in the EU region. *Users of the US regional deployment will not be affected (dashboard.vapi.ai, api.vapi.ai, sip.vapi.ai)* When: Wednesday, September 9 2-2:15am CET (Tuesday, September 8 5-5:15pm PT) What to expect: There will be downtime at 2am in which calls made using Vapi Numbers, directly via our SIP infrastructure, or via SIP trunk will not connect and fail immediately. After, there will be a period where we monitor and validate the maintenance but calls will start connecting again. Action needed: If there are concerns around minutes of downtime, customers can configure an alternate transport (i.e. Twilio) for calls. We'll update this page as the maintenance progresses when SIP calls should be back online and when the update is completed altogether.

Maintenance: DB Maintenance

Fri, 28 Aug 2026 18:19:02 -0000

We're performing scheduled maintenance on our database layer, including a capacity upgrade to a read replica and configuration updates to improve connection handling under load. Brief elevated API latency is possible. Active calls are not affected.

Maintenance: SIP Maintenance

Wed, 26 Aug 2026 17:20:03 -0000

We're performing routine maintenance on our telephony infrastructure. When: Monday, August 31 9-10pm PT What to expect: There will be downtime for ~10min at 9pm in which calls made using Vapi Numbers, directly via our SIP infrastructure, or via SIP trunk will not connect and fail immediately. After, there will be a period where we monitor and validate the maintenance but calls will start connecting again. Action needed: If there are concerns around minutes of downtime, customers can configure an alternate transport (i.e. Twilio) for calls. We'll update this page as the maintenance progresses when SIP calls should be back online and when the update is completed altogether.

Increased rate of call failures

Thu, 20 Aug 2026 17:20:00 -0000

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

Increased rate of call failures

Wed, 19 Aug 2026 20:19:00 -0000

The incident is resolved.

Increased rate of call failures

Wed, 19 Aug 2026 20:02:00 -0000

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

Increased rate of call failures

Wed, 19 Aug 2026 19:55:00 -0000

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.

Increased rate of call failures

Wed, 19 Aug 2026 19:26:00 -0000

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

Increased rate of call failures

Wed, 19 Aug 2026 19:01:00 -0000

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.

Increased rate of call failures

Wed, 19 Aug 2026 18:36:00 -0000

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

Increased rate of call failures

Wed, 19 Aug 2026 18:16:00 -0000

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

CallWebhook issues affecting some web calls

Wed, 12 Aug 2026 11:50:00 -0000

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.

Maintenance: Core database maintenance

Fri, 07 Aug 2026 21:39:20 -0000

We're performing scheduled maintenance on core database infrastructure. When: Tuesday, September 8st, 2026 — 9PM to 10PM PDT What to expect: Calls, API reads, and the dashboard continue to work normally throughout. During the window there are three brief periods, a couple of minutes each, where write operations may fail and need to be retried. This affects changes to assistants, phone numbers, and credentials. Action needed: None. Clients with standard retry behavior will not notice. If a write fails, retry it. We'll update this page as the maintenance progresses and post a final note when it's complete.

Documentation unavilable.

Wed, 05 Aug 2026 20:30:00 -0000

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

Documentation unavilable.

Wed, 05 Aug 2026 19:55:00 -0000

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 impact to the Vapi dashboard, API, or other services.

API Degradation on Daily

Tue, 04 Aug 2026 20:20:00 -0000

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.

API Degradation on Daily

Tue, 04 Aug 2026 19:52:00 -0000

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

API Degradation on Daily

Tue, 04 Aug 2026 19:41:00 -0000

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

Maintenance: Authentication System Maintenance

Tue, 04 Aug 2026 01:16:14 -0000

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.

Elevated API errors - US

Fri, 24 Jul 2026 11:44:00 -0000

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.

Maintenance: SIP Server Update

Wed, 22 Jul 2026 12:57:58 -0000

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.

Dashboard Access Degredation

Thu, 16 Jul 2026 10:17:00 -0000

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.

Dashboard Access Degredation

Thu, 16 Jul 2026 10:00:00 -0000

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.

API Degradation

Wed, 08 Jul 2026 20:59:00 -0000

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.

API Degradation

Wed, 08 Jul 2026 20:22:00 -0000

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.

Errors updating Boards

Tue, 07 Jul 2026 07:06:00 -0000

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.

Errors updating Boards

Tue, 07 Jul 2026 02:54:00 -0000

We are deploying a fix into production. We will provide a final update once the fix is merged and the issue has been resolved.

Errors updating Boards

Tue, 07 Jul 2026 02:01:00 -0000

We are continuing to deploy a fix for the degraded performance affecting Boards. We will provide our next update by 7:45 PM PT.

Errors updating Boards

Tue, 07 Jul 2026 01:14:00 -0000

We have identified the root cause of the issue and are actively deploying a fix to restore normal performance to boards.

Errors updating Boards

Tue, 07 Jul 2026 00:30:00 -0000

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.

API Success Rate Degradation on Daily

Mon, 06 Jul 2026 18:15:00 -0000

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.

API degradation

Thu, 02 Jul 2026 18:15:00 -0000

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.

API degradation

Thu, 02 Jul 2026 18:07:00 -0000

We are aware of and are investigating degradation in API success rate in the daily channel.

High latency retrieving call logs

Sat, 27 Jun 2026 00:48:00 -0000

We have deployed a fix for this issue and are observing full resolution. All systems are fully operational. Our team will continue to monitor.

High latency retrieving call logs

Fri, 26 Jun 2026 23:03:00 -0000

We are continuing our work to deploy this fix across our services. Our next update will be once the fix is successfully deployed everywhere.

High latency retrieving call logs

Fri, 26 Jun 2026 20:51:00 -0000

We have identified the root cause of this issue and are working to deploy a fix.

High latency retrieving call logs

Fri, 26 Jun 2026 19:55:00 -0000

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.

Elevated API error rate on Weekly Channel

Wed, 24 Jun 2026 20:59:00 -0000

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.

Elevated API error rate on Weekly Channel

Wed, 24 Jun 2026 20:41:00 -0000

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.

Elevated API error rate on Weekly Channel

Wed, 24 Jun 2026 20:12:00 -0000

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.

Elevated API error rates

Wed, 17 Jun 2026 01:47:00 -0000

We have implemented a fix and observed full recovery. Failures were observed beginning 5:45pm and resolved as of 6:05pm.

Elevated API error rates

Wed, 17 Jun 2026 01:15:00 -0000

We are observing recovery in API success rates across both daily and weekly channels.

Elevated API error rates

Wed, 17 Jun 2026 01:01:00 -0000

We are observing elevated error rates across API endpoints in the daily and weekly channels. The team is actively investigating.

[Recovered] Elevated API error rates

Tue, 16 Jun 2026 19:17:00 -0000

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.

Maintenance: SIP Server Restart – Certificate Rotation

Mon, 08 Jun 2026 20:22:48 -0000

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.

Increased rate of call failures

Wed, 03 Jun 2026 13:31:00 -0000

The incident has been resolved, and service restored as of 5:47am PDT.

Increased rate of call failures

Wed, 03 Jun 2026 13:03:00 -0000

We implemented a fix and are seeing recovery as of 5:47am PDT. We will continue to monitor and update here.

Increased rate of call failures

Wed, 03 Jun 2026 12:40:00 -0000

We are seeing a high rate of call creation failures. We are investigating and will share updates here.

Dashboard Errors

Tue, 02 Jun 2026 23:42:00 -0000

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.

Dashboard Errors

Tue, 02 Jun 2026 23:14:00 -0000

If you are seeing issues, you may use https://dashboard-weekly.vapi.ai/ as an immediate workaround instead of https://dashboard.vapi.ai/

Dashboard Errors

Tue, 02 Jun 2026 23:11:00 -0000

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.

Voice calls dropped and dashboard unavailable

Fri, 29 May 2026 20:22:00 -0000

# 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.

Dashboard Errors

Fri, 29 May 2026 03:58:00 -0000

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.

Dashboard Errors

Fri, 29 May 2026 03:51:00 -0000

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.

Increased Call Failure Rates

Thu, 28 May 2026 11:08:00 -0000

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.

Increased Call Failure Rates

Thu, 28 May 2026 10:14:00 -0000

We're seeing an increased rate in call failures and are actively looking into it.

Elevated call failure rate

Tue, 26 May 2026 19:55:00 -0000

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.

Elevated call failure rate

Tue, 26 May 2026 19:17:00 -0000

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.

Voice calls dropped and dashboard unavailable

Fri, 22 May 2026 03:03:00 -0000

# 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. |

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 18:32:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 18:09:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 18:06:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 17:41:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 17:13:00 -0000

Our daily cluster is still experiencing a full outage. Weekly is seeing some recovery.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 17:11:00 -0000

We are still in a degraded state on weekly and working on fully resolving the issue. Our daily cluster is still out.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 16:41:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 16:29:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 15:59:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 15:27:00 -0000

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.

Voice calls dropped and dashboard unavailable

Thu, 21 May 2026 13:55:00 -0000

We are investigating an incident causing voice calls dropped. We will publish updates as we get more information or in 30 minutes.

SIP Availability degraded

Fri, 15 May 2026 16:30:00 -0000

The incident has been resolved and platform functionality has been fully restored. We will continue monitoring and will publish additional details if necessary.

SIP Availability degraded

Fri, 15 May 2026 15:50:00 -0000

We are seeing SIP issues affecting some customers and are investigating.

Tool call is degraded in the Daily Channel

Fri, 15 May 2026 09:40:00 -0000

We have noticed a higher-than-usual rate of tool calls in the daily cluster and are currently investigating the issue.

Increased Call Failure Rates

Tue, 12 May 2026 17:03:00 -0000

This incident has been resolved. All systems are operating normally

Increased Call Failure Rates

Tue, 12 May 2026 16:36:00 -0000

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.

Increased Call Failure Rates

Tue, 12 May 2026 15:53:00 -0000

The team is still actively looking into the issue and working on a fix.

Increased Call Failure Rates

Tue, 12 May 2026 15:18:00 -0000

We're seeing an increased rate in call failures and are actively looking into it.

Chat Tool Calls Degraded on Weekly Channel

Tue, 05 May 2026 14:44:00 -0000

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.

Documentation resources are down

Mon, 20 Apr 2026 22:12:00 -0000

Our documentation provider is experiencing an outage. We’re in touch with the team and will provide communication when services are back up

Degraded Performance on Inbound Calls

Thu, 16 Apr 2026 17:00:00 -0000

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.

Degraded Performance on Inbound Calls

Thu, 16 Apr 2026 15:35:00 -0000

We are observing systems recover and performance is returning to normal. Some users may still see brief residual impact as systems stabilize.

Degraded Performance on Inbound Calls

Thu, 16 Apr 2026 14:45:00 -0000

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.

SIP Infrastructure Outage

Tue, 14 Apr 2026 15:27:00 -0000

The issue has been resolved. After applying the remediation, we monitored the affected systems and confirmed stable operation. All services are functioning normally.

SIP Infrastructure Outage

Tue, 14 Apr 2026 15:12:00 -0000

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.

SIP Infrastructure Outage

Tue, 14 Apr 2026 14:57:00 -0000

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.

SIP Infrastructure Outage

Tue, 14 Apr 2026 14:25:00 -0000

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.

SIP Infrastructure Outage

Tue, 14 Apr 2026 13:32:00 -0000

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.

Maintenance: SIP Maintenance

Sat, 11 Apr 2026 01:43:30 -0000

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.

Maintenance: SIP Maintenance

Sat, 11 Apr 2026 01:42:39 -0000

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.

Elevated Error Rates with Soniox Transcriber

Thu, 02 Apr 2026 11:30:00 -0000

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.

Degraded API performance on Daily and Weekly channels

Wed, 25 Mar 2026 20:53:00 -0000

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.

Elevated Call Failure Rate on Weekly

Sat, 21 Mar 2026 05:46:00 -0000

**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.

Elevated Call Failure Rate on Weekly

Fri, 20 Mar 2026 04:23:00 -0000

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.

Elevated Call Failure Rate on Weekly

Fri, 20 Mar 2026 03:09:00 -0000

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.

Elevated Call Failure Rate on Weekly

Fri, 20 Mar 2026 00:22:00 -0000

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.

Elevated Call Failure Rate on Weekly

Thu, 19 Mar 2026 23:50:00 -0000

We're seeing improved call success rates, but we're still monitoring the situation.

Elevated Call Failure Rate on Weekly

Thu, 19 Mar 2026 23:17:00 -0000

We're seeing elevated call failures on weekly, and the team is actively looking into it.

Elevated errors in daily and weekly channels

Thu, 19 Mar 2026 20:40:00 -0000

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.

Elevated errors in daily and weekly channels

Thu, 19 Mar 2026 20:22:00 -0000

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.

Elevated errors in daily and weekly channels

Thu, 19 Mar 2026 19:51:00 -0000

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.

Elevated errors in daily and weekly channels

Thu, 19 Mar 2026 19:32:00 -0000

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.

Elevated errors in daily and weekly channels

Thu, 19 Mar 2026 19:21:00 -0000

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.

Some GPT 5.2 calls failing with inference issues

Thu, 19 Mar 2026 18:51:00 -0000

The issue has been resolved we're not seeing any further degradation

Maintenance: SIP System Restart

Tue, 17 Mar 2026 22:46:01 -0000

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.

Daily channel - Calls & dashboard are impacted

Thu, 12 Mar 2026 16:22:00 -0000

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.

Daily channel - Calls & dashboard are impacted

Thu, 12 Mar 2026 15:23:00 -0000

High failure rate in connecting calls and API in the daily channel. Team is working on resolving it.

Some GPT 5.2 calls failing with inference issues

Tue, 10 Mar 2026 12:46:00 -0000

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.

Maintenance: Update SIP certificates

Mon, 09 Mar 2026 22:33:49 -0000

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.

Call Degradation on Daily

Wed, 04 Mar 2026 16:17:00 -0000

The issue has been resolved and all systems are operational.

Vapi Voice "Emma" is temporarily unavailable

Wed, 04 Mar 2026 16:04:00 -0000

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

Call Degradation on Daily

Wed, 04 Mar 2026 16:03:00 -0000

We're noticing some call degradation primarily on the Daily channel. We are monitoring the situation and will update as we know more.

Vapi Voice "Emma" is temporarily unavailable

Wed, 04 Mar 2026 02:31:00 -0000

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.

Authentication Provider Degradation in India

Thu, 26 Feb 2026 17:08:00 -0000

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

Calls are degraded on Daily channel

Thu, 26 Feb 2026 01:59:00 -0000

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"**.

Calls are degraded on Daily channel

Wed, 25 Feb 2026 19:12:00 -0000

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).

Call degradation on Weekly channel

Wed, 25 Feb 2026 17:50:00 -0000

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.

Calls are degraded on Daily channel

Wed, 25 Feb 2026 16:56:00 -0000

The issue is resolved, the team is monitoring and continuing to work on a fix for the recurrent issue.

Calls are degraded on Daily channel

Wed, 25 Feb 2026 16:33:00 -0000

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.

Calls are degraded on Daily channel

Wed, 25 Feb 2026 15:27:00 -0000

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.

Call degradation on Weekly channel

Tue, 24 Feb 2026 23:21:00 -0000

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.

Call degradation on Weekly channel

Tue, 24 Feb 2026 21:11:00 -0000

The issue is now resolved.

Call degradation on Weekly channel

Tue, 24 Feb 2026 19:45:00 -0000

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.

Call degradation on Weekly channel

Tue, 24 Feb 2026 19:25:00 -0000

We are seeing calls degraded on Weekly channel. The team is looking into the issue and will share updates here.

Authentication Provider Degradation in India

Tue, 24 Feb 2026 18:33:00 -0000

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.

Call Degradation in Daily Channel

Mon, 23 Feb 2026 18:09:00 -0000

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".

Call Degradation in Daily Channel

Mon, 23 Feb 2026 17:52:00 -0000

We are rolling back to an earlier deployment. We are seeing calls getting picked up, but will update here once resolved.

Call Degradation in Daily Channel

Mon, 23 Feb 2026 17:30:00 -0000

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.

Unable to Sign in to the Vapi dashboard via Email Authentication

Fri, 13 Feb 2026 05:05:00 -0000

Email authentication for the Vapi dashboard has been restored. Users should now be able to sign in normally using their email credentials.

Unable to Sign in to the Vapi dashboard via Email Authentication

Thu, 12 Feb 2026 20:57:00 -0000

email authentication for the vapi dashboard was experiencing issues. users were unable to sign in using their email credentials.

Maintenance: SIP system restart

Thu, 12 Feb 2026 19:22:35 -0000

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.

Calls not showing up on dashboard

Thu, 12 Feb 2026 18:58:00 -0000

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.

Calls not showing up on dashboard

Thu, 12 Feb 2026 17:34:00 -0000

We've identified that the issue is related to the ongoing CDC ClickPipes outage (see: https://status.clickhouse.com/incidents/01KH9BE0WY28P4Z48DQ7FPS4DQ).

Calls not showing up on dashboard

Thu, 12 Feb 2026 17:08:00 -0000

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.

Elevated Error Rates with Deepgram Transcriber

Wed, 11 Feb 2026 20:30:00 -0000

Deepgram had an issue while upgrading their system, which caused 429 errors. They've fixed it and are implementing controls to prevent recurrence.

Elevated Error Rates with Deepgram Transcriber

Wed, 11 Feb 2026 17:10:00 -0000

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.

Api, call execution degradation

Wed, 04 Feb 2026 14:32:00 -0000

Errors have decreased and the incident has been resolved. We'll post an RCA soon.

Api, call execution degradation

Wed, 04 Feb 2026 14:24:00 -0000

We've identified the issue and have deployed a potential fix - we will continue to monitor the situation.

Api, call execution degradation

Wed, 04 Feb 2026 14:14:00 -0000

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.

Google Gemini Rate Limiting

Tue, 03 Feb 2026 21:16:00 -0000

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.

Google Gemini Rate Limiting

Tue, 27 Jan 2026 17:47:00 -0000

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.

Google Gemini Rate Limiting

Tue, 27 Jan 2026 06:50:00 -0000

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.

Google Gemini Rate Limiting

Mon, 26 Jan 2026 04:03:00 -0000

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).

Google Gemini Rate Limiting

Thu, 22 Jan 2026 18:47:00 -0000

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.

Google Gemini Rate Limiting

Thu, 22 Jan 2026 07:30:00 -0000

We have confirmed with the provider that the issue is from their end. We have implemented fallbacks that should help mitigate this issue going forward. We apologize for any disruption to service as a result of this issue.

Google Gemini Rate Limiting

Wed, 21 Jan 2026 20:11:00 -0000

**Google/Gemini Service Degradation - Immediate Workarounds** We're experiencing intermittent rate limiting from Google affecting several Vapi features. We're working with Google to resolve this. In the meantime, there are immediate workarounds for affected features. - Model (LLM): Gemini models may intermittently fail. - Workaround one - switch to a different model (e.g., GPT 4.1) - Workaround two - [obtain an API key](https://aistudio.google.com/app/api-keys) from Google and use that. - Vapi Dashboard → Settings → Integrations → Custom Credentials - Transcriber (STT): Gemini-based transcription may intermittently fail - Two workarounds - switch your primary or fallback transcriber to a different model (e.g., Deepgram Nova 3) or obtain an API key from Google and use that. - [Voicemail detection](https://docs.vapi.ai/tools/voicemail-tool): may intermittently fail if "provider" is set to "google" - Two workarounds. Switch to "openai" or "twilio" provider (if using Twilio telephony) or turn off **`voicemailDetection`** and switch to Voicemail tool - [Query tool](https://docs.vapi.ai/knowledge-base/using-query-tool): may intermittently fail since it relies on Google infrastructure - Two workarounds (both high effort) - switch to a custom knowledgebase or use a function tool to replicate behavior - [Structured Outputs](https://docs.vapi.ai/assistants/structured-outputs-quickstart): Gemini models may intermittently fail. - Workaround - switch to a different model provider: OpenAI or Anthropic - [Speech-to-Speech](https://docs.vapi.ai/openai-realtime): Gemini models may intermittently fail. - Workaround - switch to a different model provider: OpenAI

Google Gemini Rate Limiting

Wed, 21 Jan 2026 19:40:00 -0000

We are hitting rate limits again with our Google Gemini models. We are working with the vendor to resolve this issue. Please consider using another model at this time or implementing fallbacks.

Google Gemini Rate Limiting Issue

Wed, 21 Jan 2026 04:19:00 -0000

We have pushed a fix and this issue should be resolved. The team will continue to monitor.

Google Gemini Rate Limiting Issue

Wed, 21 Jan 2026 00:10:00 -0000

We have identified the issue and are pushing a fix now.

Google Gemini Rate Limiting Issue

Tue, 20 Jan 2026 23:32:00 -0000

We are seeing an issue with our own Google Vertex AI API key resulting in increased 429 errors using Gemini models. Please consider using a different model provider if you are experiencing this issue. Customers bringing their own key should not be impacted. The team is looking into this issue and will update here.

Maintenance: SIP maintenance

Tue, 20 Jan 2026 21:55:31 -0000

We're doing an upgrade to our SIP database which might cause a few minutes of downtime and instability.

Calls not connecting in daily channel

Mon, 19 Jan 2026 18:38:00 -0000

We experienced a temporary increase in call connection errors caused by worker unavailability. The issue has since been resolved. Impact was limited to the daily channel; the weekly channel was not affected.

Maintenance: SIP Database Maintenance

Thu, 15 Jan 2026 04:00:21 -0000

We need to perform resizing of our existing SIP database. The operation should finish within a few seconds.

Call Degradation in Daily Channel

Thu, 08 Jan 2026 18:11:00 -0000

We are seeing decreased success rate in calls on the `daily` channel. The team is investigating and we will post updates here.

End of call reports + transcript showing duplicate messages

Wed, 24 Dec 2025 07:21:00 -0000

We have reverted the change and tested to confirm the issue is resolved.

Maintenance: Database maintenance

Wed, 24 Dec 2025 06:29:15 -0000

A continuation of yesterday's maintenance will be completed tonight. We anticipate minimal disruption to services. We appreciate your patience and apologize for any inconvenience this may cause.

Calls failing due to worker unavailability

Tue, 23 Dec 2025 23:18:00 -0000

# [IR] Dec 17th — Call Worker Degradation — Object Storage Upload Errors ## Summary On December 17, 2025, at 10:25 AM PST, we observed degradation in our Call Worker service. The issue was caused by Call Workers becoming blocked while uploading call recordings to a downstream object storage provider facing an outage of their own. The incident was fully resolved by 11:02 AM PST, once the downstream provider recovered and Call Workers returned to normal operation. ## Timeline (PST) - **10:25 AM** — Initial call degradation alert triggered - **10:40 AM** — Investigation began - **10:45 AM** — Downstream provider partially recovered - **10:52 AM** — Downstream provider fully recovered - **11:02 AM** — Call Workers fully recovered ## Root Cause A downstream object storage provider experienced a partial outage, during which call recording upload requests began failing or stalling. Requests either timed out or returned 502 errors. These stalled upload operations increased processing time within Call Workers, leading to worker exhaustion. Due to this resource saturation, the system was unable to scale quickly enough to accept new incoming calls, resulting in dropped or unaccepted calls during the affected period. ## Impact For approximately 30 minutes, a subset of calls could not be accepted or were dropped due to unavailable or terminated Call Workers. There was no data loss. **Calls not picked up (worker not available):** - Daily organizations: 15,555 - Weekly organizations: 478 ## What Went Well - Autoscaling eventually resolved the issue of workers being unavailable without the need for manual intervention. ## What Went Poorly - No fallback mechanism was in place for object storage uploads. - Monitoring did not quickly identify the downstream dependency as the root cause. ## Remediation - [ ] Make the object storage upload process asynchronous - [ ] Add more aggressive timeouts and retries for upload operations - [x] Investigate procedures for manually scaling capacity during incidents - [x] Add monitoring for object storage upload errors --- If working on realtime distributed systems excites you, consider applying: https://jobs.ashbyhq.com/vapi/295f5269-1bb5-4740-81fa-9716adc32ad5

End of call reports + transcript showing duplicate messages

Tue, 23 Dec 2025 22:48:00 -0000

A code bug is causing the final call transcripts to show duplicate assistant messages when using `modelOutputInMessagesEnabled`. Calls are working fine, but post-call processing may be impacted. This issue is impacting both `weekly` and `daily` channels. The team is working to revert the offending change. We will update here.

Calls failing due to worker unavailability

Wed, 17 Dec 2025 19:20:00 -0000

The system has recovered. The team is monitoring, and we will update here with a full RCA.

Calls failing due to worker unavailability

Wed, 17 Dec 2025 19:06:00 -0000

We have detected an issue with our call workers not scaling to meet demand. The team is investigating and will update here.

Maintenance: Database maintenance

Tue, 16 Dec 2025 03:31:25 -0000

We'll be adjusting our database configuration during a brief maintenance window of up to 1 hour. During this period, API requests may experience intermittent delays or errors, but we do not anticipate any significant disruption. We appreciate your patience and apologize for any inconvenience this may cause.

Maintenance: SIP maintenance

Sat, 13 Dec 2025 04:00:59 -0000

We need to perform an upgrade on our SIP servers, which needs a restart of some critical services. We expect a few seconds of downtime, and the service should recover itself shortly.

Deepgram Transcriber Degraded

Wed, 10 Dec 2025 20:18:00 -0000

Deepgram has resolved the issue, and we're seeing calls go through fine. We will be closely monitoring the issue. We highly recommend setting up transcriber fallbacks to avoid call failures in situations like this. https://docs.vapi.ai/api-reference/assistants/create#request.body.transcriber.DeepgramTranscriber.fallbackPlan

Deepgram Transcriber Degraded

Wed, 10 Dec 2025 19:49:00 -0000

We're noticing some calls failing with issues with the deepgram transcriber, we're actively monitoring it. In the meantime, we recommend switching to a different transcriber and setting up Transcriber Fallbacks to prevent calls from failing.

ElevenLabs Transcriber Performance Degraded

Sat, 06 Dec 2025 00:26:00 -0000

The issue has been resolved and we will continue monitoring the situation. We recommend setting up transcriber fallbacks to avoid any failed calls in such situations - https://docs.vapi.ai/api-reference/assistants/create#request.body.transcriber.ElevenLabsTranscriber.fallbackPlan

ElevenLabs Transcriber Performance Degraded

Fri, 05 Dec 2025 23:33:00 -0000

Transcriber performance for ElevenLabs STT is currently degraded with some requests being dropped. While we monitor the situation, we recommend switching to another transcriber or setting up fallbacks - https://docs.vapi.ai/api-reference/assistants/create#request.body.transcriber.ElevenLabsTranscriber.fallbackPlan Status Report from ElevenLabs - https://status.elevenlabs.io/incidents/01KBRDKA2CKANKJK182W1WXFXH

Dashboard unavailable due to Cloudflare Issues

Fri, 05 Dec 2025 09:27:00 -0000

The Vapi dashboard is now available after cloudflare have applied the fix. We will continue to monitor to ensure no further disruptions.

Dashboard unavailable due to Cloudflare Issues

Fri, 05 Dec 2025 09:03:00 -0000

Vapi Dashboard is currently unavailable to due a Cloudflare Outage (https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) Calls are NOT impacted.

Calls are impacted.

Thu, 04 Dec 2025 21:24:00 -0000

The system has recovered. We are now working on monitoring the failures closely.

Calls are impacted.

Thu, 04 Dec 2025 21:14:00 -0000

We are seeing elevated errors in starting calls. Our team is on it.

Maintenance: Authentication system maintenance

Mon, 01 Dec 2025 22:29:38 -0000

We’re performing a planned resize of our authentication database, which will require a brief restart of the instance. During this window, users may experience elevated errors when signing in or signing up. Call functionality will not be affected. The process is typically completed within one minute.

Call Logs after Nov 22 not available

Sat, 29 Nov 2025 18:40:00 -0000

We identified the issue as a misconfiguration in the read-API endpoint. The fix has been applied, and all call logs should now display correctly. No data was lost.

Call Logs after Nov 22 not available

Sat, 29 Nov 2025 18:00:00 -0000

We have identified an issue in Dashboard → Call Logs that is preventing call records after November 22 (PST) from appearing in the interface. API access to call logs does not seem affected.

Maintenance: SIP Maintenance

Wed, 26 Nov 2025 23:18:54 -0000

We will be performing critical maintenance on our SIP infrastructure. Calls may be impacted during this period. We appreciate your patience and apologize for any inconvenience this may cause.

Call Logs after 4 PM PT not loading

Thu, 20 Nov 2025 02:40:00 -0000

Affected call logs have been successfully restored. We will providing a detailed RCA soon.

Call Logs after 4 PM PT not loading

Thu, 20 Nov 2025 01:06:00 -0000

We have fixed the sync issue and we see new calls are showing up on the dashboard again. We are still working on restoring the calls logs between 4:00 pm and 5:06 pm PT.

Call Logs after 4 PM PT not loading

Thu, 20 Nov 2025 00:00:00 -0000

We have identified an issue in our DB read replicas that is not displaying call logs after 4 PM PT in dashboard. We are working on fixing the issue. This does not impact active calls and we don't believe there is data loss at this time.

API Degradation

Tue, 18 Nov 2025 17:00:00 -0000

Cloudflare has resolved their issues and our services are restored.

API Degradation

Tue, 18 Nov 2025 12:33:00 -0000

We are experiencing increased API failures due to a widespread Cloudflare outage. Our systems remain operational, but requests routed through Cloudflare may fail or time out. This issue originates at the Cloudflare level and is impacting multiple services globally.

Gladia concurrency limit affected

Mon, 17 Nov 2025 15:00:00 -0000

We have temporarily increased our concurrency limits with provider and working on a long term solution.

Gladia concurrency limit affected

Mon, 17 Nov 2025 13:25:00 -0000

We've identified an spike in call ended reasons with: call.in-progress.error-vapifault-gladia-transcriber-failed. Caused due to a concurrency limit with the provider. While we work on resolving the issue, we recommend switching to another Transcriber.

Call concurrency limit affected

Sun, 16 Nov 2025 16:57:00 -0000

concurrency limit has been reset and jobs are processing normally. issue has been resolved as of 9:05 PT

Deepgram STT degradation

Thu, 13 Nov 2025 23:26:00 -0000

Our STT provider has made a fix on their end and are reporting improvement. We are continuing to monitor while we push out our own improvement: https://status.deepgram.com/incidents/vgsyqxkc67by.

Deepgram STT degradation

Thu, 13 Nov 2025 22:53:00 -0000

Deepgram has confirmed there is an issue on their end resulting in increased latency that may cause calls to drop. We are making a change internally to handle the exception properly.

Deepgram STT degradation

Thu, 13 Nov 2025 22:24:00 -0000

We have found an issue with increased latency from one of our providers which is resulting in call failures.

Deepgram STT degradation

Thu, 13 Nov 2025 22:12:00 -0000

We are seeing calls being dropped for both daily/weekly channels.

Calls to openAI provider are affected

Thu, 13 Nov 2025 10:51:00 -0000

Issue has been mitigated as of 2:50 AM PT

Calls to openAI provider are affected

Thu, 13 Nov 2025 09:46:00 -0000

Calls to openAI provider are affected from 12:15 AM PT, we are actively investigating the issue

SIP calls are degraded

Thu, 13 Nov 2025 02:05:00 -0000

Nov 7th 2025 SIP service degradation Summary ---------- On Friday, November 7th, 2025, one of our SIP gateway experienced a failure, causing inbound and outbound Vapi SIP calls to be disrupted between 10:30 AM and 12:15 PM PST Context --------- All Vapi SIP calls go through our SIP infrastructure which handles SIP trunking, authentication, and registration. When an inbound SIP call arrives, the SIP SBC authenticates and validates it, making a webhook call to our API server for call registration. Once calls are registered, SBC establishes a bidirectional websocket connection (via websocket proxy) to call workers for real-time call processing and audio streaming. Root Cause ------------ Our SIP gateway runs on dedicated infrastructure which runs stateful workloads. This part of our infrastructure was missing log archival configuration. Over time, application logs accumulated and filled the available disk space, causing the server to crash and become unresponsive.This issue was compounded by the absence of disk space monitoring and alerting, which delayed our detection and response. Resolution ---------- Once the issue was identified, our engineering team took the following actions: Cleared accumulated logs to restore available disk space - Restarted SIP gateway services and validated recovery - Implemented immediate log rotation on the affected host - Verified all SIP services were operational before resuming normal operations What We’re Doing to Prevent This -------------------------------- Immediate Actions (Completed) - Deployed disk space monitoring with alerts at 75% utilization - Fixed SIP gateway metrics-based alerts to detect node failures and missing metrics - Added volume-based alerts for all stateful SIP instances Expected results: Early detection of issues affecting SIP gateway instances including high disk usage, node failures, or no metrics, so that any disruption to call processing can be identified and resolved before impacting customers. Short-Term Actions (In Progress – 30 Days) --------------------------------------------- - Implement comprehensive per-node health monitoring with automated alerting - Enhance our synthetic phone health checks to test individual SIP nodes for stateful service health - Deploy hot standby SIP instances for immediate failover capability Expected results: Capture all functional issues at the individual SIP instance level, and ensure that in the event of a failure, we can immediately failover manually to a standby SIP gateway instance to remediate quickly. Long-Term Improvements (Next 60 Days) -------------------------------------------- High Availability: - Implement automated SIP failover based on instance health checks - Perform quarterly automated failover tests to verify reliability Expected results: Failed SIP instances are automatically removed and replaced with healthy nodes, ensuring minimal or no manual intervention and uninterrupted service continuity.

Maintenance: SIP Database Maintenance

Mon, 10 Nov 2025 19:40:57 -0000

We are seeing moderately higher latency on our SIP database (separate from our core application databases) resulting in slightly higher SIP response times (1-1.5 seconds). We will be performing critical maintenance on our database to remediate this issue.

Degradation in SIP calls

Sat, 08 Nov 2025 08:51:00 -0000

We are working on RCA for SIP degradation, we will share it by November 12th

Maintenance: SIP maintenance

Fri, 07 Nov 2025 22:27:05 -0000

We will be performing critical maintenance on our SIP infrastructure. Calls may be impacted during this period. We appreciate your patience and apologize for any inconvenience this may cause.

Degradation in SIP calls

Fri, 07 Nov 2025 20:17:00 -0000

The SIP issue has been resolved. We will continue to monitor our systems.

Degradation in SIP calls

Fri, 07 Nov 2025 20:04:00 -0000

SIP calls are still degraded. Team is actively working on remediation.

Degradation in SIP calls

Fri, 07 Nov 2025 19:27:00 -0000

We are seeing degradation in SIP calls. The team is currently investigating the issue.

SIP calls are degraded

Fri, 07 Nov 2025 13:49:00 -0000

SIP calls are currently degraded. We're looking into it.

Maintenance: Database maintenance

Tue, 04 Nov 2025 23:15:41 -0000

Maintenance: Database maintenance

Tue, 04 Nov 2025 23:13:23 -0000

Maintenance: SIP Maintenance

Wed, 29 Oct 2025 23:02:51 -0000

We are making a minor change to our SIP service (hosted at sip.vapi.ai) that may result in some downtime.

Elevated errors in connecting calls.

Tue, 28 Oct 2025 23:01:00 -0000

We experienced a spike in call connection errors between 3:40 and 3:58. The issue has since been resolved.

API + DB Degradation

Wed, 22 Oct 2025 19:35:00 -0000

We are seeing increased latency and requests timing out from API and DB degradation. We are working with our DB provider to resolve this, and have made a change. Now monitoring to ensure improvement. There was a DB restart and things are looking normal now. The issues have been resolved.

Elevated errors in api

Tue, 21 Oct 2025 16:54:00 -0000

we experienced elevated errors in our api (for phone calls create) at 9:35 AM PT for few minutes. This has been resolved.

Increased 5XXs for a minute

Wed, 15 Oct 2025 18:31:00 -0000

We had a restart on our database endpoint leading to a small blip in 500s for api endpoints.

Worker died errors on calls.

Tue, 14 Oct 2025 09:00:00 -0000

We had a small blip on daily channel with call.in-progress.error-vapifault-worker-died errors due to a new daily deployment. We have rolled it back.

Degradation for inbound twilio calls

Mon, 13 Oct 2025 20:11:00 -0000

The issue with twilio inbound calls failing on daily has been resolved. The root cause was connection timeouts on a new egress proxy service.

Degradation for inbound twilio calls

Mon, 13 Oct 2025 20:01:00 -0000

We are seeing degradation in twilio inbound calls. Only daily channel is affected.

Call logs not visible on dashboard

Mon, 13 Oct 2025 07:45:00 -0000

We detected calls logs not reflecting in the dashboard for some time. This was due to an error while attaching a partition and has been resolved now. Call logs will be populated soon if they were missing.

Increased Latency in Vapi Web Call

Sat, 04 Oct 2025 23:22:00 -0000

After further investigation with our WebRTC provider, this does not seem to be platform issue. We will follow up with impacted users directly.

Increased Latency in Vapi Web Call

Fri, 03 Oct 2025 23:00:00 -0000

We have detected increased latency in Vapi Web Calls which may prevent certain users from joining the call and ultimately ending the call with ended reason: `call.in-progress.error-assistant-did-not-receive-customer-audio`. We are actively working with our WebRTC provider to resolve the issue. To mitigate this, you can try increasing the `customerJoinTimeoutSeconds` property of your assistant. ```bash curl -X PATCH https://api.vapi.ai/assistant/ \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "customerJoinTimeoutSeconds": 60 }' ```

Elevated API errors between 9:30-11:30am PT on 30th Sept.

Tue, 30 Sep 2025 19:11:00 -0000

We experienced intermittent spikes in 5xx errors on our APIs in the weekly cluster. The root cause was identified, and a fix has already been implemented. During this period, both inbound and outbound calls may have been affected, as they rely on the APIs for data, resulting in potential service degradation.

Degradation in connecting SIP calls.

Fri, 12 Sep 2025 22:47:00 -0000

Services are restored.

Degradation in connecting SIP calls.

Fri, 12 Sep 2025 22:19:00 -0000

We're noticing slight increase in failures to connect SIP calls. Our team is investigating on priority.

High errors with connecting to our assistant Db. Calls and API are affected.

Wed, 10 Sep 2025 19:27:00 -0000

Problem has been resolved now. All services are healthy again.

High errors with connecting to our assistant Db. Calls and API are affected.

Wed, 10 Sep 2025 19:17:00 -0000

We are investigating the problem.

Call Logs Since 09/05 00:00 UTC not loading

Fri, 05 Sep 2025 01:43:00 -0000

We have fixed the issue. Call Logs are returned correctly by API

Call Logs Since 09/05 00:00 UTC not loading

Fri, 05 Sep 2025 00:00:00 -0000

We’ve identified an issue in our API that is preventing call logs from loading after 00:00 UTC September 5, 2025. Our team is actively working on a fix. Calls are not affected, and there is no data loss. We’ll provide updates here as soon as the issue is resolved.

Cartesia Voices Degraded

Thu, 04 Sep 2025 20:55:00 -0000

Cartesia has resolved the issue, and is full operational.

Cartesia Voices Degraded

Thu, 04 Sep 2025 20:13:00 -0000

Cartesia voices are experiencing a service degradation and returning 500s which might cause calls to end with call.in-progress.error-vapifault-cartesia-voice-failed. We are closely monitoring the issue, and recommend setting a voice fallback or moving to Vapi voices while this is resolved. You can also track the status at https://status.cartesia.ai/

Elevated cases of assistant not responding in calls on daily cluster

Wed, 03 Sep 2025 10:06:00 -0000

We have identified the root cause. The problem has been fixed by rolling back a recent deployment on daily.

Elevated cases of assistant not responding in calls on daily cluster

Wed, 03 Sep 2025 09:56:00 -0000

We are seeing cases of calls going silent. Either assistant is not responding, causing silence timeouts.

Call Transfers Degradation on Vapi Phone Number

Tue, 02 Sep 2025 19:24:00 -0000

We have scaled up our telephony infrastructure resources and bumped our rate limits. We haven't seen any more issues in the last 20 minutes, and call transfers are working as expected now. We are closely monitoring.

Call Transfers Degradation on Vapi Phone Number

Tue, 02 Sep 2025 14:00:00 -0000

We have identified a high error rate on call transfers when using Vapi Phone Numbers. To the end-user this may cause call drops when assistants initiate a call transfer. The team is actively working in our SIP infrastructure to resolve this.

Deepgram Aura-2 TTS Performance Degradation

Thu, 28 Aug 2025 19:04:00 -0000

Deepgram is investigating an issue where a subset of requests may return elevated rates of 5XX errors or experience significantly higher time to first byte

Aura-2 TTS Performance Degradation

Wed, 27 Aug 2025 21:00:00 -0000

This incident has been resolved.

Aura-2 TTS Performance Degradation

Wed, 27 Aug 2025 17:00:00 -0000

Deepgram reported high rate of 500 errors when using their Aura-2 Voices, which may impact Vapi calls if using this provider. (e.g. ended reason call.in-progress.error-vapifault-deepgram-voice-failed) Follow deepgram's incident report here: https://status.deepgram.com/incidents/sl3zxvhddf1w Recommendations 1. Temporarily switch to another voice, like Vapi or Elevenlabs. 2. Configure a voice fallback. Your calls will still go to Deepgram first but if it fails, it will switch voice to another provider. We won't drop any calls but the user will hear another voice.

Intermittent issues with the dashboard loading

Tue, 26 Aug 2025 00:04:00 -0000

The issue was pinpointed and reverted quickly

Intermittent issues with the dashboard loading

Mon, 25 Aug 2025 23:57:00 -0000

The team has determined the code change which caused the issues and rolled it back. We are continuing to monitor.

Intermittent issues with the dashboard loading

Mon, 25 Aug 2025 21:50:00 -0000

We are seeing issues with the dashboard sidebar loading for some customers. We are looking into it and will update here as we know more. For the time being, users can workaround this issue by clearing local cache and cookies.

Elevated error rates on ElevenLabs Voice requests

Wed, 06 Aug 2025 04:14:00 -0000

Elevenlabs released a fix and is fully operational now. We are also seeing normal levels, but will continue to monitor. For impacted users, we recommend implementing Vapi Fallback Plan to automatically failover in the future https://docs.vapi.ai/voice-fallback-plan

Maintenance: SIP Maintenance

Thu, 31 Jul 2025 02:35:30 -0000

We need to perform an upgrade on our SIP service. Therefore, the SIP service needs a restart. It should be a quick restart but there might be some disruption with ongoing calls and incoming calls, during the restart.

Maintenance: Regular DB maintenance

Tue, 22 Jul 2025 18:00:00 -0000

We are rolling out an important update to our database. Call logs and analytics may be impacted during this period. We appreciate your patience and apologize for any inconvenience this may cause.

Maintenance: Regular DB maintenance

Sat, 19 Jul 2025 00:35:22 -0000

We are rolling out security patches and important updates to our database. This would need a restart of all our database servers. Restarts are quick but there could be a few seconds of intermittent unavailability.

Maintenance: SIP Infrastructure Changes

Thu, 03 Jul 2025 04:57:58 -0000

We will be making changes to our SIP infrastructure which may result in some service degradation, especially for SIP REFER's and outbound calls.

Maintenance: Database maintenance

Sun, 29 Jun 2025 03:30:20 -0000

We'll be adjusting our database configuration during a brief maintenance window of up to 30 minutes. During this period, API requests may experience intermittent delays or errors, but we do not anticipate any significant disruption. We appreciate your patience and apologize for any inconvenience this may cause.

Maintenance: Version upgrade for dedicated SIP instances

Wed, 25 Jun 2025 02:34:23 -0000

We are scheduling a 4 hour maintenance window 2025-06-28 1-5pm PT to upgrade the version of our dedicated SIP infrastructure. There may be some disruption to calls during this time.

Maintenance: Weekly cluster call export maintenance

Tue, 24 Jun 2025 15:00:02 -0000

We’re currently performing maintenance on our analytics database. As a result, call exports from the weekly cluster may return blank CSV files until maintenance is complete. If you run into this issue and need to export data, please temporarily switch your organization’s export setting to daily, then revert back to weekly after exporting. Maintenance will finish by 6 PM PST today. Thank you for your patience.

Maintenance: Weekly cluster maintenance

Tue, 03 Jun 2025 17:00:28 -0000

Weekly cluster is undergoing additional maintenance

Maintenance: Weekly cluster maintenance

Mon, 02 Jun 2025 18:00:25 -0000

Weekly cluster is under additional monitoring and maintenance after update. We should have things resolved by tonight

Maintenance: Upgrading Weekly Cluster

Sun, 04 May 2025 03:20:35 -0000

Regular upgrades to cluster

Maintenance: Auth DB restart

Fri, 25 Apr 2025 03:16:59 -0000

We will be performing a brief restart of our authentication database to accommodate increased scale. This maintenance is expected to complete within one minute. We appreciate your patience and apologize for any inconvenience. Should only impact the signin & signup on dashboard. Calls and other APIs will not be impacted by it.

Maintenance: Upgrading Weekly API

Tue, 15 Apr 2025 18:21:20 -0000

Applying performance optimizations

Maintenance: Upgrade SIP infrastructure

Wed, 26 Mar 2025 01:44:35 -0000

We are rolling out some major infra changes to our SIP infrastructure that should make it more stable. There should not be any downtime but could be some cases of call drops that rely on SIP during the infrastructure rollout.

Maintenance: NeonDB Scheduled Maintenance: DB endpoing restart

Tue, 11 Mar 2025 19:58:24 -0000

Neon is doing scheduled maintenance in our region `us-west-2`: https://neonstatus.com/aws-us-west-oregon/incidents/01JP2WGPKFV2GDV4QSKV8F8NGP. This will require a restart of our endpoint that will result in seconds of downtime. We have marked off the block of time in which this restart will likely happen.

Maintenance: Kubernetes cluster upgrades

Sat, 08 Mar 2025 19:00:38 -0000

We're rolling out Kubernetes cluster upgrades for security and reliability.

Maintenance: SIP cluster scaling

Wed, 29 Jan 2025 21:49:46 -0000

We will be retrying our deployment of SIP cluster to make sure we are ready for upcoming scale. There might be some minor disruptions wrt connecting SIP calls, but we will be closely monitoring the situation and complete the migration swiftly.

Maintenance: DB resizing, 5m of downtime expected.

Sat, 26 Oct 2024 21:45:29 -0000

We need to resize the DB to handle increased load. 5m of downtime is expected.

Maintenance: DB partitioning Saturday afternoon.

Fri, 11 Oct 2024 01:04:56 -0000

We're partitioning our biggest table call. We expect this to be zero downtime but want to be communicative.