Is Optimizely Down?

No — Optimizely is up

Reachable from all 8 checked regions

Average response time: 979ms

Last checked 27 minutes ago · checks run every 6 hours

Official status page: https://status.optimizely.com

Optimizely uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1023ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

1279ms

DNS 0ms TCP 2ms TLS 15ms TTFB 609ms

arn

1237ms

DNS 0ms TCP 1ms TLS 12ms TTFB 618ms

lhr

1217ms

DNS 0ms TCP 2ms TLS 11ms TTFB 575ms

nrt

660ms

DNS 0ms TCP 1ms TLS 10ms TTFB 630ms

ord

382ms

DNS 0ms TCP 2ms TLS 14ms TTFB 344ms

sin

2052ms

DNS 0ms TCP 1ms TLS 13ms TTFB 878ms

sjc

479ms

DNS 0ms TCP 3ms TLS 11ms TTFB 445ms

syd

1321ms

DNS 0ms TCP 1ms TLS 14ms TTFB 802ms

yyz

422ms

DNS 0ms TCP 1ms TLS 10ms TTFB 311ms

What Optimizely does

Optimizely began as an A/B testing tool and is now a suite: Web Experimentation and Feature Experimentation alongside a CMS, Commerce, a Content Marketing Platform and Optimizely Data Platform. Experiments run inside customer websites through a snippet or SDK, so an Optimizely fault surfaces on other companies' pages rather than on Optimizely's own.

What an outage looks like

Pages running the Optimizely snippet render the original variant or flash unstyled content while the script times out, and experiment results stop updating. Feature flags fall back to their default values, which can silently disable a feature that was meant to be on. Editors lose access to the CMS or find publishing fails. Optimizely reports most components per region, so EMEA can be affected while NA is not.

What to do about it

Read status.optimizely.com and find your region: CMS SaaS, Search and Navigation and Optimizely Graph are each reported for APAC, EMEA and NA separately, and the top banner covers all of them. Check the specific product line too, since Web Experimentation, Feature Experimentation, Configured Commerce and the Data Platform fail independently. Optimizely also posts scheduled maintenance there, which explains most short windows.

Is it down for everyone, or just you?

If this page says Optimizely is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Optimizely outage FAQ

Is Optimizely down, or is the problem my site?

Because Optimizely runs inside your pages, its faults look like your faults. Load status.optimizely.com and check the component for your product and region, then open your browser network tab: a snippet that times out or returns an error is an Optimizely-side problem, while a snippet that loads and does nothing usually points at your experiment configuration.

What happens to feature flags when Optimizely is unavailable?

SDKs fall back to their default values rather than erroring, which is safer than failing closed but easy to miss. A feature you had switched on can quietly turn off for everyone, and nothing in your own logs will say why. If you run Feature Experimentation in production, the flag defaults you ship are effectively your outage behaviour, so they are worth setting deliberately.

Does an Optimizely outage affect every region?

Usually not. Optimizely reports CMS SaaS, Search and Navigation and Optimizely Graph separately for APAC, EMEA, NA and UAE, and incidents are frequently confined to one of them. The overall banner aggregates every region and every product, so it can read degraded when your instance is healthy, or read normal while a single regional component is not.

Will my experiment data be lost during an outage?

Visitors served during an incident may not be recorded, which shows up as a gap rather than as an error. That matters for interpretation more than for data safety: an experiment that ran through an outage has a period where exposure and conversion counts are incomplete, and treating the whole run as clean can skew the result. Check the incident window against your reporting dates.

How we measure this

We request Optimizely's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Optimizely publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Optimizely goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required