Rewindex

CompaniesContentstackIncidents

Contentstack: Contentstack – Azure EU – Publishing and Webhook Delays

MajorStatus: resolvedStarted Resolved (50 min)5 updatesstspg.io (opens in new tab)
Part of an outage event

Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents

Contentstack’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h 39 min vs Google Cloud’s own post)

Swipe sideways to see the whole diagram.

blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory +51 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud,Clerk +3GitHubposted +18 min, did not name GoogleCloudBolt.new+24 minTwilioposted +1 h 42 min, did not nameGoogle CloudGorgias, Iterable+2 h 23 min to +2 h 37 minContentstack (this incident)posted +1 h 39 min
blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory +51 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk +3GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minContentstack (this incident)posted +1 h 39 min
Contentstack is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["Contentstack (this incident)<br/>posted +1 h 39 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Microsoft Azure EU Region - Webhook DispatcherWebhook DispatcherContent Management APIMicrosoft Azure EU Region - Content Management API

Timeline of updates

  1. investigating

    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 support@contentstack.com.

  2. identified

    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 support@contentstack.com.

  3. monitoring

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

  4. monitoring

    We are continuing to monitor for any further issues.

  5. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Contentstack profileRecent Contentstack incidentsMarkdownJSON