CompaniesOptimizelyMonthly reportsMay 2018
Optimizely in May 2018: incidents, uptime and changes
2incidents posted
0labelled major or critical
100%free of major/critical
99.50%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 3 h 42 min. 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: Minor 1 · No impact listed 1
Incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Episerver is investigating an issue with the Episerver Cloud API / License API | No impact listed | 3.0 h | resolved | 05-10 | |
| US Find | Minor | 3.7 h | resolved | 05-23 |
Cite this
Optimizely posted 2 status incidents in May 2018 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Optimizely in May 2018
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/2018/05