rewindex

CompaniesVapiUptime

Vapi uptime

From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.

99.86%free of major or critical incidents, last 30 days
98.87%free of major or critical incidents, last 90 days
96.72%free of any incident, last 90 days
8incidents started, last 90 days

Last 90 days, by UTC day

Aug 7 (UTC day): no vendor-reported incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): no vendor-reported incident openAug 11 (UTC day): no vendor-reported incident openAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): no vendor-reported incident openAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): no vendor-reported incident openAug 18 (UTC day): no vendor-reported incident openAug 19 (UTC day): 5 h 44 min with a major or critical incident open, 5 h 44 min with any incident open, 1 incident startedAug 20 (UTC day): 17 h 20 min with a major or critical incident open, 17 h 20 min with any incident openAug 21 (UTC day): no vendor-reported incident openAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): no vendor-reported incident openAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): no vendor-reported incident openSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): no vendor-reported incident openSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 1 incident startedSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): no vendor-reported incident openSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): 0 min with a major or critical incident open, 6 h 44 min with any incident open, 1 incident startedSep 30 (UTC day): 0 min with a major or critical incident open, 16 h 1 min with any incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): 21 min with a major or critical incident open, 21 min with any incident open, 1 incident startedOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): 0 min with a major or critical incident open, 2 h 56 min with any incident open, 1 incident startedOct 7 (UTC day): 0 min with a major or critical incident open, 9 min with any incident openOct 8 (UTC day): 0 min with a major or critical incident open, 5 h 33 min with any incident open, 1 incident startedOct 9 (UTC day): 0 min with a major or critical incident open, 14 h 47 min with any incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): 9 min with a major or critical incident open, 9 min with any incident open, 1 incident startedOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): no vendor-reported incident openOct 16 (UTC day): 49 min with a major or critical incident open, 49 min with any incident open, 1 incident startedOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): no vendor-reported incident openOct 20 (UTC day): no vendor-reported incident openOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): no vendor-reported incident openOct 23 (UTC day): no vendor-reported incident openOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): no vendor-reported incident openOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): no vendor-reported incident openNov 4 (UTC day): no vendor-reported incident open

Aug 7today

no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive

Last 7 days, by hour

now

Numbers

WindowFree of major/criticalFree of any incidentOutage timeIncident timeIncidents
Last 30 days99.86%96.61%58 min24 h 23 min4
Last 90 days98.87%96.72%24 h 23 min2.9 days8

This is what Vapi itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .

See the incidents: Vapi status history · last 90 days · Vapi status page (opens in new tab) · Markdown