Optimizely: Configured Commerce/B2B - Intermittent DNS conflict reported by multiple customers
Timeline of updates
- resolved
We have identified an issue regarding a DNS conflict which may impact multiple customers and/or sites. Teams have identified an immediate mitigation for this issue to reset the ports being used for DNS queries on affected nodes.
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 2024-08-13 18:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Configured Commerce/B2B - Intermittent DNS conflict reported by multiple customers
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/9lhr0fgq8ywm
Optimizely profileRecent Optimizely incidentsAll outages on August 13, 2024Optimizely in August 2024MarkdownJSON