Contentstack 中断历史

1. 2026年9月1日 UTC 16:20investigating

   我们目前正在调查一个影响Azure欧盟区域内容出版和网络浏览的问题。 在此期间,用户在发布内容时和在提供webhook时可能会遇到延误. 已公布内容的内容提供情况未受影响,其他地区未受影响. 我们的工程团队已经动员起来,正在积极努力,找出根源,恢复正常服务。 客户行动:目前不需要客户采取任何行动。 一旦掌握了更多信息,我们将分享下一次最新情况。 如果您在获取我们的服务方面遇到困难, 请联系我们的Contentack 支持, 请求援助@ contentstack.com .

2. 2026年9月1日 UTC 16:29identified

   这一问题影响到Azure欧盟区域的内容出版和网络浏览发送的根源已经查明。 我们的工程队目前正在执行一个恢复正常服务的固定方案。 已公布内容的内容提供情况未受影响,其他地区未受影响. 客户行动:目前不需要客户采取任何行动。 一旦掌握了更多信息,我们将分享下一次最新情况。 如果您在获取我们的服务方面遇到困难, 请联系我们的Contentack 支持, 请求援助@ contentstack.com .

3. 2026年9月1日 UTC 16:57monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年9月1日 UTC 17:01monitoring

   我们正在继续监测任何其他问题.

5. 2026年9月1日 UTC 17:11resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月28日 UTC 11:16investigating

   8月28日 UTC凌晨8点左右,我们开始调查一个影响到AWS欧盟地区Webhook调度员的问题. 在此期间,Webhook触发器不会因任何事件而针对本地区所有客户被发射. 内容出版本身不受影响,继续正常处理;这个问题仅限于网络hook发送. 我们的工程团队已经动员起来,正在积极努力,找出根源,恢复正常服务。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年8月28日 UTC 11:57identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年8月28日 UTC 12:08monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年8月28日 UTC 12:15resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 22:05investigating

   我们目前正在调查一个影响微软Azure NA和Azure EU区域Contack Web应用程序的问题。 在此期间,用户可能成功登录,但发现仪表板(应用程序主页)未能加载. 这个问题仅限于网络应用接口Content Management API,发布内容的内容交付,其他服务继续正常运行. 我们的工程团队已经动员起来,正在积极开展工作,以找出根源,恢复对网络应用程序的充分访问。 我们理解这可能造成的不便,并正在高度优先地对待它。 客户行动:目前不需要客户采取任何行动。 需要暂时管理内容的客户可以通过内容管理API继续这样做. 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年7月23日 UTC 22:35identified

   已经确定了影响微软Azure NA和Azure EU区域Contact Web应用程序的问题。 我们的工程组目前正在执行一个修复措施,以恢复正常的准入。 这个问题仅限于网络应用界面——内容管理API,发布内容的内容交付,其他服务继续正常运行. 客户行动:目前不需要客户采取任何行动。 需要暂时管理内容的客户可以通过内容管理API继续这样做. 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年7月23日 UTC 22:51monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年7月23日 UTC 22:59resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 09:50investigating

   我们目前正在调查影响GCP NA区域内容出版的问题。 在此期间,用户在试图发布内容时可能会遇到故障. 所有其他服务都未受影响。 我们的工程团队已经动员起来,正在积极努力,找出根源,恢复正常服务。 客户行动:目前不需要客户采取任何行动。 等我们掌握更多信息后,我们再分享下一次更新 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年7月13日 UTC 09:54monitoring

   影响GCP NA区域内容出版的问题已经缓解,服务正常运行. 我们的小组将继续密切监测系统的业绩,以确保稳定。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年7月13日 UTC 09:57resolved

   影响GCP NA区域内容出版的这一事件已经完全解决,所有系统都在正常运行. 客户行动:目前不需要客户采取任何行动。 我们感谢你在努力恢复服务时的耐心 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年7月12日 UTC 10:13investigating

   在协调世界时7月12日10点,我们开始在GCP NA上发布内容时出现间歇性延误. 用户可能会通知出版请求的完成时间比通常要长。 所有其他组成部分都未受影响。 目前无需客户采取行动。 一旦掌握了更多信息,我们将分享下一次最新情况。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年7月12日 UTC 10:20identified

   我们查明了在GCP NA上发布内容时时断时续拖延的原因. 我们的工程组正在修复 所有其他组成部分都未受影响。 目前无需客户采取行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年7月12日 UTC 10:24monitoring

   我们的工程小组已经对影响全球气候方案NA内容出版的间歇性延误采取了补救措施,我们正在监测结果。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

4. 2026年7月12日 UTC 10:30resolved

   影响GCP NA内容出版的间歇性拖延问题已经解决. 我们的工程小组采用的固定方法稳定了出版业绩,我们通过持续监测确认了正常运作。 在整个事件中,所有其他组成部分都未受影响。 目前无需客户采取行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年7月11日 UTC 13:06investigating

   目前,我们正在调查关于干扰全球气候行动网络区域多种服务的报告。 客户在受影响服务中可能时有错误、延误或业绩下降。 我们的工程团队正在积极调查,以确定影响的根源和范围。 目前无需客户采取行动。 一旦获得更多信息,我们将分享下一份最新情况。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年7月11日 UTC 14:03identified

   受这一事件影响的GCP NA地区的多种服务现已恢复,正常运行. AgentOS仍然受到影响,我们的工程团队继续研究修复方案. 在GCP NA区域使用AgentOS的客户可能继续发生间歇性出错,延误或性能退化. 目前无需客户采取行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年7月11日 UTC 14:20resolved

   该区域所有服务已经恢复并正常运行。 目前无需客户采取行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年7月8日 UTC 14:32resolved

   影响AWS欧盟地区Webhook调度器的这一事件已经完全解决,所有系统都在正常运行. 发生了什么事: 出版量的增加使我们的伐木基础设施的储存能力很低,这暂时阻止了在仪表板上公布队列和网页记录。 实际的网络浏览发送和出版业务在整个过程中继续正常运行,在任何时刻都没有受到影响——这只影响到日志的能见度。 我们的团队增加了可用的存储能力,日志的能见度已完全恢复. 该期于协调世界时2026年7月8日从09:30左右至11:00活跃. 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年6月28日 UTC 21:00investigating

   我们正在调查一个影响Google Cloud平台NA(美国)区域内容交付API的问题。 在此期间,用户在通过CDA获取内容时可能遇到出错或中断. 所有其他Contextack服务和地区都按预期运作。 我们的工程团队已经动员起来,正在积极努力,找出根源,恢复正常服务。 我们知道这对你的行动可能产生的影响 并且正以最高优先处理这件事 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年6月28日 UTC 21:11identified

   影响Google Cloud平台NA(美国)区域内容交付API的问题的根源已经查明,我们的工程团队目前正在实施一项修复措施来恢复正常服务。 所有其他Contack服务和区域都未受影响。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年6月28日 UTC 21:12monitoring

   影响Google Cloud平台NA(美国)区域内容交付API的问题已经得到缓解,服务正常运行. 我们的小组将继续密切监测系统的业绩,以确保稳定。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

4. 2026年6月28日 UTC 21:19resolved

   这个影响Google Cloud平台NA(美国)区域内容交付API的事件已经完全解决,所有系统都正常运行. 发生了什么:一个影响后端基础设施的问题导致内容交付API无法使用. 我们的工程队查明了原因,执行了一个固定方案,并核实这项服务已完全恢复。 客户行动:目前不需要客户采取任何行动。 如果你还遇到问题 请联系我们的支援小组 我们感谢你在努力恢复服务时的耐心 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年6月26日 UTC 13:01investigating

   我们正在调查一个影响亚马逊网络服务欧盟地区Webhook调度员的问题。 在此期间,用户可能会在webhook发送中遇到延误或失败. 其他区域和所有其他Concertack服务都未受影响。 我们的工程团队已经动员起来,正在积极努力,找出根源,恢复正常服务。 客户行动:目前不需要客户采取任何行动。 如果您的集成依赖于webhook事件, 您可能希望监视您的端点日志 。 一旦获得更多信息,我们将分享下一份最新情况。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

2. 2026年6月26日 UTC 13:17identified

   已查明影响亚马逊网络服务欧盟区域Webhook调度员的问题的根源。 我们的工程队目前正在执行一个恢复正常服务的固定方案。 其他区域以及核心内容管理和交付服务仍未受到影响。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

3. 2026年6月26日 UTC 13:30monitoring

   影响亚马逊网络服务欧盟区域Webhook调度员的问题已经得到缓解,服务正常运行. 我们的小组将继续密切监测系统的业绩,以确保稳定。 客户行动:目前不需要客户采取任何行动。 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

4. 2026年6月26日 UTC 13:35resolved

   这一影响亚马逊网络服务欧盟地区Webhook调度器的事件已经完全解决,所有系统都在正常运行. 目前无需客户采取行动。 我们感谢你在努力恢复服务时的耐心 如果您在获取我们的服务方面有任何困难, 请联系客户成功团队寻求帮助@ contentstack.com.

自动翻译自官方事件更新。

1. 2026年6月17日 UTC 13:23investigating

   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. 2026年6月17日 UTC 13:32identified

   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. 2026年6月17日 UTC 13:38monitoring

   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. 2026年6月17日 UTC 13:44resolved

   This incident has been resolved.

1. 2026年5月29日 UTC 07:31identified

   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. 2026年5月29日 UTC 08:34identified

   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. 2026年5月29日 UTC 10:11identified

   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. 2026年5月29日 UTC 12:18resolved

   This incident has been resolved.

1. 2026年5月28日 UTC 07:04investigating

   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. 2026年5月28日 UTC 11:04identified

   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. 2026年5月28日 UTC 13:46resolved

   This incident has been resolved.

1. 2026年5月15日 UTC 16:15investigating

   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. 2026年5月15日 UTC 17:00monitoring

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

3. 2026年5月15日 UTC 17:06resolved

   This incident has been resolved.

1. 2026年5月9日 UTC 11:19resolved

   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]

1. 2026年4月11日 UTC 06:18investigating

   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. 2026年4月11日 UTC 07:04identified

   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. 2026年4月11日 UTC 07:18monitoring

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

4. 2026年4月11日 UTC 07:32resolved

   This incident has been resolved.

1. 2026年4月9日 UTC 18:04investigating

   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. 2026年4月9日 UTC 18:10monitoring

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

3. 2026年4月9日 UTC 18:13resolved

   This incident has been resolved.

1. 2026年3月21日 UTC 05:24investigating

   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. 2026年3月21日 UTC 06:10investigating

   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. 2026年3月21日 UTC 06:40monitoring

   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. 2026年3月21日 UTC 06:45resolved

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

1. 2026年2月12日 UTC 11:03identified

   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. 2026年2月12日 UTC 11:35monitoring

   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. 2026年2月12日 UTC 11:57resolved

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

1. 2026年2月7日 UTC 12:42resolved

   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.

1. 2026年2月6日 UTC 09:46investigating

   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. 2026年2月6日 UTC 10:13identified

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

3. 2026年2月6日 UTC 10:23monitoring

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

4. 2026年2月6日 UTC 10:33resolved

   This incident has been resolved.