Optimizely Service Status
System status
Incident overview
Total incidents
22
Active now
0
Resolved
22
Avg. resolution
4h 43m
Recent incidents
View all →Content Graph Performance Degredation
Asset uploads failing in Optimizely CMP and DAM
Degraded Performance - CMS Edit Mode in DXP
Optimizely Campaign: Campaign user interface
ODP EU Region - Impact due to Snowflake incident
Degraded Snippet Publishing Performance
Elevated GraphQL API errors and delayed data ingestion in ODP – US region
Content Graph Performance Degradation
Data processing delays in EMEA
Optimizely Graph - All region's production clusters experienced failed stored queries
Frequently asked questions
Is Optimizely Service down right now?
Optimizely Service is currently maintenance. DevHelm monitors Optimizely Service's official status page continuously and updates this page every 5 minutes.
What is Optimizely Service's current uptime?
Optimizely Service has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Optimizely Service's official status page data.
How many incidents has Optimizely Service had recently?
Optimizely Service has experienced 22 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 4h 43m. All incidents are currently resolved.
What components does Optimizely Service monitor?
DevHelm tracks 140 individual components for Optimizely Service, including East US, E-mail, E-mail dispatch, Canada East, Singapore, and 135 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Optimizely Service outages?
You can subscribe to Optimizely Service's incident feed via Atom/RSS at devhelm.io/status/episerver/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Optimizely Service as a dependency in your DevHelm workspace.
About Optimizely Service status monitoring
This page provides real-time operational status for Optimizely Service, powered by DevHelm's continuous monitoring infrastructure. We track Optimizely Service's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Optimizely Service status data is refreshed every 5 minutes. We currently track 140 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Optimizely Service in your stack
Get alerted when Optimizely Service has issues — before your users notice. Set up in 30 seconds.