V
Outage recap · Vapi

Vapi outage — October 8, 2026

On October 8, 2026, Vapi had 2 reported incidents on Vapi's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Scheduled maintenance on SIP outbound dialing infrastructure, US region

resolved
Started
Oct 8, 12:00 AM EDT
Resolved
Oct 8, 12:10 AM EDT
Duration
11 min

Vapi's updates (3)

  1. update · Oct 8, 12:00 AM EDT

    Status: Scheduled What is affected: We will apply a software patch to the web server/API that controls outbound dialing through our US SIP infrastructure. When: Tonight, Wednesday, October 7, 21:00–21:15 PT (04:00–04:15 UTC, Thursday, October 8). What to expect: Non-Campaign Outbound calls may briefly stall or fail to connect during the patch over a 5-10 minute period. We will validate for the remainder of the window to confirm calls are connecting normally and update this page when connectivity returns and maintenance is complete. Action needed: None.

  2. update · Oct 8, 12:10 AM EDT

    Maintenance ended

  3. update · Oct 8, 12:10 AM EDT

    The patch to the outbound server was applied and tested in approximately 5 minutes with no downtime. We will continue monitoring over the next few hours.

What our checks recorded

We checked Vapi 3 times from Vapi's start time to its resolution, once every five minutes. Every one of them reached Vapi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 117 ms, against 90 ms over the 24 hours before. Vapi posted the incident at Oct 8, 12:00 AM EDT.

Updates are Vapi's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance: SIP BYO trunk creation

resolved
Started
Oct 8, 2:27 PM EDT
Resolved
Oct 9, 10:47 AM EDT
Duration
20h 20m

Vapi's updates (4)

  1. update · Oct 8, 2:27 PM EDT

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

  2. update · Oct 8, 2:57 PM EDT

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

  3. update · Oct 8, 4:08 PM EDT

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

  4. resolved · Oct 9, 10:47 AM EDT

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

What our checks recorded

We checked Vapi 244 times from Vapi's start time to its resolution, once every five minutes. Every one of them reached Vapi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 116 ms, against 100 ms over the 24 hours before. Vapi posted the incident at Oct 8, 2:27 PM EDT.

Updates are Vapi's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Vapi. This recap summarizes incidents published on Vapi's official status page.