Optimizely: Content Graph Performance Degredation
Affected components: Optimizely Graph - APAC RegionOptimizely Graph - EMEA RegionOptimizely Graph - NA RegionOptimizely Graph - UAEN Region
Timeline of updates
- monitoring
Content Graph experienced http 500 and 404 errors, which we have remediated. We are continuing to monitor the health of the service closely.
- resolved
This incident has been resolved and the service has remained healthy
Changes Rewindex caught on this incident
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 these records existed by then and have 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-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3ece824b8d3f2598…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e5385858dc871a53…
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 2026-10-28 17:27 UTC, resolved after 2.5 h, 2 update(s); edited after publishing.
- Title
- Content Graph Performance Degredation
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/86q04dsmlbh4
Optimizely profileRecent Optimizely incidentsAll outages on October 28, 2026Optimizely in October 2026MarkdownJSON