Contentstack Outage History

Contentstack proactively monitored an upstream Microsoft Azure NA region issue that lasted 4.8 hours, but no actual impact occurred to their services. All Contentstack systems including content management and content delivery remained fully operational throughout the incident. The incident was resolved when the upstream cloud provider issue was fixed.

Contentstack experienced delayed webhook executions in their AWS North America region for 6.7 hours, affecting the Webhook Dispatcher component while other services remained unaffected. The engineering team identified the root cause and deployed fixes to resolve the issue.

Contentstack's web application experienced UI degradation in AWS EU and NA regions for 53 minutes, causing intermittent delays and errors with entry pages not loading properly. Users were advised to perform hard refreshes as a temporary workaround while experiencing these interface issues. The engineering team implemented a fix and monitored the results before fully resolving the incident.

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.

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.

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.