# Optimizely: Delay in support response

> Optimizely status incident “Delay in support response” on 2017-04-12: impact none (vendor’s label), 2.8 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/optimizely/incidents/381ljjhklp26
Last updated: 2017-04-12T12:25:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2017-04-12 09:39 UTC · Resolved: 2017-04-12 12:25 UTC · Duration: 2.8 h
- Updates: 1
- [Vendor status page: https://status.optimizely.com/incidents/381ljjhklp26](https://status.optimizely.com/incidents/381ljjhklp26)
- [Company: Optimizely](https://rewindex.com/company/optimizely.md)

## Timeline of updates

- **resolved** 2017-04-12 12:25 UTC: The unforeseen event is now under control and personnel is returning to the office.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: none) posted by Optimizely, started 2017-04-12 09:39 UTC, resolved after 2.8 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/optimizely/incidents/381ljjhklp26
- Citation: Optimizely, “Delay in support response” (2017-04-12 09:39 UTC). Archived by Rewindex: https://rewindex.com/company/optimizely/incidents/381ljjhklp26 (CC BY 4.0).
- Markdown link: `[Optimizely: Delay in support response (2017-04-12)](https://rewindex.com/company/optimizely/incidents/381ljjhklp26)`


---
Canonical: https://rewindex.com/company/optimizely/incidents/381ljjhklp26 · Markdown: https://rewindex.com/company/optimizely/incidents/381ljjhklp26.md · JSON: https://rewindex.com/api/v1/companies/optimizely/incidents/381ljjhklp26 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:56:37.723Z