Optimizely: Delay in support response
Timeline of updates
- resolved
The unforeseen event is now under control and personnel is returning to the office.
From Optimizely’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.optimizely.com (opens in new tab).
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).
- Title
- Delay in support response
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/381ljjhklp26
Optimizely profileRecent Optimizely incidentsAll outages on April 12, 2017Optimizely in April 2017MarkdownJSON