Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Contentstack Outage History

Every past Contentstack outage tracked by IsDown, with detection times, duration, and resolution details.

There were 106 Contentstack outages since October 2018. The 17 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 11, 2026

April 2026: Contentstack - AWS EU - Full outage

Detected Apr 11, 2026 2:18 AM EDT · Resolved Apr 11, 2026 3:37 AM EDT · Duration about 1 hour

Contentstack experienced a full outage in the AWS EU region lasting 1.3 hours, affecting all services including Content Delivery API, Content Management API, Web Application, and other core components. The issue was caused by a problem with the ingress controller during an AWS EKS Kubernetes cluster upgrade, which disrupted traffic routing across the region. The engineering team identified the root cause, implemented a fix to restore traffic routing, and resolved the incident after monitoring for stability.

Minor April 9, 2026

April 2026: Contentstack – Azure EU – Intermittent Single and Bulk Publishing/Unpublishing Issue

Detected Apr 9, 2026 2:04 PM EDT · Resolved Apr 9, 2026 2:16 PM EDT · Duration 12 minutes

Contentstack's Azure EU region experienced intermittent issues with single and bulk publishing/unpublishing, releases, search, entries, and webhooks for 12 minutes. Customers observed delays in seeing entries reflected on the entry list page and experienced delays or loss of webhook invocations. The incident was resolved after implementing a fix and monitoring the results.

Minor March 21, 2026

March 2026: Contentstack – Azure NA – Service Disruption

Detected Mar 21, 2026 1:24 AM EDT · Resolved Mar 21, 2026 2:46 AM EDT · Duration about 1 hour

Contentstack experienced a service disruption in the Microsoft Azure North America region lasting 1.4 hours, causing service unavailability and API errors for users. The outage affected multiple services within the region while the engineering team investigated and worked to identify the root cause. The issue was successfully mitigated and all systems returned to normal operation, with continued monitoring to ensure stability.