Optimizely: Increased error rate in application and REST APIs
Affected components: Feature Experimentation - Optimizely REST APIOptimizely REST APIApp UIWeb Experimentation - App UIApplication UIFeature Experimentation - Application UI
Timeline of updates
- resolved
We have resolved an issue that was resulting in some users receiving errors in the application and configuration-related REST APIs (500 or 502 status codes). There was no impact to experiment execution or ingestion related to the issue.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
84c66154e47f5c9c…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Optimizely, started 2026-06-22 13:03 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased error rate in application and REST APIs
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/c3g2d2txcgbs
Optimizely profileRecent Optimizely incidentsAll outages on June 22, 2026Optimizely in June 2026MarkdownJSON