CompaniesOptimizelyMonthly reportsJanuary 2018
Optimizely in January 2018: incidents, uptime and changes
5incidents posted
0labelled major or critical
100%free of major/critical
78.30%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 6.7 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: Minor 4 · No impact listed 1
Incidents 5
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| EPiServer Find EU | No impact listed | 35 min | resolved | 01-19 | |
| EPiServer Find EU | Minor | 1.3 h | resolved | 01-21 | |
| EPiServer Find EU | Minor | 3.9 h | resolved | 01-23 | |
| Degraded performance | Minor | 14 d | resolved | 01-25 | |
| A partial service interruption in Azure is currently causing issues with DXC deployments. | Minor | 6 d | resolved | 01-31 |
Cite this
Optimizely posted 5 status incidents in January 2018 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Optimizely in January 2018
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/2018/01