Contentstack incident

Contentstack – Azure EU – Publishing and Webhook Delays

Major Resolved View vendor source →

Contentstack experienced a major incident on September 1, 2026 affecting Content Management API and Webhook Dispatcher, lasting 50m. The incident has been resolved; the full update timeline is below.

Started
Sep 01, 2026, 04:20 PM UTC
Resolved
Sep 01, 2026, 05:11 PM UTC
Duration
50m
Detected by Pingoru
Sep 01, 2026, 04:20 PM UTC

Affected components

Content Management APIWebhook Dispatcher

Update timeline

  1. investigating Sep 01, 2026, 04:20 PM UTC

    We are currently investigating an issue affecting content publishing and webhook delivery in the Azure EU region. During this time, users may experience delays when publishing content and in webhook delivery. Content delivery of already-published content remains unaffected, and other regions remain unaffected. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. Customer Action: No action is required from customers at this time. We will share our next update as soon as we have more information. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

  2. identified Sep 01, 2026, 04:29 PM UTC

    The root cause of the issue affecting content publishing and webhook delivery in the Azure EU region has been identified. Our engineering team is currently implementing a fix to restore normal service. Content delivery of already-published content remains unaffected, and other regions remain unaffected. Customer Action: No action is required from customers at this time. We will share our next update as soon as we have more information. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

  3. monitoring Sep 01, 2026, 04:57 PM UTC

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

  4. monitoring Sep 01, 2026, 05:01 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Sep 01, 2026, 05:11 PM UTC

    This incident has been resolved.