Contentstack Outage History

Started Oct 23, 2026, 04:16 AM UTC· resolved Oct 23, 2026, 05:53 AM UTC

1. investigating Oct 23, 2026, 04:16 AM UTC

   We are currently investigating an issue affecting Contentstack customer support channels. During this time, customers may be unable to raise new tickets through the Support Portal, and responses to support requests via chat and email may be delayed. The issue is related to a third-party service provider we use for support operations. Contentstack products, APIs, and content delivery are not affected. Our team is working with the provider to restore normal service as quickly as possible. Customer Action: If you are unable to raise a ticket through the Support Portal, please email [email protected]. Replies may be delayed until the issue is resolved.

2. identified Oct 23, 2026, 05:37 AM UTC

   The root cause of the issue affecting Contentstack customer support channels has been identified: an outage on the platform of a third-party service provider we use for support operations. The provider is working on a fix, and our team is in contact with them to restore normal service. Until then, customers may be unable to raise new tickets through the Support Portal, and responses to support requests via chat and email may be delayed. Contentstack products, APIs, and content delivery are not affected. Customer Action: If you are unable to raise a ticket through the Support Portal, please email [email protected]. Replies may be delayed until the issue is resolved. 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. resolved Oct 23, 2026, 05:53 AM UTC

   This incident affecting Contentstack customer support channels has been fully resolved, and all support channels are operating normally. Contentstack products, APIs, and content delivery were not affected at any point. Customer Action: If you tried to raise a ticket through the Support Portal during this period and it did not go through, please submit it again. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

Read the full incident report →

Started Oct 10, 2026, 05:56 PM UTC· resolved Oct 10, 2026, 06:19 PM UTC

1. investigating Oct 10, 2026, 05:56 PM UTC

   We are currently investigating an issue affecting AgentOS,Polaris and Automation in the GCP NA region. During this time, users may be unable to access Custom Agents, Polaris, and automations may fail to execute. Content management and delivery of already-published content remain unaffected. Other regions remain unaffected. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. We understand the impact this may have on your operations and are treating this with the highest priority. 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. monitoring Oct 10, 2026, 06:11 PM UTC

   A fix has been applied for the issue affecting Custom Agents, Polaris, and Automation in the GCP NA region, and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

3. resolved Oct 10, 2026, 06:19 PM UTC

   This incident affecting Custom Agents, Polaris, and Automation in the GCP NA region has been fully resolved, and all systems are operating normally. Customer Action: No action is required from customers at this time. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

Read the full incident report →

Started Sep 20, 2026, 03:31 AM UTC· resolved Sep 20, 2026, 04:35 AM UTC

1. investigating Sep 20, 2026, 03:31 AM UTC

   we began investigating an issue affecting the delivery of newly published content in the GCP NA region. During this time, recently published or unpublished content may take longer than usual to appear in delivered content, including through GraphQL queries and asset URLs. Content delivery of already-published content remains unaffected. 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 20, 2026, 04:18 AM UTC

   The root cause of the issue affecting the delivery of newly published content in the GCP NA region has been identified. Our engineering team is currently implementing a fix to restore normal service. During this time, recently published or unpublished content may take longer than usual to appear in delivered content, including through GraphQL queries and asset URLs. Content delivery of already-published content remains unaffected. 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.

3. monitoring Sep 20, 2026, 04:30 AM UTC

   The issue affecting the delivery of newly published content in the GCP NA region has been mitigated and services are operating normally. Recently published and unpublished changes are being reflected in delivered content as expected. Our team will continue monitoring system performance closely to ensure stability. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

4. resolved Sep 20, 2026, 04:35 AM UTC

   This incident affecting the delivery of newly published content in the GCP NA region has been fully resolved and all systems are operating normally. Recently published and unpublished changes are being reflected in delivered content as expected. Delivery of already-published content continued to function normally throughout. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services,

Read the full incident report →

Started Sep 16, 2026, 05:40 PM UTC· resolved Sep 16, 2026, 07:06 PM UTC

1. investigating Sep 16, 2026, 05:40 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 16, 2026, 05:56 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 16, 2026, 07:03 PM UTC

   The issue affecting content publishing and webhook delivery in the Azure EU region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

4. resolved Sep 16, 2026, 07:06 PM UTC

   This incident affecting content publishing and webhook delivery in the Azure EU region has been fully resolved and all systems are operating normally. Customer Action: No action is required from customers at this time. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

Read the full incident report →

Started Sep 16, 2026, 09:22 AM UTC· resolved Sep 16, 2026, 03:04 PM UTC

1. investigating Sep 16, 2026, 09:22 AM UTC

   We are currently experiencing an issue with our Support Live Chat functionality, and the Support Portal is also impacted due to an outage with an upstream service provider, Salesforce. Support Portal and Email may also be intermittently impacted during this time. Our team is actively monitoring the situation and working to restore our support services as quickly as possible. In the meantime, our support team remains available to assist you. If you experience any difficulties accessing our services, please contact Contentstack Support at [email protected]

2. identified Sep 16, 2026, 10:47 AM UTC

   The issue has been identified and a fix is being implemented.

3. identified Sep 16, 2026, 12:22 PM UTC

   Our upstream service provider's fix is now rolling out region by region, and we're seeing our Support Live Chat and Support Portal return to normal in the regions where that rollout has completed. Support Portal and Email may continue to be intermittently impacted in regions where the rollout is still in progress. All other services remain unaffected. We're continuing to monitor the rollout as it completes across all regions, and our upstream provider is working on a permanent fix. 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].

4. monitoring Sep 16, 2026, 02:59 PM UTC

   Our upstream service provider has completed the next phase of their rollout, and our Support Live Chat and Support Portal now appear to be operating normally. Our engineering team is actively monitoring to confirm continued stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Contentstack Support for assistance at [email protected].

5. resolved Sep 16, 2026, 03:04 PM UTC

   This incident affecting Support Live Chat and Support Portal has been fully resolved and all systems are operating normally.

Read the full incident report →

Started Sep 01, 2026, 04:20 PM UTC· resolved Sep 01, 2026, 05:11 PM UTC

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.

Read the full incident report →

Started Aug 28, 2026, 11:16 AM UTC· resolved Aug 28, 2026, 12:15 PM UTC

1. investigating Aug 28, 2026, 11:16 AM UTC

   On August 28 around 08:00 UTC, we began investigating an issue affecting the Webhook Dispatcher in the AWS EU region. During this time, webhook triggers are not being fired for any events across all customers in this region. Content publishing itself is not affected and continues to process normally; this issue is limited to webhook delivery. 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. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Aug 28, 2026, 11:57 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Aug 28, 2026, 12:08 PM UTC

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

4. resolved Aug 28, 2026, 12:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 10:05 PM UTC· resolved Jul 23, 2026, 10:59 PM UTC

1. investigating Jul 23, 2026, 10:05 PM UTC

   We are currently investigating an issue affecting the Contentstack Web Application in the Microsoft Azure NA and Azure EU regions. During this time, users may successfully log in but find that the dashboard (application homepage) fails to load. This issue is limited to the web application interface the Content Management API, content delivery of published content, and other services continue to operate normally. Our engineering team has been mobilized and is actively working to identify the root cause and restore full access to the web application. We understand the inconvenience this may cause and are treating it with high priority. Customer Action: No action is required from customers at this time. Customers who need to manage content in the interim can continue to do so via the Content Management API. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Jul 23, 2026, 10:35 PM UTC

   The issue affecting the Contentstack Web Application in the Microsoft Azure NA and Azure EU regions has been identified. Our engineering team is currently implementing a fix to restore normal access. This issue is limited to the web application interface — the Content Management API, content delivery of published content, and other services continue to operate normally. Customer Action: No action is required from customers at this time. Customers who need to manage content in the interim can continue to do so via the Content Management API. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Jul 23, 2026, 10:51 PM UTC

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

4. resolved Jul 23, 2026, 10:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 13, 2026, 09:50 AM UTC· resolved Jul 13, 2026, 09:57 AM UTC

1. investigating Jul 13, 2026, 09:50 AM UTC

   We are currently investigating an issue affecting content publishing in the GCP NA region. During this time, users may experience failures when attempting to publish content. All other services remains 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 Customer Success team for assistance at [email protected].

2. monitoring Jul 13, 2026, 09:54 AM UTC

   The issue affecting content publishing in the GCP NA region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. resolved Jul 13, 2026, 09:57 AM UTC

   This incident affecting content publishing in the GCP NA region has been fully resolved and all systems are operating normally. Customer Action: No action is required from customers at this time. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jul 12, 2026, 10:13 AM UTC· resolved Jul 12, 2026, 10:30 AM UTC

1. investigating Jul 12, 2026, 10:13 AM UTC

   On July 12 at 10:00 UTC, we began experiencing intermittent delays when publishing content on GCP NA. Users may notice publish requests taking longer than usual to complete. All other components remains unaffected. 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 Customer Success team for assistance at [email protected].

2. identified Jul 12, 2026, 10:20 AM UTC

   We identified the cause of intermittent delays when publishing content on GCP NA. Our engineering team is working on a fix. All other components remain unaffected. No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Jul 12, 2026, 10:24 AM UTC

   Our engineering team has applied a fix for the intermittent delays affecting content publishing on GCP NA and we are monitoring the results. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved Jul 12, 2026, 10:30 AM UTC

   The intermittent delays affecting content publishing on GCP NA have been resolved. The fix applied by our engineering team has stabilized publishing performance, and we have confirmed normal operation through continued monitoring. All other components remained unaffected throughout this incident. No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jul 11, 2026, 01:06 PM UTC· resolved Jul 11, 2026, 02:20 PM UTC

1. investigating Jul 11, 2026, 01:06 PM UTC

   We are currently investigating reports of disruption affecting multiple services in the GCP NA region. Customers may experience intermittent errors, delays, or degraded performance across affected services. Our engineering team is actively investigating to determine the root cause and scope of impact. No action is required from customers at this time. We will share our next update as soon as more information is available. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Jul 11, 2026, 02:03 PM UTC

   Multiple services in the GCP NA region affected by this incident have now recovered and are operating normally. AgentOS remains impacted, and our engineering team continues to work on a fix. Customers using AgentOS in the GCP NA region may continue to experience intermittent errors, delays, or degraded performance. No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. resolved Jul 11, 2026, 02:20 PM UTC

   All services in the region have recovered and are operating normally. No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jul 08, 2026, 04:00 AM UTC· resolved Jul 08, 2026, 01:00 PM UTC

1. resolved Jul 08, 2026, 02:32 PM UTC

   This incident affecting the Webhook Dispatcher in the AWS EU region has been fully resolved and all systems are operating normally. What happened: An increase in publishing volume caused available storage capacity on our logging infrastructure to run low, which temporarily prevented publish queue and webhook logs from appearing in the dashboard. Actual webhook delivery and publishing operations continued to function normally throughout and were not impacted at any point — this affected log visibility only. Our team increased the available storage capacity, and log visibility has been fully restored. The issue was active from approximately 09:30 to 13:00 UTC on July 8, 2026. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jun 28, 2026, 09:00 PM UTC· resolved Jun 28, 2026, 09:19 PM UTC

1. investigating Jun 28, 2026, 09:00 PM UTC

   We are currently investigating an issue affecting the Content Delivery API in the Google Cloud Platform NA(US) region. During this time, users may experience errors or disruptions when fetching content via the CDA. All other Contentstack services and regions are operating as expected. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. We understand the impact this may have on your operations and are treating this with the highest priority. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Jun 28, 2026, 09:11 PM UTC

   The root cause of the issue affecting the Content Delivery API in the Google Cloud Platform NA (US) region has been identified and our engineering team is currently implementing a fix to restore normal service. All other Contentstack services and regions remain unaffected. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Jun 28, 2026, 09:12 PM UTC

   The issue affecting the Content Delivery API in the Google Cloud Platform NA (US) region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved Jun 28, 2026, 09:19 PM UTC

   This incident affecting the Content Delivery API in the Google Cloud Platform NA (US) region has been fully resolved, and all systems are operating normally. What happened: An issue affecting backend infrastructure caused the Content Delivery API to become unavailable. Our engineering team identified the cause, implemented a fix, and verified that service has been fully restored. Customer Action: No action is required from customers at this time. If you are still experiencing issues, please contact our support team. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jun 26, 2026, 01:01 PM UTC· resolved Jun 26, 2026, 01:35 PM UTC

1. investigating Jun 26, 2026, 01:01 PM UTC

   We are currently encountering technical difficulties with our Webhook functionalities. Our team is actively investigating to determine the underlying cause and to implement a resolution. If you have any questions or concerns, please do not hesitate to contact Contentstack support at [email protected].

2. identified Jun 26, 2026, 01:17 PM UTC

   The root cause of the issue affecting the Webhook Dispatcher in the Amazon Web Services EU Region has been identified. Our engineering team is currently implementing a fix to restore normal service. Other regions and core content management and delivery services remain unaffected. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Jun 26, 2026, 01:30 PM UTC

   The issue affecting the Webhook Dispatcher in the Amazon Web Services EU Region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved Jun 26, 2026, 01:35 PM UTC

   This incident affecting the Webhook Dispatcher in the Amazon Web Services EU Region has been fully resolved and all systems are operating normally. No action is required from customers at this time. We appreciate your patience while we worked to restore service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

Read the full incident report →

Started Jun 17, 2026, 01:23 PM UTC· resolved Jun 17, 2026, 01:44 PM UTC

1. investigating Jun 17, 2026, 01:23 PM UTC

   We are currently investigating an issue affecting the Web Application in the Microsoft Azure US Region. During this time, users may experience difficulties loading the Contentstack Application. Other regions and content delivery of already-published content remain unaffected. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. We understand the impact this may have on your operations and are treating this with the highest priority. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Jun 17, 2026, 01:32 PM UTC

   The root cause of the issue affecting the Web Application in the Microsoft Azure US Region has been identified. Our engineering team is currently implementing a fix to restore normal service. Other regions and content delivery of already-published content remain unaffected. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Jun 17, 2026, 01:38 PM UTC

   The issue affecting the Web Application in the Microsoft Azure US Region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: If you are still experiencing difficulties loading the Contentstack application, please clear your local browser cache and reload the page. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved Jun 17, 2026, 01:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2026, 07:31 AM UTC· resolved May 29, 2026, 12:18 PM UTC

1. identified May 29, 2026, 07:31 AM UTC

   We are aware of an ongoing issue with our upstream cloud provider affecting the Microsoft Azure NA region. At this time, we have not observed any impact to Contentstack services, and all systems — including content management and content delivery — are operating normally. As a precaution, our engineering team is proactively monitoring the situation closely and is prepared to act immediately should any impact to our services arise. We are posting this update in the interest of transparency so you are informed while we keep watch. Customer Action: No action is required from customers at this time. We will share our next update within 60 minutes, or sooner if the situation changes. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified May 29, 2026, 08:34 AM UTC

   The upstream cloud provider issue affecting the Microsoft Azure NA region remains ongoing, with recovery still in progress on the provider's side. Contentstack services continue to operate normally, and we have not observed any impact to content management or content delivery at any point. Our engineering team remains actively engaged and is continuing to monitor the situation closely, ready to act immediately should any impact to our services arise. Customer Action: No action is required from customers at this time. We will share our next update within 60 minutes, or sooner if the situation changes. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. identified May 29, 2026, 10:11 AM UTC

   The upstream cloud provider issue affecting the Microsoft Azure NA region is still ongoing, with recovery continuing on the provider's side. Contentstack services remain fully operational, and we have not observed any impact to content management or content delivery at any point during this event. Our engineering team continues to actively monitor the situation and remains ready to respond immediately should any impact to our services arise. Customer Action: No action is required from customers at this time. We will share our next update within 60 minutes, or sooner if the situation changes. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved May 29, 2026, 12:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 07:04 AM UTC· resolved May 28, 2026, 01:46 PM UTC

1. investigating May 28, 2026, 07:04 AM UTC

   We are currently investigating an issue causing delayed webhook executions. Please note that no other services are affected due to the webhook delay. Our team is actively working to identify the root cause and restore normal service. If you have any questions or concerns, please do not hesitate to contact Contentstack support at [email protected]."

2. identified May 28, 2026, 11:04 AM UTC

   Our Engineering Team has identified the issue and deployed the required fixes. We are continuing to monitor the situation closely and will provide further updates as progress is made. If you have any questions or concerns, please do not hesitate to contact Contentstack Support at [email protected].

3. resolved May 28, 2026, 01:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2026, 04:15 PM UTC· resolved May 15, 2026, 05:06 PM UTC

1. investigating May 15, 2026, 04:15 PM UTC

   We are currently investigating an issue affecting the Web Application in the AWS EU & AWS NA region. During this time, users may experience intermittent delays and errors within the Contentstack user interface, particularly when the entry page is not loading. If you experience this issue, please perform a hard refresh of the page. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. monitoring May 15, 2026, 05:00 PM UTC

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

3. resolved May 15, 2026, 05:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 09, 2026, 11:19 AM UTC· resolved May 09, 2026, 11:19 AM UTC

1. resolved May 09, 2026, 11:19 AM UTC

   An industry-wide security vulnerability known as "Copy Fail" (CVE-2026-31431) was publicly disclosed. This critical vulnerability affected the Linux operating systems used across most major cloud providers. Resolution We are writing to let you know that our engineering team has successfully completed the full remediation of this vulnerability across all of our cloud infrastructure. The official security patches have been completely deployed, and post-upgrade validation has been performed to ensure all systems are running securely. Customer Impact & Actions Required * Action Required: None. Our services are fully patched and secure, and you do not need to make any changes on your end. * Service Impact: No service interruptions occurred during this security update. Security and reliability remain our highest priorities. If you have any questions or require further information, please feel free to reach out to our support team at [email protected]

Read the full incident report →

Started Apr 11, 2026, 06:18 AM UTC· resolved Apr 11, 2026, 07:32 AM UTC

1. investigating Apr 11, 2026, 06:18 AM UTC

   We are currently investigating an issue impacting all services in the AWS EU region, which may result in a full outage for users. Our engineering team has been engaged and is actively working to identify the root cause and restore services as quickly as possible. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. identified Apr 11, 2026, 07:04 AM UTC

   The issue has been identified within the ingress controller during an ongoing AWS EKS Kubernetes cluster upgrade, which led to a disruption impacting all services in the AWS EU region. Our team has isolated the root cause and is actively implementing a fix to restore normal traffic routing. Services are expected to recover as the remediation progresses.

3. monitoring Apr 11, 2026, 07:18 AM UTC

   A fix has been implemented, and traffic has been restored. We are currently monitoring the results to ensure continued stability.

4. resolved Apr 11, 2026, 07:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 09, 2026, 06:04 PM UTC· resolved Apr 09, 2026, 06:13 PM UTC

1. investigating Apr 09, 2026, 06:04 PM UTC

   We are currently experiencing issues with Single and Bulk Publishing/Unpublishing, Releases, Search, and Entries. As a result, customers may observe delays in seeing entries reflected on the entry list page. We are also noticing issues with Webhooks, which may lead to delays or loss of invocations. Our team is actively working to resolve the issue and will share further updates as they become available. Please reach out to Contentstack Support if you require assistance.

2. monitoring Apr 09, 2026, 06:10 PM UTC

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

3. resolved Apr 09, 2026, 06:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 21, 2026, 05:24 AM UTC· resolved Mar 21, 2026, 06:45 AM UTC

1. investigating Mar 21, 2026, 05:24 AM UTC

   We are currently investigating a outage affecting multiple services in the Microsoft Azure NA region. During this time, users may experience service unavailability and API errors. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

2. investigating Mar 21, 2026, 06:10 AM UTC

   Our engineering team continues to actively investigate the issue affecting multiple services in the Microsoft Azure NA region. Users may continue to experience service unavailability and API errors. We are working to identify the root cause and will provide another update as soon as more information becomes available. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

3. monitoring Mar 21, 2026, 06:40 AM UTC

   The issue affecting multiple services in the Microsoft Azure NA region has been mitigated and services are operating normally. Our team will continue monitoring system performance to ensure stability. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].

4. resolved Mar 21, 2026, 06:45 AM UTC

   This incident has been fully resolved and all systems are operating normally. Thank you for your patience while we worked to restore the services.

Read the full incident report →

Started Feb 12, 2026, 11:03 AM UTC· resolved Feb 12, 2026, 11:57 AM UTC

1. identified Feb 12, 2026, 11:03 AM UTC

   Customers in the Azure NA region may experience timeouts when accessing applications deployed on Launch, which may impact existing deployments. Our team is actively investigating the issue and working toward a resolution. We are closely monitoring the situation and will provide updates as more information becomes available. If you experience any issues accessing our services, please contact our Customer Success team for assistance.

2. monitoring Feb 12, 2026, 11:35 AM UTC

   A fix is being applied, and we are actively monitoring the situation. If you still face a timeout, affected customers are requested to redeploy their applications to ensure full restoration of service.

3. resolved Feb 12, 2026, 11:57 AM UTC

   This incident has been resolved. If you are still experiencing any issues, please redeploy your application or contact our Customer Support for assistance.

Read the full incident report →

Started Feb 06, 2026, 04:30 PM UTC· resolved Feb 06, 2026, 04:30 PM UTC

1. resolved Feb 07, 2026, 12:42 PM UTC

   On February 6 at 22:00 UTC, we experienced a temporary issue in the Azure NA region that impacted scheduled publishing operations. We want to assure you that immediate (non-scheduled) publishing operations were not affected by this incident. Our engineering team promptly investigated and resolved the root cause. All scheduled publishing functionality has now been fully restored, and all impacted scheduled publish jobs have been successfully recovered and published. You can continue scheduling content for publishing as usual. If you have any questions or continue to experience issues, please contact the Contentstack Support team for assistance.

Read the full incident report →

Started Feb 06, 2026, 09:46 AM UTC· resolved Feb 06, 2026, 10:33 AM UTC

1. investigating Feb 06, 2026, 09:46 AM UTC

   We are currently investigating an issue affecting Content Management (CMA) services in the Azure NA region. During this time, users may experience failures or delays with publishing and data management (CRUD) activities. Our engineering team is actively working toward a resolution. We are monitoring the situation closely and will provide further updates as they become available. If you encounter persistent issues, please reach out to the Contentstack Support team for assistance.

2. identified Feb 06, 2026, 10:13 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 06, 2026, 10:23 AM UTC

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

4. resolved Feb 06, 2026, 10:33 AM UTC

   This incident has been resolved.

Read the full incident report →