Live  /  Optimizely  /  Incident

Optimizely: Content Graph Performance Degredation

Optimizely · optimizely.comResolved2026-10-28 20:00 UTC
Public — what happened

Summary

Optimizely said its Content Graph service had a performance problem that began at 17:27 UTC on 28 October 2026, with users getting HTTP 500 and 404 error responses. The company reported that it had remediated the errors and was watching the service's health closely. The incident was marked resolved at 20:00 the same day, and Optimizely did not state a cause in the text provided.

Affected

Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

As listed on Optimizely’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 45, 2026, our weekly internet health report.

The full archive is on the Optimizely status & history page.

Related: Optimizely status & history. SquidGrid is not affiliated with Optimizely.