Live / Optimizely / Incident
Optimizely: Degraded Snippet Publishing Performance
Optimizely · optimizely.comMinor incidentResolved2026-10-15 13:39 UTC
Public — what happened
Summary
Optimizely reported a minor issue starting at 10:35 UTC on October 15, 2026, in which publishing experiments and other changes took longer than usual, with some customers seeing deployments stuck in the "Uploading to CDN" stage. The company said experiences already live kept working normally throughout. At 12:00 UTC, Optimizely said it had traced the slowdown to a spike in snippet uploads that backed up its processing queue, and that it had acted to stop the source of the backlog. The incident was marked resolved at 13:39 the same day.
Affected
Snippet Building
Timeline
- Started — 2026-10-15 10:35 UTC
- Investigating — 2026-10-15 10:35 UTC
- Identified — 2026-10-15 12:00 UTC
- Resolved — 2026-10-15 13:39 UTC · 3h 04m 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 43, 2026, our weekly internet health report.