Optimizely: Azure Issue: North Central US
Timeline of updates
- resolved
From Azure: Preliminary root cause: Engineers identified configuration change as the potential root cause. Mitigation: Engineers performed a change to the service configuration to BGP and mitigate the issue. Next steps: Engineers will continue to investigate to establish the full root cause in approximately 72 hours.
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 2017-11-06 21:19 UTC, resolved after 34 min, 1 update(s).
- Title
- Azure Issue: North Central US
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/6jcs6pjrxjmh
Optimizely profileRecent Optimizely incidentsAll outages on November 6, 2017Optimizely in November 2017MarkdownJSON