Changes / Optimizely / Login results in 429 error
Optimizely: Major incident: Login results in 429 error
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Login results in 429 error
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-07-23 15:26 UTC
Before: not present
After: 2026-07-23 18:41 UTC
Before: not present
After: General - Optimizely Identity, Optimizely Identity
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: The disruption with our identify provider has been resolved. Thank you for your patience with this issue.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Login results in 429 error (this change) 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. | Major incident |
All Optimizely changes → · Optimizely profile · Markdown · JSON