Is Optimizely Down?

No — Optimizely is up

Optimizely's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 848 ms

Right now

The verdict is the worse of these two. How we decide

Optimizely's status page

status.optimizely.com · read 3 minutes ago · checked every 3 minutes

Operational

Optimizely's components, as its status page reports them
Component	Status
E-mail	Operational
Telephone	Operational
Support Portal - optimizely.com/support	Operational
Application UI	Operational
Datafile Build Service	Operational
SDKs	Operational
Results Page	Operational
Event Pipeline	Operational
Optimizely REST API	Operational
Experiment Collaboration	Operational
Full Stack (Legacy)	Operational
Results API	Operational

43 more, all operational · show all 55

All of Optimizely's components
Component	Status
Optimizely Support
E-mail	Operational
Telephone	Operational
Support Portal - optimizely.com/support	Operational
Feature Experimentation
Application UI	Operational
Datafile Build Service	Operational
SDKs	Operational
Results Page	Operational
Event Pipeline	Operational
Optimizely REST API	Operational
Experiment Collaboration	Operational
Full Stack (Legacy)	Operational
Results API	Operational
Events API	Operational
Event Export	Operational
Web Experimentation
Integrations	Operational
Snippet Delivery	Operational
Snippet Building	Operational
Recommendations	Operational
App UI	Operational
Visual Editor	Operational
DCP	Operational
List Attributes	Operational
Preview Mode	Operational
Results API	Operational
Events API	Operational
Event Export	Operational
Performance Edge
Data file build and Prop	Operational
Edge Decider (CDN worker)	Operational
General
Optimizely Identity	Operational
Optimizely Admin Center	Operational
Content Marketing Platform
Library	Operational
Plan	Operational
Requests	Operational
Open API	Operational
Analytics	Operational
Optimizely Opal
Opal Chat	Operational
Opal Backend	Operational
Opal Tools	Operational
Opal Agents	Operational
Opal Retrieval Engine	Operational
Optimizely Public Websites
Optimizely main website - Optimizely.com	Operational
World Developer Forum - world.optimizely.com	Operational
Nuget CMS/Commerce package feed - nuget.optimizely.com	Operational
Search & Navigation Demo Portal - find.optimizely.com	Operational
Edge Delivery
Manifest Creation	Operational
AI Optimization
Contextual Bandits	Operational
Multi-Armed Bandits	Operational
Adaptive Audiences	Operational
Optimizely Analytics
app.netspring.io	Operational
analytics.optimizely.com	Operational
Digital Experience Cloud Service - Management Portal	Operational
Optimizely Graph - NA Region	Operational
Optimizely Graph - UAEN Region	Operational
Configured Commerce – NA Region	Operational
Configured Commerce: Product Information Management (PIM) – NA Region	Operational

85 locations All operational

Open their status page

FlareWarden checks

app.optimizely.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 848 ms
Checked: 1 hour ago

By region

Amsterdam reachable, 1393 ms
Dallas reachable, 445 ms
Newark reachable, 540 ms
Paris reachable, 1160 ms
San Jose reachable, 577 ms
Stockholm reachable, 851 ms
Sydney reachable, 1285 ms
Toronto reachable, 540 ms

Timing by region

Connection timing for each region that loaded the page
Region	TCP	TLS	TTFB
Amsterdam	1 ms	13 ms	669 ms
Dallas	1 ms	9 ms	314 ms
Newark	2 ms	18 ms	431 ms
Paris	2 ms	11 ms	624 ms
San Jose	1 ms	14 ms	513 ms
Stockholm	1 ms	9 ms	695 ms
Sydney	0 ms	9 ms	783 ms
Toronto	1 ms	11 ms	442 ms

We check that app.optimizely.com loads, not every feature behind it. Test it yourself

History

Incidents Optimizely reported

Since Oct 22, 3 days · from status.optimizely.com

Incidents: 3
Major or critical: 0
Median to resolve: 3h 19m

Degraded Performance - CMS Edit Mode in DXP
minor · Oct 23
lasted 1h 31m
Optimizely Campaign: Campaign user interface
minor · Oct 22
lasted 3h 19m
ODP EU Region - Impact due to Snowflake incident
minor · Oct 21
lasted 12h 29m

Optimizely website availability

Measured by FlareWarden · app.optimizely.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 1186ms

Last 30 days

74-day clean streak

Sep 25 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.optimizely.com from multiple regions every 6 hours. Optimizely's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 74 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Optimizely itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Optimizely goes down

We check Optimizely every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required