rewindex

ChangesOptimizelyConfigured Commerce incident (November 19th 2026)

Optimizely: Incident updated: Configured Commerce incident (November 19th 2026)

Incident updateNormal progress (rule, 100%)Changed status.optimizely.com (opens in new tab)
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
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-21 00:30 UTC
AddedUpdateresolved#3
Before: not present
After: This incident has been resolved.

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.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodaySaturday, November 21Sat, Nov 21

1 rewrite, 1 incident change

Cite this

Incident updated: Configured Commerce incident (November 19th 2026) on Optimizely’s status page, changed 2026-11-21 00:33 UTC (change 1 of 2).

Title
Incident updated: Configured Commerce incident (November 19th 2026)
Vendor
Optimizely
Date
URL
https://rewindex.com/change/rec690a9e0284c4

All Optimizely changesOptimizely profileMarkdownJSON