Optimizely: Configured Commerce - Degradation of sandbox environments in US region
Timeline of updates
- resolved
We are resolving this issue as it has been successfully mitigated for the vast majority of clients. While we are seeing the normal background rate for sporadic DNS resolution failures, it is still possible for a very limited subset of clients to experience occasional impacts in the sandbox environment until we fully implement necessary infrastructure configuration changes. In the meantime, we have a workaround in place, and we are also working with our third-party supplier to obtain an RCA for additional context surrounding this incident.
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: minor) posted by Optimizely, started 2024-08-30 15:05 UTC, resolved after 24 d, 1 update(s).
- Title
- Configured Commerce - Degradation of sandbox environments in US region
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/7wd21gg2k5bk
Optimizely profileRecent Optimizely incidentsAll outages on August 30, 2024Optimizely in August 2024MarkdownJSON