CompaniesOptimizelyUptime
Optimizely 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.
97.86%free of major or critical incidents, last 30 days
98.74%free of major or critical incidents, last 90 days
95.79%free of any incident, last 90 days
18incidents 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): 0 min with a major or critical incident open, 5 h 26 min with any incident open, 1 incident startedAug 13 (UTC day): no vendor-reported incident openAug 14 (UTC day): 0 min with a major or critical incident open, 6 h 1 min with any incident open, 1 incident startedAug 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): no vendor-reported incident openAug 20 (UTC day): no vendor-reported 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, 4 h 9 min with any incident open, 1 incident startedAug 25 (UTC day): 0 min with a major or critical incident open, 2 h 22 min with any incident open, 1 incident startedAug 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): 10 h 7 min with a major or critical incident open, 10 h 7 min with any incident open, 2 incidents startedSep 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): 0 min with a major or critical incident open, 16 h 25 min with any incident open, 1 incident startedSep 9 (UTC day): 0 min with a major or critical incident open, 5 h 13 min with any 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): 0 min with a major or critical incident open, 23 min with any incident open, 1 incident startedSep 17 (UTC day): 0 min with a major or critical incident open, 4 min with any incident open, 1 incident startedSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): 1 h 44 min with a major or critical incident open, 1 h 44 min with any incident open, 1 incident startedSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 0 min with a major or critical incident open, 2 h 52 min with any incident open, 1 incident startedSep 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): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): no vendor-reported incident openOct 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): no vendor-reported incident openOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): 0 min with a major or critical incident open, 17 min with any incident open, 1 incident startedOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): 0 min with a major or critical incident open, 3 h 4 min with any incident open, 1 incident startedOct 16 (UTC day): no vendor-reported incident openOct 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): 0 min with a major or critical incident open, 4 h 53 min with any incident open, 1 incident startedOct 22 (UTC day): 0 min with a major or critical incident open, 10 h 55 min with any incident open, 1 incident startedOct 23 (UTC day): 0 min with a major or critical incident open, 1 h 32 min with any incident open, 1 incident startedOct 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): 8 h 8 min with a major or critical incident open, 8 h 8 min with any incident open, 1 incident startedOct 28 (UTC day): 7 h 13 min with a major or critical incident open, 7 h 13 min with any 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
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 97.86% | 94.99% | 15 h 21 min | 36 h 2 min | 7 |
| Last 90 days | 98.74% | 95.79% | 27 h 12 min | 3.8 days | 18 |
This is what Optimizely 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: Optimizely status history · last 90 days · Optimizely status page (opens in new tab) · Markdown