# Optimizely in January 2018: incidents, uptime and changes

> Optimizely in January 2018: 5 incidents on its status page (0 major or critical), 100% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Optimizely’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/optimizely/2018/01
Last updated: 2018-02-06T07:10:00Z

- Incidents posted: 5 (major/critical: 0) · Maintenance: 0
- By vendor impact label: minor 4, none 1
- Uptime (vendor-reported): 100% free of major/critical incidents, 78.30% free of any incident; outage time 0 min, incident time 6.7 days
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2017](https://rewindex.com/company/optimizely/2017/12.md) · Next: [February 2018](https://rewindex.com/company/optimizely/2018/02.md) · [All months](https://rewindex.com/company/optimizely/reports.md) · [Optimizely](https://rewindex.com/company/optimizely.md)

_Uptime: 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._

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [EPiServer Find EU](https://rewindex.com/company/optimizely/incidents/7jpfx6mthgw9.md) | none | 2018-01-19 15:07 UTC | 2018-01-19 15:42 UTC | 35 min | resolved |
| [EPiServer Find EU](https://rewindex.com/company/optimizely/incidents/rlqksbmc6mgl.md) | minor | 2018-01-21 09:51 UTC | 2018-01-21 11:11 UTC | 1.3 h | resolved |
| [EPiServer Find EU](https://rewindex.com/company/optimizely/incidents/w8j70cvttnb4.md) | minor | 2018-01-23 10:45 UTC | 2018-01-23 14:38 UTC | 3.9 h | resolved |
| [Degraded performance](https://rewindex.com/company/optimizely/incidents/5qwj51c5fky9.md) | minor | 2018-01-25 11:47 UTC | 2018-02-08 15:51 UTC | 14 d | resolved |
| [A partial service interruption in Azure is currently causing issues with DXC deployments.](https://rewindex.com/company/optimizely/incidents/hp428kbtdwgc.md) | minor | 2018-01-31 10:29 UTC | 2018-02-06 07:10 UTC | 6 d | resolved |

## Cite this

Optimizely posted 5 status incidents in January 2018 (0 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/optimizely/2018/01
- Citation: Optimizely, “Optimizely in January 2018” (2018-01-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/optimizely/2018/01 (CC BY 4.0).
- Markdown link: `[Optimizely: Optimizely in January 2018 (2018-01-01)](https://rewindex.com/company/optimizely/2018/01)`


---
Canonical: https://rewindex.com/company/optimizely/2018/01 · Markdown: https://rewindex.com/company/optimizely/2018/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T10:18:28.558Z