Vapi Outage History
45 incidents recorded over the last 365 days, 45 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Vapi Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 8, 2026 | SIP Infrastructure Scheduled Maintenance | 15 min | Resolved |
| Oct 20, 2026 | Cert renewal for Australia SIP Infra | -22 min | Resolved |
| Oct 20, 2026 | US SIP Infrastructure maintenance | 15 min | Resolved |
| Oct 19, 2026 | Upgrade to SIP infrastructure | 1h 0m | Resolved |
| Oct 16, 2026 | Dashboard is unavailable | 472h 49m | Resolved |
| Oct 14, 2026 | Database maintenance | 2h 0m | Resolved |
| Oct 13, 2026 | Emergency maintenance on SIP monitoring server, US region | 25 min | Resolved |
| Oct 12, 2026 | docs.vapi.ai is unavailable | 565h 7m | Resolved |
| Oct 12, 2026 | Emergency maintenance on SIP outbound dialing infrastructure, US region | 25 min | Resolved |
| Oct 11, 2026 | SIP Infrastructure Maintenance | 15 min | Resolved |
| Oct 10, 2026 | Reactive maintenance on SIP outbound dialing infrastructure, US region | 14 min | Resolved |
| Oct 9, 2026 | BYO SIP Registration | 15 min | Resolved |
| Oct 8, 2026 | Degraded performance: SIP BYO trunk creation | 660h 35m | Resolved |
| Oct 8, 2026 | Scheduled maintenance on SIP outbound dialing infrastructure, US region | 10 min | Resolved |
| Oct 7, 2026 | Reactive maintenance on SIP outbound dialing infrastructure, US region | 32 min | Resolved |
| Oct 6, 2026 | SIP Server downtime | 705h 58m | Resolved |
| Oct 2, 2026 | outbound SIP calls are failing | 810h 50m | Resolved |
| Sep 29, 2026 | New Vapi Phone Number creation degraded | 877h 46m | Resolved |
| Sep 21, 2026 | SIP US Maintenance | 10 min | Resolved |
| Sep 18, 2026 | Dashboard login is unavailable | 1136h 2m | Resolved |
| Sep 13, 2026 | [Resolved] Vapi Chat service disruption | 1261h 2m | Resolved |
| Sep 9, 2026 | EU SIP Maintenance | 15 min | Resolved |
| Sep 2, 2026 | DB Maintenance | -32 min | Resolved |
| Sep 1, 2026 | SIP Maintenance | 24 min | Resolved |
| Aug 29, 2026 | SIP Maintenance | -660 min | Resolved |
| Aug 26, 2026 | Core database maintenance | 361h 29m | Resolved |
| Aug 19, 2026 | Increased rate of call failures | 1757h 27m | Resolved |
| Aug 12, 2026 | CallWebhook issues affecting some web calls | 1931h 53m | Resolved |
| Aug 6, 2026 | Authentication System Maintenance | 1h 0m | Resolved |
| Aug 5, 2026 | Documentation unavilable. | 2091h 48m | Resolved |
| Aug 4, 2026 | API Degradation on Daily | 2116h 2m | Resolved |
| Jul 27, 2026 | SIP Server Update | 1h 0m | Resolved |
| Jul 24, 2026 | Elevated API errors - US | 1644h 10m | Resolved |
| Jul 16, 2026 | Dashboard Access Degredation | 1837h 54m | Resolved |
| Jul 8, 2026 | API Degradation | 2019h 32m | Resolved |
| Jul 7, 2026 | Errors updating Boards | 2063h 24m | Resolved |
| Jul 6, 2026 | API Success Rate Degradation on Daily | 2069h 39m | Resolved |
| Jul 2, 2026 | API degradation | 2165h 47m | Resolved |
| Jun 26, 2026 | High latency retrieving call logs | 1588h 4m | Resolved |
| Jun 24, 2026 | Elevated API error rate on Weekly Channel | 1635h 47m | Resolved |
| Jun 17, 2026 | Elevated API error rates | 1822h 58m | Resolved |
| Jun 16, 2026 | [Recovered] Elevated API error rates | 1828h 42m | Resolved |
| Jun 9, 2026 | SIP Server Restart – Certificate Rotation | 15h 58m | Resolved |
| Jun 3, 2026 | Increased rate of call failures | 2147h 19m | Resolved |
| Jun 2, 2026 | Dashboard Errors | 2160h 48m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Vapi incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Vapi Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Vapi acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Vapi outage in this window ran 90d 5h, against a mean recovery of 37d 10h. If you depend on Vapi in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.