Vonage 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.
100%free of major or critical incidents, last 30 days
100%free of major or critical incidents, last 90 days
46.22%free of any incident, last 90 days
103incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): 0 min with a major or critical incident open, 2 h 42 min with any incident open, 1 incident startedAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): 0 min with a major or critical incident open, 2 h 13 min with any incident open, 1 incident startedAug 10 (UTC day): 0 min with a major or critical incident open, 11 h 43 min with any incident openAug 11 (UTC day): 0 min with a major or critical incident open, 11 h 29 min with any incident open, 2 incidents startedAug 12 (UTC day): 0 min with a major or critical incident open, 5 h 58 min with any incident open, 1 incident startedAug 13 (UTC day): 0 min with a major or critical incident open, 11 h 54 min with any incident open, 2 incidents startedAug 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedAug 15 (UTC day): 0 min with a major or critical incident open, 23 h 34 min with any incident open, 1 incident startedAug 16 (UTC day): 0 min with a major or critical incident open, 1 h 46 min with any incident open, 1 incident startedAug 17 (UTC day): no vendor-reported incident openAug 18 (UTC day): 0 min with a major or critical incident open, 3 h 34 min with any incident open, 1 incident startedAug 19 (UTC day): 0 min with a major or critical incident open, 17 h 43 min with any incident open, 1 incident startedAug 20 (UTC day): 0 min with a major or critical incident open, 1 h 5 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): 0 min with a major or critical incident open, 2 h 28 min with any incident open, 1 incident startedAug 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): 0 min with a major or critical incident open, 15 h 34 min with any incident open, 2 incidents startedAug 30 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 31 (UTC day): 0 min with a major or critical incident open, 13 h 50 min with any incident open, 1 incident startedSep 1 (UTC day): 0 min with a major or critical incident open, 19 h 5 min with any incident open, 2 incidents startedSep 2 (UTC day): 0 min with a major or critical incident open, 9 h 21 min with any incident open, 2 incidents startedSep 3 (UTC day): 0 min with a major or critical incident open, 15 h 39 min with any incident open, 1 incident startedSep 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 5 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 6 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 8 (UTC day): 0 min with a major or critical incident open, 2 h 47 min with any incident open, 1 incident startedSep 9 (UTC day): 0 min with a major or critical incident open, 5 h 50 min with any incident open, 1 incident startedSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): 0 min with a major or critical incident open, 12 h 9 min with any incident open, 1 incident startedSep 12 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 13 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 15 (UTC day): 0 min with a major or critical incident open, 5 h 12 min with any incident openSep 16 (UTC day): 0 min with a major or critical incident open, 1 h 57 min with any incident open, 1 incident startedSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): 0 min with a major or critical incident open, 38 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): 0 min with a major or critical incident open, 9 h 17 min with any incident open, 1 incident startedSep 22 (UTC day): 0 min with a major or critical incident open, 20 h 52 min with any incident open, 1 incident startedSep 23 (UTC day): 0 min with a major or critical incident open, 20 h 49 min with any incident open, 4 incidents startedSep 24 (UTC day): 0 min with a major or critical incident open, 13 h 7 min with any incident open, 1 incident startedSep 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 26 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 27 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 28 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedSep 29 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 30 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 2 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 5 (UTC day): 0 min with a major or critical incident open, 16 h 6 min with any incident openOct 6 (UTC day): 0 min with a major or critical incident open, 14 h 29 min with any incident open, 2 incidents startedOct 7 (UTC day): 0 min with a major or critical incident open, 12 h 40 min with any incident open, 2 incidents startedOct 8 (UTC day): 0 min with a major or critical incident open, 15 h 14 min with any incident open, 2 incidents startedOct 9 (UTC day): 0 min with a major or critical incident open, 13 h 30 min with any incident open, 1 incident startedOct 10 (UTC day): 0 min with a major or critical incident open, 6 h 29 min with any incident open, 1 incident startedOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): 0 min with a major or critical incident open, 10 h with any incident open, 4 incidents startedOct 13 (UTC day): 0 min with a major or critical incident open, 15 h 57 min with any incident open, 3 incidents startedOct 14 (UTC day): 0 min with a major or critical incident open, 18 h 50 min with any incident open, 2 incidents startedOct 15 (UTC day): 0 min with a major or critical incident open, 8 h 53 min with any incident openOct 16 (UTC day): 0 min with a major or critical incident open, 1 h 41 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): 0 min with a major or critical incident open, 7 h 36 min with any incident open, 2 incidents startedOct 20 (UTC day): 0 min with a major or critical incident open, 8 h 18 min with any incident open, 3 incidents startedOct 21 (UTC day): 0 min with a major or critical incident open, 13 h 56 min with any incident open, 5 incidents startedOct 22 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedOct 23 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 24 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 26 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 27 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 5 incidents startedOct 28 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 29 (UTC day): 0 min with a major or critical incident open, 19 h 31 min with any incident open, 4 incidents startedOct 30 (UTC day): 0 min with a major or critical incident open, 19 h 53 min with any incident open, 1 incident startedOct 31 (UTC day): 0 min with a major or critical incident open, 13 h 40 min with any incident openNov 1 (UTC day): 0 min with a major or critical incident open, 10 h 26 min with any incident open, 1 incident startedNov 2 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedNov 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedNov 4 (UTC day): 0 min with a major or critical incident open, 6 min with any 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
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 100% | 38.43% | 0 min | 18.5 days | 55 |
| Last 90 days | 100% | 46.22% | 0 min | 48.4 days | 103 |
This is what Vonage 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: Vonage status history · last 90 days · Vonage status page (opens in new tab) · Markdown