- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
What to do
Check whether you use Optimizely in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-10-13 18:10 UTC and 2026-10-13 18:10 UTC may need a replay.Subscribe to Optimizely's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=optimizely works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Optimizely 1
- resolved
Between 15:05 and 16:10 UTC on October 13, 2026, Data Platform customers in the US region experienced delayed data ingestion and elevated error rates on the GraphQL API. From about 15:20 to 16:07 UTC, most GraphQL API requests failed with HTTP 5xx errors or timeouts. Ingestion of new data was delayed by up to about 65 minutes. All delayed data accepted during the incident was processed by 16:10 UTC. Our engineers applied infrastructure changes that resolved the issue in the US region. The same changes have been applied to our other regions to prevent a similar issue there. We apologize for the disruption.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-93fb97e12d
Is Optimizely still down?
No, this incident was resolved 2026-10-13 18:10 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
0m, from 2026-10-13 18:10 UTC to 2026-10-13 18:10 UTC, by the times Optimizely posted.
What was affected?
Optimizely named in us.
What caused it?
Optimizely hasn't published a root cause. If it does, it shows here.
Where does this come from?
Optimizely's official status page, https://status.optimizely.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.