Live / Optimizely / Incident
Optimizely: Degraded Performance - CMS Edit Mode in DXP
Optimizely · optimizely.comMinor incidentResolved2026-10-23 15:46 UTC
Public — what happened
Summary
Optimizely reported a minor issue starting at 14:14 UTC on 2026-10-23, in which the CMS editing interface and background scheduled tasks were slower than usual and sometimes returned errors in select DXP environments. By 14:41 UTC the company said it had identified the root cause and was working on a fix. At 14:55 UTC it said performance had returned to normal and it was monitoring for stability, and the incident was marked resolved at 15:46 UTC.
Affected
North Europe, Sweden Central
Timeline
- Started — 2026-10-23 14:14 UTC
- Investigating — 2026-10-23 14:14 UTC (2 updates)
- Identified — 2026-10-23 14:41 UTC
- Monitoring — 2026-10-23 14:55 UTC
- Resolved — 2026-10-23 15:46 UTC · 1h 32m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Optimizely against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Optimizely: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Optimizely report →
More from Optimizely
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.