Vendor record
Optimizely
Checked
Front door check counts and Optimizely’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Optimizely endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.optimizely.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Optimizely product, region or your app worked.
How we count front door checksOptimizely says
Incident posts from Optimizely’s status page, with its titles, impact levels and times. They say what Optimizely chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
21
incidents Optimizely posted, last 90 days
Median recorded duration: 3h 4m. From 21 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Degraded Snippet Publishing Performance
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(3h 4m)
Content Graph Performance Degradation
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(25m)
Optimizely Graph - All region's production clusters experienced failed stored queries
Not specifiedOptimizely’s postStarted, per Optimizely
Closed in our record(4h 12m)
Optimizely Graph - USEA production clusters experiencing intermittent availability issues
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(2h 58m)
CMP: Data Not Loading in Plan, Resources, Library, and Other Modules (GCP Stack)
MajorOptimizely’s postStarted, per Optimizely
Closed in our record(1h 50m)
15 older records
Delay of E-Mails Submitted via SMTP API
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(26m)
CMP Analytics Data Not Displaying
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(21h 45m)
SSL trust issue causing login failures across multiple DXP environments
MajorOptimizely’s postStarted, per Optimizely
Closed in our record(7h 34m)
CMP and DAM are inaccessible
CriticalOptimizely’s postStarted, per Optimizely
Closed in our record(2h 50m)
Service degradation due to network connectivity issue in Southeast Asia
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(2h 25m)
CMP: Assets are missing from DAM post upload
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(4h 17m)
DXP - Multiple environments returning error 503 - Affecting only Non-production environments
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(6h 1m)
CMP: PDF File Preview Generation Unavailable
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(5h 32m)
Performance degration for image delivering, tracking and online version
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(1h 26m)
Campaign: Degraded performance for sending emails
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(4h 28m)
Netspring outage
MajorOptimizely’s postStarted, per Optimizely
Closed in our record(13h 39m)
CMP: Modules are not loading in the platform
MajorOptimizely’s postStarted, per Optimizely
Closed in our record(2h 26m)
ODP and OCP Availability
Not specifiedOptimizely’s postStarted, per Optimizely
Closed in our record(1h 19m)
Login results in 429 error
MajorOptimizely’s postStarted, per Optimizely
Closed in our record(3h 18m)
Digital Experience Platform (DXP) West US
MinorOptimizely’s postStarted, per Optimizely
Closed in our record(5h 29m)
Your code, your dependencies
See which of your code paths call Optimizely
Connect GitHub or GitLab to find where your public or private repository uses Optimizely. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Optimizely status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Optimizely currently down?
Optimizely's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Optimizely last have an outage?
The most recent closed incident record began 1 day ago and spans 3h 4m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Optimizely?
No. CheckUpstream checks Optimizely’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Optimizely in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Optimizely?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.