SIP Server downtime
resolved- Started
- Oct 6, 5:04 PM EDT
- Resolved
- Oct 6, 5:29 PM EDT
- Duration
- 25 min
Vapi's updates (3)
- update · Oct 6, 5:04 PM EDT
Outbound SIP Server downtime from 1:55 to 2:07, impacting outbound calls and call transfers. Currently seeing recovery, and the team is monitoring closely.
- resolved · Oct 6, 5:29 PM EDT
The root cause has been identified, and the issue has been resolved, with downtime experienced between 1:55 and ending at 2:07
- resolved · Oct 6, 8:09 PM EDT
There will be reactive maintenance on SIP outbound dialing infrastructure, US region Status: Scheduled What is affected: Our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing, as part of remediating the root cause of today's incident. Inbound calls are not affected. When: Tuesday, October 6, 21:00–21:15 PT (04:00–04:15 UTC, Oct 7) What to expect: This work is not expected to be customer-impacting or noticeable. Outbound calls may briefly stall during the window; any impact should last less than 10 minutes. Action needed: None
What our checks recorded
We checked Vapi 5 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 55 ms, against 113 ms over the 24 hours before. Vapi posted the incident at Oct 6, 5:04 PM EDT.
Updates are Vapi's own words from its status page (status: resolved); we never add an inferred cause.