Search

Companies / Optimizely / incidents

Optimizely: Login results in 429 error

Impact: majorStatus: resolvedStarted Resolved (3.3 h)3 updatesSource: stspg.io (opens in new tab)
Summary

Optimizely reported a major outage in which login returned 429 errors, affecting access to some products through Optimizely Identity. It started at 2026-07-23 15:26 UTC and was resolved at 2026-07-23 18:41 UTC, lasting 3 h 15 min; Optimizely attributed it to a disruption with its identity provider, Okta.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: General - Optimizely IdentityOptimizely Identity

Timeline of updates

  1. investigating

    We're aware of an issue affecting access to some products, caused by a disruption with our identity provider (Okta). We're engaged with Okta support and working to restore service. Updates to follow as soon as possible.

  2. identified

    We have identified an issue stemming from a disruption with our identity provider. We are seeing some improvement as we work to mitigate the problem and we continue to work with them on a full resolution.

  3. resolved

    The disruption with our identify provider has been resolved. Thank you for your patience with this issue.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Optimizely profile · Recent Optimizely incidents · Markdown · JSON