CompaniesOptimizelyMonthly reportsFebruary 2020
Optimizely in February 2020: incidents, uptime and changes
Vendor-reported outage time 5.8 days, incident time 7.3 days. 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. Last 90 days.
By vendor label: Critical 1 · Major 1 · Minor 2 · No impact listed 1
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| FIND Incident - EU Region (EMEA04) | Critical | 6 d | resolved | 02-06 | |
| An Azure service outage may impact some subscriptions - (Issue: App Service) | Major | 5.4 h | resolved | 02-06 |
Other incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| App Service Updates Impacting Some Sites | Minor | 4 d | resolved | 02-08 | |
| FIND Incident - EU Region (EMEA04) | No impact listed | 2.6 h | resolved | 02-20 | |
| A Few Web App Instances Have Response Problems in EMEA | Minor | 33 h | resolved | 02-25 |
Cite this
Optimizely posted 5 status incidents in February 2020 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Optimizely in February 2020
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/2020/02