V
Outage recap · Vapi

Vapi outage — October 12, 2026

On October 12, 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.

Emergency maintenance on SIP outbound dialing infrastructure, US region

resolved
Started
Oct 12, 12:00 AM EDT
Resolved
Oct 12, 12:25 AM EDT
Duration
26 min

Vapi's updates (3)

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

    We will be upgrading the API server related to outbound calling. Outbound calling will be unavailable for approximately 30 minutes for new outbound call requests. 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.

  2. update · Oct 12, 12:25 AM EDT

    Maintenance ended

  3. update · Oct 12, 12:25 AM EDT

    Outbound API server upgrade was successful. Outbound call is operational. We will continue to monitor for the next 2 hours.

What our checks recorded

We checked Vapi 6 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 92 ms, against 92 ms over the 24 hours before. Vapi posted the incident at Oct 12, 12:00 AM EDT.

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

docs.vapi.ai is unavailable

resolved
Started
Oct 12, 1:54 PM EDT
Resolved
Oct 12, 2:03 PM EDT
Duration
9 min

Vapi's updates (2)

  1. update · Oct 12, 1:54 PM EDT

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

  2. resolved · Oct 12, 2:03 PM EDT

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

What our checks recorded

We checked Vapi 2 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 73 ms, against 80 ms over the 24 hours before. Vapi posted the incident at Oct 12, 1:54 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.