Is Episerver down?

Last checked 7m ago
Current status
Episerver is up

No incidents right now.

Official status page: https://status.episerver.com · Polled every 5 minutes · 135 components tracked

Episerver is operational right now. Last checked 7m ago; the most recent incident resolved 1d ago.

Real-time Episerver status, recent outages, and incident history — pulled directly from Episerver's official status page at https://status.episerver.com every 5 minutes. Pingoru tracks 135 Episerver services and has captured 16 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Episerver reports a new incident — free for 5 monitors, no credit card.

Users who monitor Episerver also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Episerver uptime 99.71% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 49m
    Started Jun 12, 2026, 02:50 PM UTC · Resolved Jun 12, 2026, 03:40 PM UTC
    Digital Experience Cloud Service - Management PortalConfigured Commerce – APAC RegionConfigured Commerce – EMEA RegionConfigured Commerce – NA Region
    Timeline · 5 updates
    • investigating · Jun 12, 2026, 02:50 PM UTC

      We are aware of an ongoing incident with one of our third party vendors that could cause site management-related API calls to fail and/or errors to be displayed. CDN cached traffic and security features are not impacted. We will continue to monitor the situation along with our vendor and will continue to post updates here as they become available.

    • identified · Jun 12, 2026, 03:03 PM UTC

      Our vendor has confirmed the issue has been identified and a fix is being implemented.

    • monitoring · Jun 12, 2026, 03:09 PM UTC

      Our vendor has confirmed that a fix has been implemented and they are monitoring the results. We will continue to monitor the situation closely.

    • monitoring · Jun 12, 2026, 03:24 PM UTC

      System performance should be restored but we will continue to monitor closely.

    • resolved · Jun 12, 2026, 03:40 PM UTC

      Our vendor has confirmed this issue has been resolved

    Latest: Our vendor has confirmed this issue has been resolved

  2. Resolved 7h 31m
    Started Jun 10, 2026, 11:49 AM UTC · Resolved Jun 10, 2026, 07:20 PM UTC
    LibraryPlanRequestsOpen APIAnalytics
    Timeline · 3 updates
    • investigating · Jun 10, 2026, 11:49 AM UTC

      We are currently investigating an incident affecting multiple modules within the Optimizely Content Marketing Platform (CMP). The following modules are currently inaccessible to customers: - Plan - Requests - Library / DAM Our Engineering team is actively working on a resolution. We will provide a further update as soon as more information is available.

    • monitoring · Jun 10, 2026, 12:31 PM UTC

      A fix has been implemented and we're currently monitoring the situation.

    • resolved · Jun 10, 2026, 07:20 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved
    Started Jun 09, 2026, 08:34 AM UTC · Resolved Jun 04, 2026, 08:00 AM UTC
    Timeline · 1 update
    • resolved · Jun 09, 2026, 08:34 AM UTC

      A partial outage affected OCP Job Scheduler, where scheduled jobs across multiple apps failed to execute due to an expired certificate in the env‑injector mutating webhook, in the US region only. This prevented required environment variables from being injected into workloads, causing job failures. Non-job features (e.g., configuration, webhooks) remained functional. No data loss occurred, and all affected jobs caught up after the issue was resolved, though customers may have experienced delays (e.g., stale audience syncs)

    Latest: A partial outage affected OCP Job Scheduler, where scheduled jobs across multiple apps failed to execute due to an expired certificate in the env‑injector mutating webhook, in the …

  4. Resolved 5h 16m
    Started Jun 08, 2026, 09:27 AM UTC · Resolved Jun 08, 2026, 02:44 PM UTC
    LibraryOpen API
    Timeline · 3 updates
    • investigating · Jun 08, 2026, 09:27 AM UTC

      We are currently investigating an issue affecting customers hosted on the GCP stack. Starting this morning, calls to the DAM REST API endpoint 'GET /v3/assets/{asset_id}/renditions' appear to be returning a 500 Internal Server Error. As a result, configured image renditions (used for cropping and scaling images across channels) are not being served. Affected customers will see only the original/main asset image in place of their configured renditions. The rendition configuration UI in CMP Settings > Assets also appears to be impacted, with rendition setups failing to load correctly. Affected: Optimizely Content Marketing Platform (CMP) – DAM / Asset Renditions Infrastructure: GCP-hosted customers only Impact: Image renditions unavailable; 'GET /v3/assets/{asset_id}/renditions' returning 500 We are actively investigating the root cause and will provide an update soon.

    • monitoring · Jun 08, 2026, 10:05 AM UTC

      A fix has been implemented for the issue affecting DAM asset renditions on the GCP stack. We are actively monitoring the situation to confirm full stability. If you are still experiencing issues, please contact Optimizely Technical Support Services for assistance. We will provide a final update once the incident is fully resolved.

    • resolved · Jun 08, 2026, 02:44 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 4h 36m
    Started Jun 02, 2026, 07:48 AM UTC · Resolved Jun 02, 2026, 12:25 PM UTC
    Content Recommendations API
    Timeline · 4 updates
    • investigating · Jun 02, 2026, 07:48 AM UTC

      We are currently investigating an issue affecting the Content Recommendation service in EMEA region. Due to an API disruption, we are unable to serve recommendations at this time. Users may notice missing or unavailable recommendations across the platform. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience!

    • monitoring · Jun 02, 2026, 08:51 AM UTC

      A fix has been implemented and we are closely monitoring the results.

    • monitoring · Jun 02, 2026, 10:45 AM UTC

      We continue to monitor the service.

    • resolved · Jun 02, 2026, 12:25 PM UTC

      The incident is resolved.

    Latest: The incident is resolved.

See the full Episerver outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Episerver outage history →

Or sign up free to get alerts when Episerver breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →