Changes Optimizely Content Graph Performance Degredation

Optimizely: Incident updated: Content Graph Performance Degredation

Incident updateNormal progress (rule, 100%)Changed 2026-10-28 20:03 UTCstatus.optimizely.com

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Optimizely removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1

~~monitoring~~

resolved

AddedResolved time#2

not present

2026-10-28 20:00 UTC

AddedUpdateresolved2026-10-28 20:00 UTC#3

not present

This incident has been resolved and the service has remained healthy

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

Oct 28
Before captured 17:34 UTC
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on Oct 29, 00:43 UTC. Record hash 3ece824b8d3f2598…
Download proof
Oct 28
After captured 20:03 UTC
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on Oct 29, 00:43 UTC. Record hash e5385858dc871a53…
Download proof

History of this incident

Wednesday, October 28

1 incident change

Normal progress
20:03Incident
Incident updateContent Graph Performance Degredationthis change

Cite this

Incident updated: Content Graph Performance Degredation on Optimizely’s status page, changed 2026-10-28 20:03 UTC (change 1 of 1).

Title: Incident updated: Content Graph Performance Degredation
Vendor: Optimizely
Date: 2026-10-28 20:03 UTC
URL: https://rewindex.com/change/r8cbcaa71d4c795

All Optimizely changes Optimizely profile Markdown JSON