V
Outage recap · Vapi

Vapi outage — October 20, 2026

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

US SIP Infrastructure maintenance

resolved
Started
Oct 20, 12:00 AM EDT
Resolved
Oct 20, 12:15 AM EDT
Duration
15 min

Vapi's updates (3)

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

    We will be installing SIP monitoring probes to the SIP infrastructure which will disrupt in progress calls for 5 minutes.

  2. update · Oct 20, 12:15 AM EDT

    Maintenance ended

  3. update · Oct 20, 12:15 AM EDT

    SIP maintenance complete with limited to no impact on calls. We will continue to monitor for the next two hours to confirm.

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 196 ms, against 155 ms over the 24 hours before. Vapi posted the incident at Oct 20, 12:00 AM EDT.

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

Cert renewal for Australia SIP Infra

resolved
Started
Oct 20, 5:00 AM EDT
Resolved
Oct 20, 5:07 AM EDT
Duration
8 min

Vapi's updates (3)

  1. update · Oct 20, 5:00 AM EDT

    Calls will be disrupted for approximately 5 minutes due to an SBC restart. We will monitor calls once the server is restarted.

  2. update · Oct 20, 5:07 AM EDT

    Australia SBC was rebooted successfully with less than a minute of interruption.

  3. update · Oct 20, 5:07 AM EDT

    Maintenance ended

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 97 ms, against 155 ms over the 24 hours before. Vapi posted the incident at Oct 20, 5:00 AM 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.